Improve bin/status2html.sh, update news + status

For the improvements to the script, besides a typo, a link to the FAQ (for submitting entries) has been added and a link to the GitHub issues page (the new issue page) has been added in the case where an unknown status appears in the status.json file. The news update is that more progress has been made in that one of the longer files to check for invalid links is done (thanks file) and that two long files are left but that instead of looking at those two first the other html files will be looked at first as it's quite possible that both will have to be updated in some way or another as the other files are being edited. Indeed this has happened numerous times already. This way will save time and prevent having to look at those files a second time. It also notes that some of the top level html files have also been reviewed (see below) and a link was fixed (added a <div id="news"> for a link that was linked to). I am fairly certain that I also fixed some formatting problems and some links were fixed as well. The status.md/status.html file has been updated with some links added, more div blocks (for each section describing the status.json file), which are used, slight formatting updates and possibly some other things as well. As for some of the links we might say that it's 'statuses all the way down' :-) With this commit I am happy to report that some other top level files have also been verified for invalid links: judges.html news.html status.html As the news.html file will be updated it is entirely possible that some fixes will have to be made but the links up to and including 08 June 2024 (unless more changes are made today of course) need not be checked again. More top level html files (which include those in next/ and other subdirectories that are not of the entries) also have to be checked but these should also go relatively quickly. Regenerated status.json file as the news has been updated.
2024-06-08 09:24:16 -07:00
1 parent 3a125b9fc2
commit 7e63c97ab1
@@ -383,20 +383,51 @@

 <!-- BEFORE: 1st line of markdown file: news.md -->
 <h1 id="for-more-news-try-mastodon">For more news, try mastodon</h1>
-<h3 id="please-follow-the-ioccc-on-mastodon">Please follow** the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
+<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 to 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>
-<h2 id="section">2024-05-30</h2>
+<h1 id="news">News</h1>
+<h2 id="section">2024-06-08</h2>
+<p>We continue to make good progress on the
+<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
+via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
+<p>One of the <a href="thanks-for-help.html">largest html
+files</a> has
+been checked for broken links which leaves two longer files to go. These two
+files are the <a href="bugs.html">bugs.html</a>
+file and the <a href="faq.html">FAQ</a>.</p>
+<p>However, where it was thought that those two files would be looked at before the
+other html files, it has been decided that they will be done after the other
+files as it is very possible that some things in these two files will have to be
+changed or added as the other files are reviewed for broken links.</p>
+<p>As of today, 08 June 2024, the top level html files are being looked at, with at
+least three done already (<a href="judges.html">judges.html</a>, <a href="news.html">news.html</a> and
+<a href="status.html">status.html</a>). This should not take more than a few days if things
+go as planned, as these files are small and should be relatively quick and easy
+to check for broken links. Of course, some of these, like the
+<a href="news.html">news.html</a> and possibly <a href="status.html">status.html</a> will likely have to be
+checked again but as for <a href="news.html">news.html</a> the dates up to and including <em>08
+June 2024</em> have been checked for invalid links so that only new news updates
+will have to be checked.</p>
+<p>Once those are done the html files of all the entries will be looked at. As
+those are being reviewed it the <a href="bugs.html">bugs.html</a> might very well be
+updated and the <a href="faq.html">FAQ</a> might be as well. This is why, as noted above,
+we have decided to review these files last, in order to save time and effort in
+not having to look at them more than once on a whole, other than possible
+entries that have to be added at the end, like the example below.</p>
+<p>Once the <em>submit server</em> server is ready another FAQ will be added and that
+entry can be looked at alone.</p>
+<h2 id="section-1">2024-05-30</h2>
 <p>A number of issues from minor fixes have been applied to the
 <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
 <p>437 commits have been applied since 2024-04-20, bringing the total
 number to 5260 commits to date. The
 <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a>
