wip

docs/v1/configuration/fusionssg-configuration/index.html

@@ -153,7 +153,7 @@ <h2 id="wips">wips</h2>
                 <p class="info">Files and folders prepended with "!" are <em>negated and will be generated.</em></p>
             </aside>
             <p class="ver">Introduced in v1.2.0</p>
-            <p>Beginning with v1.2.0, fusion.ssg will <em>report all works in progress</em> for each release build cycle. These warnings serve to prevent the <em>unintended</em> updating of web sites with missing HTML documents that should have been included but haven&#39;t because they are still marked as works in progress.</p>
+            <p>Beginning with v1.2.0, fusion.ssg will <em>report all works in progress</em> for each release build cycle. These warnings serve to prevent the <em>unintended</em> updating of websites with missing HTML documents that should have been included but haven&#39;t because they are still marked as works in progress.</p>
             <img src="/media/posts/WIPS-reporting.07983da1e438b481001057cfc959f0df.png" alt="imgage">
             <h2 id="tokens">tokens</h2>
             <p>Simple token property values declared here are global to the project and replace all matching simple tokens declared in <em>all HTML documents</em>. If both a local simple token and a global simple token have the same name <em>the local simple token takes precedence</em>.</p>

docs/v1/htmldocuments/templates/index.html

@@ -119,10 +119,10 @@ <h1 id="templates">Templates</h1>
     </code></pre>
             </article>
             <h2 id="works-in-progress">Works In Progress</h2>
-            <p>fusion.ssg can ignore templates that are <em>works in progress</em> during release builds, thereby preventing their associated HTML documents from polluting your web site. Please see <a href="/docs/v1/configuration/fusionssg-configuration#wips">wips</a> for more information.</p>
+            <p>fusion.ssg can ignore templates that are <em>works in progress</em> during release builds, thereby preventing their associated HTML documents from polluting your website. Please see <a href="/docs/v1/configuration/fusionssg-configuration#wips">wips</a> for more information.</p>
             <h3 id="works-in-progress-reporting">Works In Progress Reporting</h3>
             <p class="ver">Introduced in v1.2.0</p>
-            <p>Beginning with v1.2.0, fusion.ssg will report all works in progress during release builds. These warnings serve to prevent the unintended updating of web sites with missing HTML documents that should have been included but aren&#39;t because they are still marked as WIPS.</p>
+            <p>Beginning with v1.2.0, fusion.ssg will report all works in progress during release builds. These warnings serve to prevent the unintended updating of websites with missing HTML documents that should have been included but aren&#39;t because they are still marked as WIPS.</p>
             <img src="/media/posts/WIPS-reporting.07983da1e438b481001057cfc959f0df.png" alt="image">
             <footer class="container bottomnav">
                 <div class="navigation">

docs/v1/projectgenerator/index.html

@@ -103,6 +103,7 @@ <h1 id="fpg-project-generator">fpg Project Generator</h1>
             <p class="info">Beginning with v1.0.0, fusion.ssg no longer includes a project generator in its package and now requires that it be installed separately as a global package. Please read <a href="/docs/v1/installation">Installation</a> for instructions regarding its installation.</p>
             <p class="info">Beginning with v1.0.0, <a href="https://browsersync.io/">Browsersync</a>, which provides synchronized browser testing, has replaced live-server.</p>
             <p><em>fpg</em>, fusion.ssg&#39;s project generator, relieves you of the burden of having to manually create and configure your projects. When run, it <em><strong>creates your project and installs all of the project&#39;s dependencies</strong></em>. The most difficult task you will face when creating a new fusion.ssg project is deciding what to name it :).</p>
+            <p class="info">The generated project that fpg creates uses the <a href="https://picocss.com/">Pico.css</a> frameowork. However, you can delete it from your project's <b>src/css</b> folder and use whatever you prefer to build your website.</p>
             <h2 id="usage">Usage</h2>
             <p>To create a new project, run the following in your terminal in a folder of your choice:</p>
             <pre><code class="language-shell">fpg n | new &lt;target_folder&gt;

news/index.html

