fixed conflict between make gen_status and make gen_top_html

The `bin/gen-status.sh` will report that the given markdown file
(`next/rules.md` or `next/guidelines.md`) is the source of the
generated HTML file.  This is so that the HTML produced by either
`make gen_status` or `make gen_top_html` will generated the same
HTML comments.  Moreover the comments in `next/rules.html` and
`next/guidelines.html` refer to the markdown file as the source of
the information instead of a tool such as `bin/gen-status.sh`.

Changed `bin/gen-status.sh` VERSION from "1.5.1 2024-04-28"
to "1.5.2 2024-04-30".

Added news for 2024-04-30 into `news.md`.

Make news dates "less shouty".

Ran `make www` to perform the above.

news.html

@@ -377,12 +377,34 @@
 
 <!-- BEFORE: 1st line of markdown file: news.md -->
 <h1 id="for-more-news-try-mastodon">For more news, try mastodon</h1>
-<h2 id="please-follow-the-ioccc-on-mastodon">Please follow** the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h2>
+<h3 id="please-follow-the-ioccc-on-mastodon">Please follow** the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
 <p>We use Mastodon to make minor announcements, in addition announcing
 major events such as the opening of a new IOCCC, or who won.</p>
 <p>See “<a href="faq.html#try_mastodon">FAQ 6.12: What is Mastodon and why does IOCCC use it?</a>” for more
 information on Mastodon.</p>
-<h1 id="section">2024-04-20</h1>
+<h2 id="section">2024-04-30</h2>
+<p>The web site now is viewing by mobile devices such as cell phones
+and tablets. Devices with a screen resolution 1024 pixels and
+narrower are given a <em>hamburger-style</em> menu icon in place of
+drop-down menus at the very top of the page (called the <em>topbar</em>).</p>
+<p>Any mobile device with a screen wider than 1024 pixels will need
+to <em>press and hold</em> to force the <em>topbar</em> pull-down menu to activate.</p>
+<p>We had to introduce the use of JavaScript to activate a <em>hamburger-style</em>
+menu icon due to the way mobile device screen touching works. Those
+devices without JavaScript (or when JavaScript has been disabled)
+will be given a link to a web page that presents the equivalent menu.</p>
+<p>Fixed generated HTML files where a link to a local file was invalid.
+Previous problems included malformed markdown, the local file was
+missing, the local file is generated by make or the entry itself, etc.</p>
+<p>The generated HTML files (via <code>bin</code> tools) and other HTML files are
+now conform with HTML 5 standards. The <strong>Nu Html Checker</strong> reports
+<strong>no error, warnings, nor info</strong> messages.</p>
+<p>The *Nu Html Checker<strong> change from <em>2024-04-20</em> is that the HTML
+files that are static (not generated <code>bin</code> tools) report </strong>no error,
+warnings, nor info** messages, changes involving fixing invalid
+links to local files have been corrected, and changes involving the
+<em>topbar</em> are now HTML 5 conforming.</p>
+<h2 id="section-1">2024-04-20</h2>
 <p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
 web site has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
 compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
@@ -400,10 +422,10 @@ glaring “<em>dancing bears</em>” and other frivolous web features.</p>
 where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
 will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC web site</a>.</p>
 <p>Stay tuned!</p>
-<h1 id="section-1">2024-02-29</h1>
+<h2 id="section-2">2024-02-29</h2>
 <p>We continue to make good progress on web site. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 4600 changes to date!</p>
 <p>All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the <a href="bin/index.html">bin</a> directory.</p>
-<h1 id="section-2">2023-05-22</h1>
+<h2 id="section-3">2023-05-22</h2>
 <p>We have been busy preparing for an important / significant update to this web site. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 2645 changes to date.</p>
 <p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
 please <strong>do not link to it</strong> as this repo and related web site will disappear once the main
@@ -459,7 +481,7 @@ that needs urgent fixing.
 The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
 who submit real IOCCC entries at risk.</p>
 <p>Stay tuned!</p>
-<h1 id="section-3">2023-01-30</h1>
+<h2 id="section-4">2023-01-30</h2>
 <p>We added to the
 <a href="status.json">status.json</a> page,
 a <em>“status_date”</em> JSON member whose value is the date
@@ -471,7 +493,7 @@ a <em>“latest_news”</em> JSON member whose value is the date
 of the most recent news item.</p>
 <pre><code>    &quot;status_date&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;,
     &quot;latest_news&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;</code></pre>
-<h1 id="section-4">2022-12-18</h1>
+<h2 id="section-5">2022-12-18</h2>
 <p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola</a>
 (_<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social_">@home.social_</span>) we now maintain a
 <a href="status.json">status.json</a> page on this web site.</p>
@@ -489,7 +511,7 @@ The details of such additional JSON members are <em>TBD</em>.</p>
 Instead you will have to rely on the additional JSON information
 and/or read the <a href="#news">IOCCC news</a>,
 and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
-<h1 id="section-5">2022-11-29</h1>
+<h2 id="section-6">2022-11-29</h2>
 <p>We are plan to abandon our
 <a href="https://twitter.com/ioccc">IOCCC Twitter feed</a>
 in favor of our new <a href="https://fosstodon.org/@ioccc">IOCCC Mastodon</a> feed.</p>
@@ -524,7 +546,7 @@ is made possible by volunteers,
 and those who voluntarily
 <a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
 <p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
-<h1 id="section-6">2022-11-19</h1>
+<h2 id="section-7">2022-11-19</h2>
 <p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
 <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
 a GitHub repo that includes the official iocccsize tool,
@@ -536,13 +558,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co
 judges will go through the motions (without judging the content) of an IOCCC:
 testing the above mentioned tools and testing the submit server.</p>
 <p>We are working on complete rebuild of this web site as well.</p>
-<h1 id="section-7">2022-01-15</h1>
+<h2 id="section-8">2022-01-15</h2>
 <p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
 <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
 a tool that is based on, and is containing, the official iocccsize tool,
 will form a compressed tarball that a registered IOCCC contestant
 will upload to the submit server (when the contest is open of course).</p>
-<h1 id="section-8">2021-12-27</h1>
+<h2 id="section-9">2021-12-27</h2>
 <p><a href="judges.html">The Judges</a>
 are continuing to work on re-tooling how we run the IOCCC.
 We are writing tools under various repositories our
@@ -551,7 +573,7 @@ We are writing tools under various repositories our
 Sorry for the delay, but we think you will appreciate the re-tooling
 when it is completed.
 Stay tuned!</p>
-<h1 id="section-9">2021-10-21</h1>
+<h2 id="section-10">2021-10-21</h2>
 <p><a href="judges.html">The Judges</a>
 are re-tooling how we run the IOCCC.
 Our goal is to build a smoother, more rapid process centered around