Renamed guides to include "How To" in their names

12 files changed, 29 insertions, 25 deletions

diff --git a/archiving_with_posix_utilities-1.png b/how_to_archive_with_posix_tar_cpio_and_pax-1.png
index 68b100a..68b100a 100644
--- a/archiving_with_posix_utilities-1.png
+++ b/how_to_archive_with_posix_tar_cpio_and_pax-1.png
diff --git a/archiving_with_posix_utilities-2.png b/how_to_archive_with_posix_tar_cpio_and_pax-2.png
index 2f31089..2f31089 100644
--- a/archiving_with_posix_utilities-2.png
+++ b/how_to_archive_with_posix_tar_cpio_and_pax-2.png
diff --git a/archiving_with_posix_utilities-3.png b/how_to_archive_with_posix_tar_cpio_and_pax-3.png
index 4a43e34..4a43e34 100644
--- a/archiving_with_posix_utilities-3.png
+++ b/how_to_archive_with_posix_tar_cpio_and_pax-3.png
diff --git a/archiving_with_posix_utilities.html b/how_to_archive_with_posix_tar_cpio_and_pax.html
index 17ce7bc..998afb7 100644
--- a/archiving_with_posix_utilities.html
+++ b/how_to_archive_with_posix_tar_cpio_and_pax.html
@@ -7,16 +7,16 @@
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>Archiving With POSIX Utilities</title>
+<title>How To Archive With POSIX tar, cpio and pax</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>Archiving With POSIX Utilities</h1>
+<h1>How To Archive With POSIX tar, cpio and pax</h1>
 <p class="subtitle">Published on 2020-07-22 22:30:00+02:00
-<p>The usual answer is <a href="https://www.gnu.org/software/tar/">tar</a>. As you may see I intentionally linked to the
-GNU Tar. If you are a *BSD user then you use some other implementation. Both of them follow and extend POSIX'es standard
-for tar utility. Or so you would think.
+<p>The usual answer to archive anything is <a href="https://www.gnu.org/software/tar/">tar</a>. As you may see I
+intentionally linked to the GNU Tar. If you are a *BSD user then you use some other implementation. Both of them follow
+and extend POSIX'es standard for tar utility. Or so you would think.
 <p>Right now there is no POSIX tar utility. It has been marked as legacy
 <a href="https://pubs.opengroup.org/onlinepubs/007908799/xcu/tar.html">already in 1997</a> and disappeared from the
 standard soon after. It's place took a behemoth called
@@ -34,7 +34,7 @@ mind what POSIX had to tell us back in the day.
 <p>Like I've already mentioned tarballs are the most popular. Not only that, they are commonly described as the easiest
 to use, although the interface is something that you can find jokes about. All operations on tarballs are handled via
 single tar utility.</p>
-<img src="archiving_with_posix_utilities-1.png" alt="box">
+<img src="how_to_archive_with_posix_tar_cpio_and_pax-1.png" alt="box">
 <p>Let's go through three basic operations: create an archive, list out the content, and extract it. Tar expects to have
 first argument to match this regular expression: <code>[rxtuc][vwfblmo]*</code>. The first part is <em>function</em>,
 and the second is a <em>modifier</em>. I'll focus only on those necessary to accomplish before-mentioned tasks.
@@ -124,7 +124,7 @@ $ cpio -id a_directory/another_file &lt;../archive.cpio
 1 block
 </pre>
 <p>This option tells cpio that it's allowed to create directories whenever it is necessary.</p>
-<img src="archiving_with_posix_utilities-2.png" alt="pass-through">
+<img src="how_to_archive_with_posix_tar_cpio_and_pax-2.png" alt="pass-through">
 <p>Bonus! Pass-through mode can be used to copy files listed in standard input to specified directory. It doesn't create
 an archive at all.</p>
 <pre>
@@ -233,6 +233,6 @@ don't get tricked by them. I find pax the most reliable of them as its "novelty"
 from both cpio and tar. Find a moment to check it out!
 <p>Let's pretend that <a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ar.html">ar</a> doesn't exist.
 Thank you.</p>
-<img src="archiving_with_posix_utilities-3.png" alt="boo!">
+<img src="how_to_archive_with_posix_tar_cpio_and_pax-3.png" alt="boo!">
 </article>
 <script src="https://stats.ignore.pl/track.js"></script>