-repo is now 5159 commits ahead of the [IOCCC
-winner[(https://github.com/ioccc-src/winner) repo.</p>
+repo is now 5159 commits ahead of the <a href="https://github.com/ioccc-src/winner">IOCCC
+winner</a> repo.</p>
 <p>Multiple <strong>((top priority))</strong> issues have been resolved or completed.
 Only one <strong>((top priority))</strong> issue, <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2006">issue
 2006</a>
@@ -409,7 +440,7 @@ there are two more before we can look at the other files.</p>
 <p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2239">issue 2239</a>
 TODO list has 10 out of 51 sub-tasks completed. That might not
 seem like much progress, but keep in mind that some of those 10
-tasks look many months and thousands of commits to complete.
+tasks took many months and thousands of commits to complete.
 Moreover, most of the remaining 41 TODO items are short “checkbox”
 tasks. The final 31 TODO items are planned to be completed in about
 a single day.</p>
@@ -423,7 +454,7 @@ ask for beta testing of the new <strong>IOCCC registration process</strong> and
 This will speed up the start date of IOCCC28.</p>
 <p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
 IOCCC.</p>
-<h2 id="section-1">2024-04-30</h2>
+<h2 id="section-2">2024-04-30</h2>
 <p>The website 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
@@ -445,7 +476,7 @@ files that are static (not generated <code>bin</code> tools) report </strong>no
 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-2">2024-04-20</h2>
+<h2 id="section-3">2024-04-20</h2>
 <p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 website 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.
@@ -463,10 +494,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 website</a>
 will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p>
 <p>Stay tuned!</p>
-<h2 id="section-3">2024-02-29</h2>
+<h2 id="section-4">2024-02-29</h2>
 <p>We continue to make good progress on website. 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>
-<h2 id="section-4">2023-05-22</h2>
+<h2 id="section-5">2023-05-22</h2>
 <p>We have been busy preparing for an important / significant update to this website. 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 website will disappear once the main
@@ -522,7 +553,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>
-<h2 id="section-5">2023-01-30</h2>
+<h2 id="section-6">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
@@ -534,11 +565,11 @@ 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>
-<h2 id="section-6">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 website.</p>
-<p>In addition to the IOCCC-style <em>easter egg</em>, you may count on
+<h2 id="section-7">2022-12-18</h2>
+<p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola
+(<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social">@home.social</span>)</a>
+we now maintain a <a href="status.json">status.json</a> page on this website.</p>
+<p>In addition to the IOCCC-style <em>Easter egg</em>, you may count on
 the JSON status page having a JSON member with name of <strong>“contest”</strong>
 that will have a value of either <strong>“closed”</strong> or <strong>“open”</strong>.
 When a future <strong>IOCCC</strong> is announced or the IOCCC is currently open,
@@ -552,8 +583,8 @@ 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>
-<h2 id="section-7">2022-11-29</h2>
-<p>We are plan to abandon our
+<h2 id="section-8">2022-11-29</h2>
+<p>We are planning 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>
 <p>Our Mastodon username is: <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
@@ -577,7 +608,7 @@ Proving a Mastodon username will be entirely <strong>optional</strong>.</p>
 <p>If you do not yet have a Mastodon account, you may obtain a <strong>free mastodon account via</strong>:
 <a href="https://joinmastodon.org">joinmastodon.org</a>.</p>
 <p>If you do have / obtain a Mastodon account, <strong>please do us a favor and follow the IOCCC at</strong>:</p>
-<pre><code>    **@ioccc@fosstodon.org**</code></pre>
+<pre><code>    @ioccc@fosstodon.org</code></pre>
 <p>The IOCCC wishes to thank the good folk running the
 <a href="https://hub.fosstodon.org/about/">fosstodon.org</a>
 Mastodon hub.
@@ -587,7 +618,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>
-<h2 id="section-8">2022-11-19</h2>
+<h2 id="section-9">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,
@@ -599,13 +630,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 website as well.</p>
-<h2 id="section-9">2022-01-15</h2>
+<h2 id="section-10">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>
-<h2 id="section-10">2021-12-27</h2>
+<h2 id="section-11">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
@@ -614,7 +645,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>
-<h2 id="section-11">2021-10-21</h2>
+<h2 id="section-12">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