@@ -50,7 +50,7 @@ <h1>News</h1>
             <h1 id="articles">Articles</h1>
             <ul>
                 <li style="list-style: none;"><a href="/news/release/v1/2023/09/11/v1.2.0/" style="display: block;"><span style="font-size: calc(var(--font-size) * 1.2)">v1.2.0</span><br /><small>Posted on <i><span style="color: #fff; opacity: 0.755;">9/11/2023</span></i> to <i style="color: #fff; opacity: 0.755;">release/v1</i></small><br /><small style="color: #fff;">We are very pleased to announce the release of fusion.ssg v1.2.0. </small></a></li>
-                <li style="list-style: none;"><a href="/news/release/v1/2023/08/22/what-is-coming-in-the-next-release/" style="display: block;"><span style="font-size: calc(var(--font-size) * 1.2)">What's Coming in the next release</span><br /><small>Posted on <i><span style="color: #fff; opacity: 0.755;">8/22/2023</span></i> to <i style="color: #fff; opacity: 0.755;">release/v1</i></small><br /><small style="color: #fff;">In our pursuit to provide you with the best tools for creating resilient static HTML documents and web sites, the next release of fusion.ssg will feature numerous enhancements (please see below for details). </small></a></li>
+                <li style="list-style: none;"><a href="/news/release/v1/2023/08/22/what-is-coming-in-the-next-release/" style="display: block;"><span style="font-size: calc(var(--font-size) * 1.2)">What's Coming in the next release</span><br /><small>Posted on <i><span style="color: #fff; opacity: 0.755;">8/22/2023</span></i> to <i style="color: #fff; opacity: 0.755;">release/v1</i></small><br /><small style="color: #fff;">In our pursuit to provide you with the best tools for creating resilient static HTML documents and websites, the next release of fusion.ssg will feature numerous enhancements (please see below for details). </small></a></li>
                 <li style="list-style: none;"><a href="/news/release/v1/2023/08/03/v1.1.0/" style="display: block;"><span style="font-size: calc(var(--font-size) * 1.2)">v1.1.0</span><br /><small>Posted on <i><span style="color: #fff; opacity: 0.755;">8/3/2023</span></i> to <i style="color: #fff; opacity: 0.755;">release/v1</i></small><br /><small style="color: #fff;">We are very pleased to announce the release of fusion.ssg v1.1.0. </small></a></li>
                 <li style="list-style: none;"><a href="/news/release/v1/2023/07/05/v1.0.0/" style="display: block;"><span style="font-size: calc(var(--font-size) * 1.2)">v1.0.0</span><br /><small>Posted on <i><span style="color: #fff; opacity: 0.755;">7/5/2023</span></i> to <i style="color: #fff; opacity: 0.755;">release/v1</i></small><br /><small style="color: #fff;">It is with great pleasure that we announce our first production release, fusion.ssg v1.0.0. </small></a></li>
                 <li style="list-style: none;"><a href="/news/release/2023/06/28/v1.0.0-progress-report/" style="display: block;"><span style="font-size: calc(var(--font-size) * 1.2)">v1.0.0 Development Progress Report</span><br /><small>Posted on <i><span style="color: #fff; opacity: 0.755;">6/28/2023</span></i> to <i style="color: #fff; opacity: 0.755;">release</i></small><br /><small style="color: #fff;">There are numerous tasks that still need to be addressed. </small></a></li>

news/release/v1/2023/08/22/what-is-coming-in-the-next-release/index.html

@@ -56,7 +56,7 @@ <h1>What's Coming in the next release</h1>
             <p>Posted on <i style="color: #fff; opacity: 0.555;">8/22/2023</i> to <i style="color: #fff; opacity: 0.555;">release/v1</i></p>
         </hgroup>
         <article>
-            <p>In our pursuit to provide you with the best tools for creating resilient static HTML documents and web sites, the next release of fusion.ssg will feature numerous enhancements (please see below for details).</p>
+            <p>In our pursuit to provide you with the best tools for creating resilient static HTML documents and websites, the next release of fusion.ssg will feature numerous enhancements (please see below for details).</p>
             <!-- end -->
             <p>We are so thrilled to see fusion.ssg being adopted by creators from all over the world ❤️.</p>
             <p>Sincerely,</p>