diff --git a/stupid_templating_with_shell_cat_and_envsubst-1.png b/how_to_create_templates_with_shell_cat_and_envsubst-1.png
index d390eac..d390eac 100644
--- a/stupid_templating_with_shell_cat_and_envsubst-1.png
+++ b/how_to_create_templates_with_shell_cat_and_envsubst-1.png
diff --git a/stupid_templating_with_shell_cat_and_envsubst.html b/how_to_create_templates_with_shell_cat_and_envsubst.html
index 7a84554..99a9c7c 100644
--- a/stupid_templating_with_shell_cat_and_envsubst.html
+++ b/how_to_create_templates_with_shell_cat_and_envsubst.html
@@ -3,16 +3,16 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <meta name="author" content="aki">
-<meta name="tags" content="template, bash, cat, shell, envsubst">
+<meta name="tags" content="tutorial, template, templating, cat, shell, envsubst">
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>Stupid Templating With Shell, cat and envsubst</title>
+<title>How To Create Templates With Shell, cat and envsubst</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>Stupid Templating With Shell, cat and envsubst</h1>
+<h1>How To Create Templates With Shell, cat and envsubst</h1>
 <p class="subtitle">Published on 2020-07-14 20:26:00+02:00
 <p>Now something trivial and fun. Creating templates of documents or configurations in shell. There are two reasons why
 I considered doing that instead of using some more verbose utilities. First off, availability - I have POSIX compliant
@@ -30,7 +30,7 @@ BEFORE
 &lt;script src=""&gt;&lt;/script&gt;
 AFTER
 </pre>
-<img src="stupid_templating_with_shell_cat_and_envsubst-1.png" alt="actual cat">
+<img src="how_to_create_templates_with_shell_cat_and_envsubst-1.png" alt="actual cat">
 <p>What you see here is a combination of
 <a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_04">heredoc</a> and plain
 redirection. It's done like this to avoid calling <code>cat</code> more than once. The script simply concatenates BEFORE
diff --git a/flashing_lolin_nodemcu_v3-1.png b/how_to_flash_lolin_nodemcu_v3-1.png
index daceb97..daceb97 100644
--- a/flashing_lolin_nodemcu_v3-1.png
+++ b/how_to_flash_lolin_nodemcu_v3-1.png
diff --git a/flashing_lolin_nodemcu_v3.html b/how_to_flash_lolin_nodemcu_v3.html
index e535f74..39760d0 100644
--- a/flashing_lolin_nodemcu_v3.html
+++ b/how_to_flash_lolin_nodemcu_v3.html
@@ -2,16 +2,16 @@
 <html lang="en">
 <meta charset="utf-8">
 <meta name="author" content="aki">
-<meta name="tags" content="tutorial, flash, nodemcu, firmware, nodemcu, hardware">
+<meta name="tags" content="tutorial, flash, nodemcu, firmware, nodemcu">
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" type="text/css" href="style.css">
 
