HISTORY REWRITE. Fixes #53, sign-off all existing commits

This commit is the completion of a history rewrite to sign-off all unsigned commits in the repo from its inception.  Please see the comments on #53 for more details on how to move your WIP if you have a branch you are working with commits ahead of master.

Note that because this is a rewrite pulling master will return an error the first time unless you run `git pull --force`.  Make sure you stash or commit your changes if you have anything on master locally that isn't merged already.

README.md

@@ -64,21 +64,65 @@ Zarf runs on [a bunch of operating systems](./docs/supported-oses.md) and aims t
   </td>
   <td>
 
-You will also need to configure the .env file, use the command below to generate a template.  _Note that you don't need to set RHEL creds if you aren't using RHEL_
+  [Read](./examples/game/add-logging.md)
 
-`earthly +envfile`
+  </td>
+  </tr>
+<!-- row end -->
+
+<!-- row start -->
+  <tr valign="top">
+  <td>
+
+  **Roll Your Own**
+
+  _Custom packages_
+
+  </td>
+  <td>
+
+  Once you're comfortable with the basic workflow & able to deploy _someone else's_ Zarf deployment packages, it's time to roll your own.  Here's how.
+
+  </td>
+  <td>
+
+  Coming Soon!
+
+  </td>
+  </tr>
+<!-- row end -->
 
-## Building
----
-To build the packages needed for RHEL-based distros, you will need a Red Hat account (developer accounts are free) to pull the required RPMs for SELINUX-enforcing within the environment.  You must specify the credentials along with the RHEL version flag (7 or 8) in the .env file.  To build the package:
+</tbody>
+</table>
+
+&nbsp;
+
+
+<!--
+##########
+# This block is about expected USECASES & ADMIN of Zarf (in production)
+##########
+-->
+## To understand *the different modes of use*, have a look at...
+
+<table>
+<tbody>
 
-### Step 1b - Configure the `.env` file
+<!-- row start: cuz markdown hates html indention -->
+  <tr valign="top">
+  <td width="150">
 
-Some secrets also have to be passed to Earthly for your build, these are stored in the `.env` file.  YOu can generate a template to complete with the command below. 
+  **Simple Applications**
 
-`earthly +envfile`
+  _Appliance Mode_
 
-_To build the packages needed for RHEL-based distros, you will need to use your RedHat Developer account to pull the required RPMs for SELINUX-enforcing within the environment.  You must specify your credentials along with a RHEL version flag (7 or 8) in the `.env` file_
+  </td>
+  <td>
+
+  If want to "run a Kubernetes app" but aren't into hand-rolling a cluster just for it, Zarf can help. Here's how, and _why_ you might want to.
+
+  </td>
+  <td>
 
   Coming Soon!