@@ -65,7 +65,7 @@ <h1>What's Coming in the next release</h1>
             <p class="info">This page has been amended on 9/5/2023 to include the notice that the implementation for the feature "conditional includes" has changed and will now be using fusion.json for its configuration and not front matter.</p>
             <h3 id="cache-busting">Cache Busting</h3>
             <img style="float: left; border-radius: 50%; shape-outside: circle(); margin-right: 10px;" src="/media/posts/buster.bb8f8cfb12c191dc1fed61aadc5e152e.png" alt="image" width="100">
-            <p>The next release of fusion.ssg will make cache busting your web sites a snap 🫰🏼. When building for release, fusion.ssg will now <em>optionally</em> cache bust your site's assets (e.g. css, media, scripts, .etc), allowing your site's visitors to immediately experience its latest changes. Specifically, to <em>opt in to cache busting your release builds</em>, you will need to append <code>--cache-bust</code> to the <em>release:fusion</em> script located in your project's <em>package.json</em> file. Once appended, the release:fusion script should look exactly like the following:</p>
+            <p>The next release of fusion.ssg will make cache busting your websites a snap 🫰🏼. When building for release, fusion.ssg will now <em>optionally</em> cache bust your site's assets (e.g. css, media, scripts, .etc), allowing your site's visitors to immediately experience its latest changes. Specifically, to <em>opt in to cache busting your release builds</em>, you will need to append <code>--cache-bust</code> to the <em>release:fusion</em> script located in your project's <em>package.json</em> file. Once appended, the release:fusion script should look exactly like the following:</p>
             <pre><code class="language-json">&quot;release:fusion&quot;: &quot;fusion release --cache-bust&quot;,
 </code></pre>
             <p>fusion.ssg handles all the details, so no additional configuration or changes to your projects other than the above change to your package.json file&#39;s release:fusion script is required to enhance your sites with cache busting.</p>
@@ -81,7 +81,7 @@ <h3 id="conditional-includes">Conditional Includes</h3>
 </code></pre>
             <p>If an include&#39;s path matches one of these conditions, its content will not be included in the target HTML document.</p>
             <h3 id="wips-reporting-during-release-builds">WIPS Reporting During Release Builds</h3>
-            <p>fusion.ssg will now report all WIPS for each release build cycle. These warnings will serve to prevent the <em>unintended</em> updating of web sites with missing HTML documents that should have been included but aren&#39;t because they are still marked as WIPS.</p>
+            <p>fusion.ssg will now report all WIPS for each release build cycle. These warnings will serve to prevent the <em>unintended</em> updating of websites with missing HTML documents that should have been included but aren&#39;t because they are still marked as WIPS.</p>
             <img src="/media/posts/WIPS-reporting.07983da1e438b481001057cfc959f0df.png" alt="imgage">
             <h3 id="exposing-more-post-metadata-as-simple-token-values">Exposing More Post Metadata As Simple Token Values</h3>
             <p>When tokenizing a post, fusion.ssg will now expose a post&#39;s <em>post date</em>, <em>categories</em>, and <em>tags</em> as simple token values, allowing them to be used as simple tokens in your templates, pages and includes. This will serve to mitigate the need of having to use a component just to include these in your HTML documents.</p>

news/release/v1/2023/09/11/v1.2.0/index.html

@@ -85,7 +85,7 @@ <h3 id="wips-reporting-during-release-builds">WIPS Reporting During Release Buil
             <ul>
                 <li>Issue# 85: Report all WIPS to the console when building for release.</li>
             </ul>
-            <p>fusion.ssg will now report all WIPS for each release build cycle. These warnings will serve to prevent the <em>unintended</em> updating of web sites with missing HTML documents that should have been included but aren&#39;t because they are still marked as WIPS.</p>
+            <p>fusion.ssg will now report all WIPS for each release build cycle. These warnings will serve to prevent the <em>unintended</em> updating of websites with missing HTML documents that should have been included but aren&#39;t because they are still marked as WIPS.</p>
             <img src="/media/posts/WIPS-reporting.07983da1e438b481001057cfc959f0df.png" alt="imgage">
             <h3 id="cache-busting">Cache Busting</h3>
             <ul>