-<title>Flashing LOLin NodeMCU v3</title>
+<title>How To Flash LOLin NodeMCU v3</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>Flashing LOLin NodeMCU v3</h1>
+<h1>How To Flash LOLin NodeMCU v3</h1>
 <p class="subtitle">Published on 2020-06-29 17:58:00+02:00
 <p>Republishing old content. This is from when I bought and flashed my first NodeMCU clone (perhaps "loose
 implementation"?) of NodeMCU v3 called LOLin v3.
@@ -41,6 +41,6 @@ $ screen <u>/dev/ttyUSB0</u> 115200
 <pre>
 $ st -l <u>/dev/ttyUSB0</u> 115200
 </pre>
-<img src="flashing_lolin_nodemcu_v3-1.png" alt="nodemcu drawing">
+<img src="how_to_flash_lolin_nodemcu_v3-1.png" alt="nodemcu drawing">
 </article>
 <script src="https://stats.ignore.pl/track.js"></script>
diff --git a/organizing_your_lua_project-1.png b/how_to_organize_your_lua_project-1.png
index aa71459..aa71459 100644
--- a/organizing_your_lua_project-1.png
+++ b/how_to_organize_your_lua_project-1.png
diff --git a/organizing_your_lua_project-2.png b/how_to_organize_your_lua_project-2.png
index 0917288..0917288 100644
--- a/organizing_your_lua_project-2.png
+++ b/how_to_organize_your_lua_project-2.png
diff --git a/organizing_your_lua_project.html b/how_to_organize_your_lua_project.html
index d6bae4a..013f712 100644
--- a/organizing_your_lua_project.html
+++ b/how_to_organize_your_lua_project.html
@@ -3,16 +3,16 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <meta name="author" content="aki">
-<meta name="tags" content="tutorial, packaging, structuring, organizing, lua, project, howto">
+<meta name="tags" content="tutorial, structuring, organizing, lua, project, howto">
 <link rel="icon" type="image/png" href="cylo.png">
 <link rel="stylesheet" href="style.css">
 
-<title>Organizing Your Lua Project</title>
+<title>How To Organize Your Lua Project</title>
 
 <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav>
 
 <article>
-<h1>Organizing Your Lua Project</h1>
+<h1>How To Organize Your Lua Project</h1>
 <p class="subtitle">Published on 2021-01-07 15:45:00+01:00
 <p>From time to time I hear complaints about how Lua handles modules. Here and there I see and even answer myself
 questions regarding <code>require</code> and adjusting the paths in <code>package</code> to allow some desired
@@ -20,7 +20,7 @@ behaviour, with the most prominent issue of relative imports that always work.
 <p>Before we hop into the explanation of how to organize files in your Lua projects, let's talk about default importing
 mechanism in Lua: <a href="https://www.lua.org/manual/5.4/manual.html#pdf-require"><code>require</code></a>.</p>
 
-<img src="organizing_your_lua_project-1.png" alt="lua hierarchy">
+<img src="how_to_organize_your_lua_project-1.png" alt="lua hierarchy">
 
 <h2>How <code>require</code> handles paths</h2>
 <p>Both <code>package</code> and <code>require</code> are surprisingly interesting tools. At first glance they are
@@ -112,7 +112,7 @@ you use an installed package from an unknown working directory. <strong>Don't</s
 directory as it is not always the same. Using full names that consider the path setup <strong>guarantees
 results</strong>.</p>
 
-<img src="organizing_your_lua_project-2.png" alt="a random whale">
+<img src="how_to_organize_your_lua_project-2.png" alt="a random whale">
 
 <h2>Organizing your files</h2>
 <p>Finally, this is what we're waiting for. Assume you have a directory that is a parent of all of your project files.
diff --git a/index.html b/index.html
index 5a9b5e1..2612ae4 100644
--- a/index.html
+++ b/index.html
@@ -40,14 +40,15 @@ completely discard the concept of a keyboard.
 	<ul>
 		<li><a href="dear_imgui_and_love.html">Dear ImGui and LÖVE,</a>
 		<li><a href="environments_in_lua_5_2_and_beyond.html">Environments in Lua 5.2 and Beyond</a>
-		<li><a href="organizing_your_lua_project.html">Organizing Your Lua Project</a>
+		<li><a href="how_to_organize_your_lua_project.html">How To Organize Your Lua Project</a>
 	</ul>
 <li>Miscellaneous Informative
 	<ul>
-		<li><a href="archiving_with_posix_utilities.html">Archiving With POSIX Utilities</a>
-		<li><a href="flashing_lolin_nodemcu_v3.html">Flashing LOLin NodeMCU v3</a>
+		<li><a href="how_to_archive_with_posix_tar_cpio_and_pax.html">How To Archive With POSIX tar, cpio and pax</a>
+		<li><a href="how_to_flash_lolin_nodemcu_v3.html">How To Flash LOLin NodeMCU v3</a>
 		<li><a href="journey_home_application_deployment.html">Journey /home - Application Deployment</a>
-		<li><a href="stupid_templating_with_shell_cat_and_envsubst.html">Stupid Templating With Shell, cat and envsubst</a>
+		<li><a href="how_to_create_templates_with_shell_cat_and_envsubst.html">How To Create Templates With Shell, cat
+			and envsubst</a>
 		<li><a href="the_gentlest_introduction_to_building_with_makefiles.html">The Gentlest Introduction to Building With Makefiles</a>
 	</ul>
 <li>Rants
@@ -68,6 +69,9 @@ completely discard the concept of a keyboard.
 <section id="news">
 <h2>News</h2>
 <p><strong><time>2021-07-25</time></strong>
+Renamed most of the guides to include "How To" in their name to make them more visible. I'm thinking about doing another
+round of website restructurization.
+<p><strong><time>2021-07-25</time></strong>
 Published <a href="deconstructing_web_browsers.html">Deconstructing Web Browsers<a>, summary of now-removed <i>Plumbing
 Your Own Browser</i> and <i>Integrating Browser into Your Environment</i>.
 <p><strong><time>2021-07-25</time></strong>