The IOCCC has a web site and now has a number of international mirrors. The +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
HIBACHI can server multiple -web sites from the same machine simply by creating content directories with the same +websites from the same machine simply by creating content directories with the same name as the URL domain names within the document root tree. Domain and/or IP aliases are simply symbolic links to content directories. There is never any need to restart HIBACHI -when web sites are published or aliases added. +when websites are published or aliases added. Assuming the server is running and that port 8008 is not blocked by any firewall, you should be able to access the server from the Internet using an IP or host name URL similar to:
@@ -253,7 +253,7 @@ and Cygwin.
-This example queries the Yahoo web site for a stock quote to insert into a web page.
+This example queries the Yahoo website for a stock quote to insert into a web page.
This example requires a browser with JavaScript support and
should work for all Unix variants and Cygwin, when Perl is installed.
The Windows PHP CGI binary distribution from the -PHP web site does not work within the Cygwin +PHP website does not work within the Cygwin environment. Instead, download the source distribution and build the PHP CGI and CLI versions from scratch from within Cygwin. The following commands were used to build: diff --git a/2004/hoyle/index.html b/2004/hoyle/index.html index 370a5ff4d..35018722e 100644 --- a/2004/hoyle/index.html +++ b/2004/hoyle/index.html @@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2004/index.html b/2004/index.html index 640a293ed..096a096c3 100644 --- a/2004/index.html +++ b/2004/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website @@ -392,7 +392,7 @@ on how to compile the entry and how to run the winning program. Look at the winning source and try to figure how it does what it does! You may then wish to look at the Author’s remarks for even more details. -The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at https://www.ioccc.org/.
Use make(1) to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at https://www.ioccc.org/.
Use make(1) to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
Most spam robots collect email addresses from the web sites of +
Most spam robots collect email addresses from the websites of
innocent people, like you. Conference organizers cannot disclose
the participant’s address to prevent malicious users from
grabbing them. One solution is to write as my_email _at_ address _dot_ com. But robots are clever enough to sort that out. A
diff --git a/2006/grothe/index.html b/2006/grothe/index.html
index e26beaa0e..aa113e4fb 100644
--- a/2006/grothe/index.html
+++ b/2006/grothe/index.html
@@ -138,7 +138,7 @@
The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux systems the Makefile needs to be changed. See the Makefile for details.
@@ -441,7 +441,7 @@ business travel, the death of an IOCCC judge’s mother, etc. that impacted our planned schedule for building the tarball of this year’s winning entries.During some of these forced delays, we took the time to better automate some of the tools needed to package the source for the winning entries to review -and to post the edited entries to the web site. It is our intent that +and to post the edited entries to the website. It is our intent that these changes made during those delays will make releasing future winning IOCCC entries a faster procedure.
p.s. The final advice given to Landon by his mom: “Have fun.” diff --git a/2014/maffiodo1/index.html b/2014/maffiodo1/index.html index 0e855f616..489769846 100644 --- a/2014/maffiodo1/index.html +++ b/2014/maffiodo1/index.html @@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2014/maffiodo2/index.html b/2014/maffiodo2/index.html index 83f78ce0f..349efbe95 100644 --- a/2014/maffiodo2/index.html +++ b/2014/maffiodo2/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2014/morgan/index.html b/2014/morgan/index.html index 06aece7fb..4aa0208a6 100644 --- a/2014/morgan/index.html +++ b/2014/morgan/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2014/sinon/index.html b/2014/sinon/index.html index d9c5dab1a..e7b22a2ac 100644 --- a/2014/sinon/index.html +++ b/2014/sinon/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2014/skeggs/index.html b/2014/skeggs/index.html index 6358e9e00..c7ec3ba2b 100644 --- a/2014/skeggs/index.html +++ b/2014/skeggs/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2014/vik/index.html b/2014/vik/index.html index e861c652e..27a9441e8 100644 --- a/2014/vik/index.html +++ b/2014/vik/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2014/wiedijk/index.html b/2014/wiedijk/index.html index dc940f6d3..6f0d14408 100644 --- a/2014/wiedijk/index.html +++ b/2014/wiedijk/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/README.md b/2015/README.md index be33c2870..5d8b79866 100644 --- a/2015/README.md +++ b/2015/README.md @@ -9,7 +9,7 @@ source and try to figure how it does what it does! You may then wish to look at the Author's remarks for even more details. This year we included most of the information included by the submitter. -The IOCCC has a web site and now has a number of international mirrors. +The IOCCC has a website and now has a number of international mirrors. The primary site can be found at [www.ioccc.org](https://www.ioccc.org). Use `make` to compile entries. It is possible that on non-Unix / non-Linux diff --git a/2015/burton/index.html b/2015/burton/index.html index 1ece29dcd..d75bd9967 100644 --- a/2015/burton/index.html +++ b/2015/burton/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/burton/road.to.obscurity.html b/2015/burton/road.to.obscurity.html index 7e575964b..b0b00cd62 100644 --- a/2015/burton/road.to.obscurity.html +++ b/2015/burton/road.to.obscurity.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/burton/spoilers.html b/2015/burton/spoilers.html index 767381cc0..e13f4dfcd 100644 --- a/2015/burton/spoilers.html +++ b/2015/burton/spoilers.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/dogon/index.html b/2015/dogon/index.html index 985cce1bd..e34309905 100644 --- a/2015/dogon/index.html +++ b/2015/dogon/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/duble/index.html b/2015/duble/index.html index 190fa5f62..101da92d3 100644 --- a/2015/duble/index.html +++ b/2015/duble/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/endoh1/index.html b/2015/endoh1/index.html index 8482fb4b5..16f8b42f9 100644 --- a/2015/endoh1/index.html +++ b/2015/endoh1/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/endoh2/index.html b/2015/endoh2/index.html index b7eb8a4bf..5f64e08f2 100644 --- a/2015/endoh2/index.html +++ b/2015/endoh2/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/endoh3/index.html b/2015/endoh3/index.html index 336abbaf1..9e4c165db 100644 --- a/2015/endoh3/index.html +++ b/2015/endoh3/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/endoh4/index.html b/2015/endoh4/index.html index f3d36c009..2bd6425cd 100644 --- a/2015/endoh4/index.html +++ b/2015/endoh4/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/guidelines.txt b/2015/guidelines.txt index f6947458c..612a7e6c6 100644 --- a/2015/guidelines.txt +++ b/2015/guidelines.txt @@ -78,8 +78,8 @@ End of important 2023 update to this historic note. | will be available and active on or slightly before the start of this IOCCC. | | The official rules, guidelines and iocccsize.c tool will be available -| on the official IOCCC web site on or slightly before start of this IOCCC. -| Please check the IOCCC web site "How to enter" link: +| on the official IOCCC website on or slightly before start of this IOCCC. +| Please check the IOCCC website "How to enter" link: | | https://www.ioccc.org/index.html#enter | @@ -703,7 +703,7 @@ by a git commit to the IOCCC entries repo: https://github.com/ioccc-src/winner -that, in turn, updates the offivial IOCCC web site: +that, in turn, updates the offivial IOCCC website: https://www.ioccc.org/index.html @@ -827,7 +827,7 @@ by a git commit to the IOCCC entries repo: https://github.com/ioccc-src/winner -that, in turn, updates the offivial IOCCC web site: +that, in turn, updates the offivial IOCCC website: https://www.ioccc.org/index.html @@ -850,7 +850,7 @@ End of important 2023 update to this historic note. The judges will then post an initial announcement of who won, the name of their award, and a very brief description of the winning entry - on the IOCCC web site: + on the IOCCC website: https://www.ioccc.org/whowon.html @@ -867,7 +867,7 @@ End of important 2023 update to this historic note. Sometime after the initial announcement, and once the review by the winners has been completed, the winning source will be - posted to the IOCCC web site: + posted to the IOCCC website: https://www.ioccc.org/years.html @@ -883,7 +883,7 @@ by a git commit to the IOCCC entries repo: https://github.com/ioccc-src/winner -that, in turn, updates the offivial IOCCC web site: +that, in turn, updates the offivial IOCCC website: https://www.ioccc.org/index.html diff --git a/2015/hou/index.html b/2015/hou/index.html index 4858b88ff..91324cf15 100644 --- a/2015/hou/index.html +++ b/2015/hou/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/howe/index.html b/2015/howe/index.html index 218322cf5..e24ea0320 100644 --- a/2015/howe/index.html +++ b/2015/howe/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/2015/index.html b/2015/index.html index 447fbe77d..4d126d3b9 100644 --- a/2015/index.html +++ b/2015/index.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website @@ -393,7 +393,7 @@ compile the entry and how to run the winning program. Look at the winning source and try to figure how it does what it does! You may then wish to look at the Author’s remarks for even more details. This year we included most of the information included by the submitter. -The IOCCC has a web site and now has a number of international mirrors. +
The IOCCC has a website and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
Please visit www.ioccc.org for the official IOCCC web site.
-Please do NOT bookmark or link to this experimental web site.
+Please visit www.ioccc.org for the official IOCCC website.
+Please do NOT bookmark or link to this experimental website.
When this experiment is finished, this site will go away!
This test web tree is part of the temp-test-ioccc GitHub repo.
-This web site will be undergoing major changes, so expect many +
This website will be undergoing major changes, so expect many broken links, typos and other problems. If you wish to recommend changes (understanding that things may be rapidly changing out from under your copy), then consider making pull requests against the @@ -415,7 +415,7 @@ mealy-mouthed denials and obfuscations.
late Middle English: from late Latin obfuscatio(n-), from obfuscare ‘to darken or obscure’ (see obfuscate).
-The official IOCCC web site is www.ioccc.org.
+The official IOCCC website is www.ioccc.org.
The original inspiration of the International Obfuscated C Code Contest came
from the Bourne Shell source and the finger(1) command as distributed in
diff --git a/README.md b/README.md
index 7fda3d377..6fd3ef5d8 100644
--- a/README.md
+++ b/README.md
@@ -1,15 +1,15 @@
-### This is NOT the official IOCCC web site!
+### This is NOT the official IOCCC website!
-Please visit [www.ioccc.org](https://www.ioccc.org) for the official **IOCCC** web site.
+Please visit [www.ioccc.org](https://www.ioccc.org) for the official **IOCCC** website.
-Please do NOT bookmark or link to this [experimental web site](https://ioccc-src.github.io/temp-test-ioccc/).
+Please do NOT bookmark or link to this [experimental website](https://ioccc-src.github.io/temp-test-ioccc/).
When this experiment is finished, this site will go away!
This test web tree is part of the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc).
-This web site will be undergoing major changes, so expect many
+This website will be undergoing major changes, so expect many
broken links, typos and other problems. If you wish to recommend
changes (understanding that things may be rapidly changing out from
under your copy), then consider making pull requests against the
@@ -42,7 +42,7 @@ mealy-mouthed denials and obfuscations.
late Middle English: from late Latin **obfuscatio(n-)**, from **obfuscare**
'to darken or obscure' (see *obfuscate*).
-The official IOCCC web site is [www.ioccc.org](https://www.ioccc.org).
+The official IOCCC website is [www.ioccc.org](https://www.ioccc.org).
## How it was started:
diff --git a/archive/historic/index.html b/archive/historic/index.html
index a0c90fbd5..70e2d8b3e 100644
--- a/archive/historic/index.html
+++ b/archive/historic/index.html
@@ -138,7 +138,7 @@
The bin directory holds tools that build files, such as HTML -content, for the official IOCCC web site.
+content, for the official IOCCC website.For HTML content, the bin directory tools make use of HTML fragments from the inc directory as well as various JSON files and other content from the IOCCC GitHub @@ -445,7 +445,7 @@ files.
Usage:
bin/gen-other-html.sh -v 1Generate an XML sitemap for the IOCCC web site.
+Generate an XML sitemap for the IOCCC website.
Usage:
bin/gen-sitemap.sh -v 1We recommend that this tool be invoked via the top level Makefile:
news.html.
We recommend that this tool be invoked via the top level Makefile:
make gen_statusGenerate a number of top level HTML pages for the IOCCC web sites.
+Generate a number of top level HTML pages for the IOCCC websites.
Usage:
bin/gen-top-html.sh -v 1Examples of top level HTML pages built by this tool include:
@@ -748,9 +748,9 @@ See also, the tool readme2index.sh for an e how such command lines are used.Some of the files under this directory are used to form MOST of the HTML content -on the official IOCCC web site.
+on the official IOCCC website.These files are used to form MOST of the HTML content -on the experimental web site.
+on the experimental website.… and in particular files under inc that are of the form (called default HTML files) …:
*.default.htmlHere are some reasons why we are using these files and special tools to create HTML content / IOCCC web pages:
-We host official IOCCC web site via GitHub
+ We host official IOCCC website via GitHub
pages. As of the time this file written, only
static web pages are supported.We cannot use server side include
@@ -793,7 +793,7 @@ only to find that the generous benefactor moves on, or their service is purchase
by someone else who is not so generous. While it is possible that GitHub might someday
suffer a similar fate, for the time being we are betting that GitHub will remain
willing to host the IOCCC.
The official IOCCC web site is, after all, primarily C +
The official IOCCC website is, after all, primarily C source code with some supporting documentation (sometimes :-) ). As such it is a natural fit for GitHub and GitHub pages.
<object> elementWe do not use JavaScript to include HTML content.
While the IOCCC may use JavaScript in the future to directly render things like C source code, we will do so in such a way that someone will be able to view -official IOCCC web site content with JavaScript +official IOCCC website content with JavaScript disabled.
The IOCCC will NOT MANDATE USE OF JavaScript to view official IOCCC web site.
diff --git a/bin/md2html.sh b/bin/md2html.sh index 57d58976f..85f595fed 100755 --- a/bin/md2html.sh +++ b/bin/md2html.sh @@ -2,7 +2,7 @@ # # md2html.sh - convert markdown into an IOCCC HTML file via config file # -# Convert a markdown file into a HTML file for the IOCCC web site, +# Convert a markdown file into a HTML file for the IOCCC website, # using the inc/md2html.cfg configuration file. Conversion from # markdown to HTML is performed via the 'pandoc wrapper tool'. # @@ -228,7 +228,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] NOTE: The '-u repo_url' is passed as leading options on -b tool, -a tool, and -o tool command lines. -U url URL of HTML being formed (def: $URL) NOTE: The '-U url' is passed as leading options on -b tool, -a tool, and -o tool command lines. - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -m mdtag string to write about the markdown file used to form HTML content (def: no markdown file is used) -e string output 'string', followed by newline, to stderr (def: do not) diff --git a/bin/output-index-author.sh b/bin/output-index-author.sh index 673c0946d..5401f873b 100755 --- a/bin/output-index-author.sh +++ b/bin/output-index-author.sh @@ -144,7 +144,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bin/output-index-inventory.sh b/bin/output-index-inventory.sh index 27cb63e33..ca67861bb 100755 --- a/bin/output-index-inventory.sh +++ b/bin/output-index-inventory.sh @@ -144,7 +144,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bin/output-year-index.sh b/bin/output-year-index.sh index 6e7460a2d..9a41637b2 100755 --- a/bin/output-year-index.sh +++ b/bin/output-year-index.sh @@ -149,7 +149,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bin/quick-readme2index.sh b/bin/quick-readme2index.sh index 103187920..36d21bd08 100755 --- a/bin/quick-readme2index.sh +++ b/bin/quick-readme2index.sh @@ -158,7 +158,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) NOTE: The '-u repo_url' is passed as leading options on tool command lines. - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) NOTE: The '-w site_url' is passed as leading options on tool command lines. tool the tool to run over all entries diff --git a/bin/readme2index.sh b/bin/readme2index.sh index 98d8fe237..bba883c17 100755 --- a/bin/readme2index.sh +++ b/bin/readme2index.sh @@ -149,7 +149,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) NOTE: The '-u repo_url' is passed as leading options on tool command lines. - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) NOTE: The '-w site_url' is passed as leading options on tool command lines. YYYY/dir path from topdir to entry directory: must contain the files: README.md, .path and .entry.json diff --git a/bin/status2html.sh b/bin/status2html.sh index 40e6c316a..d9bd53a1c 100755 --- a/bin/status2html.sh +++ b/bin/status2html.sh @@ -141,7 +141,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bin/subst.default.sh b/bin/subst.default.sh index 7b42e91b5..4d802d12a 100755 --- a/bin/subst.default.sh +++ b/bin/subst.default.sh @@ -132,7 +132,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-D docroot/] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bin/subst.entry-index.sh b/bin/subst.entry-index.sh index a9442c145..aef08ea71 100755 --- a/bin/subst.entry-index.sh +++ b/bin/subst.entry-index.sh @@ -142,7 +142,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bin/subst.year-index.sh b/bin/subst.year-index.sh index fbbaeb892..e2b7cbb7b 100755 --- a/bin/subst.year-index.sh +++ b/bin/subst.year-index.sh @@ -142,7 +142,7 @@ export USAGE="usage: $0 [-h] [-v level] [-V] [-d topdir] [-n] [-N] -u repo_url Base level URL of target git repo (def: $REPO_URL) -U url URL of HTML file being formed (def: $URL) - -w site_url Base URL of the web site (def: $SITE_URL) + -w site_url Base URL of the website (def: $SITE_URL) -e string output string, followed by newline, to stderr (def: do not) -E exitcode force exit with exitcode (def: exit based on success or failure of the action) diff --git a/bugs.html b/bugs.html index e63495c49..6003358cd 100644 --- a/bugs.html +++ b/bugs.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website diff --git a/contact.html b/contact.html index dac197e35..33cc92a15 100644 --- a/contact.html +++ b/contact.html @@ -138,7 +138,7 @@ @@ -283,7 +283,7 @@ - Fixing the web site + Fixing the website @@ -387,7 +387,7 @@Instead of sending us Email, Please consider using the GitHub pull request process @@ -396,7 +396,7 @@ of the ioccc-src/winner repo.<
If you are trying to:
Instead first look at the IOCCC
diff --git a/contact.md b/contact.md
index 4180abb4f..ae592a704 100644
--- a/contact.md
+++ b/contact.md
@@ -4,7 +4,7 @@ If you are trying to:
* **Fix a winning IOCCC entry** - See [FAQ 5.2](faq.html#fix_an_entry)
* **Update winning author information** - See [FAQ 5.5](faq.html#fix_author)
-* **Correct a web site problem** - See [FAQ 5.4](faq.html#fix_web_site) or [FAQ 5.6](faq.html#fix_link)
+* **Correct a website problem** - See [FAQ 5.4](faq.html#fix_web_site) or [FAQ 5.6](faq.html#fix_link)
Instead of sending us Email, **Please** consider using the [GitHub
pull request](https://github.com/ioccc-src/winner/pulls) process
@@ -14,7 +14,7 @@ of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner).
If you are trying to:
* **Report a bug in an IOCCC winning entry** - See [FAQ 5.1](faq.html#report_bug)
-* **Report an IOCCC web site problem** - See [FAQ 5.3](faq.html#report_web_problem)
+* **Report an IOCCC website problem** - See [FAQ 5.3](faq.html#report_web_problem)
* **Report a broken or wrong web link** - See [FAQ 5.6](faq.html#fix_link)
Instead first look at the [IOCCC
diff --git a/faq.html b/faq.html
index 4d61db417..b26549320 100644
--- a/faq.html
+++ b/faq.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -397,7 +397,7 @@
Section 2 - IOCCC Judging process
@@ -451,8 +451,8 @@ other inconsistencies with the original entry?
README.md markdown file
as the basis for forming the index.html web page for that entry.
-All generated HTML pages on the Official IOCCC web site
+All generated HTML pages on the Official IOCCC website
start with some markdown content.
IMPORTANT: Please read the IOCCC markdown best practices guide as it lists things you should not use in markdown files.
@@ -812,12 +812,12 @@ do not permit us to hold a new IOCCC.The pause during the 2021-2023 period was due to the IOCCC judges developing tools to make is much more likely for the IOCCC to be held in a yearly basis later on.
The long history of the official IOCCC web site can be +
The long history of the official IOCCC website can be viewed at the Internet Wayback Machine Wayback Machine.
-One can view several thousand snapshots showing how the IOCCC web site has
+ One can view several thousand snapshots showing how the IOCCC website has
evolved going back
as far as 1998 Dec 12
www.ioccc.org.
Furthermore, a bzip2 compressed tarball containing the released IOCCC entry source code may be found under the @@ -853,7 +853,7 @@ and then on Wed Dec 30 16:57:03 2020 -0800 added a preview of c0663537cb88d39b74285a930ff1a668c6d5968b.
On 2020 Dec 30, with commit c0663537cb88d39b74285a930ff1a668c6d5968b, -the official IOCCC web site of 2022 Dec +the official IOCCC website of 2022 Dec 29 was uploaded into the Official IOCCC winner repo.
@@ -897,11 +897,11 @@ and IOCCC judge made edits to their local repository with occasional pushes to the Official IOCCC winner repo and the Official -www.ioccc.org web site. After +www.ioccc.org website. After that time and until the Great Fork Merge, very few changes were made to the Official IOCCC winner repo and the Official -www.ioccc.org web site most of +www.ioccc.org website most of which were news updates.While the temp-test-ioccc repo has history @@ -911,11 +911,11 @@ the repo was forked on Sun Sep 18 17:30:00 2022 -0700. The first push into the temp-test-ioccc repo occurred on Sun Sep 18 11:15:49 2022 -0700.
-At this same time, the temp-test-ioccc web site went live.
+At this same time, the temp-test-ioccc website went live.
Edits were made by an IOCCC judge to their local git repository and were pushed into the temp-test-ioccc repo -and to the temp-test-ioccc web site.
+and to the temp-test-ioccc website.The first accepted pull request made directly to the temp-test-ioccc repo on @@ -955,7 +955,7 @@ request. gen-years.sh tool.
winners.html, via the gen-authors.sh tool.On 202y mm dd, the temporary repo was merged back into the IOCCC winner repo resulting in many, many substantial improvements -to the official IOCCC web site.
+to the official IOCCC website.Announce who are authors of this year’s winning IOCCC entries via the @IOCCC mastodon feed.
Upload the winning code to the Official IOCCC winner repo
Update the Official IOCCC web site, and in particular +
Update the Official IOCCC website, and in particular display this year’s winning IOCCC entries at the top of the IOCCC winning entries page.
Update the IOCCC news page.
See the Wayland web site for more details.
+See the Wayland website for more details.
IMPORTANT NOTE: We do NOT know if IOCCC entries will run under Wayland. Some IOCCC entries that use X11 might be OK while other IOCCC entries that use X11 in an unusual way might fail under Wayland.
@@ -1415,7 +1415,7 @@ may be helpful: See the above note for details.First, see the above note on installing and starting Xorg.
-See the X.org foundation web site.
+See the X.org foundation website.
IMPORTANT NOTE: The X.org server has been deprecated. See the above note for details.
Although one can clone the entire winner -repo to get the entire web site and all +repo to get the entire website and all entries, we also provide, as a convenience, a way to download individual entries as well as a way to download a year’s winning entries.
Please note that some of the links in the html files will not work! This is because you are not downloading the full website. If you want to view the entry with links intact you should clone the repo or view it on the official IOCCC -web site instead.
+website instead.The individual entry tarballs are named in the form of
YYYY/winner/YYYY_winner.tar.bz2 (e.g.
@@ -2127,7 +2127,7 @@ could no longer be so: main() instead had to call another function
the body of the old main() and that function would call itself again. In some
cases, however, this had to be done even without clang objections.
If you discover a problem with the IOCCC web site that is related +
If you discover a problem with the IOCCC website that is related to a particular IOCCC entry, please see FAQ 5.1 for information about reporting a bug in an IOCCC entry, and see FAQ 5.2 for information on how to submit a fix to an IOCCC entry.
-If you discover a problem with the IOCCC web site (such as a broken link, which +
If you discover a problem with the IOCCC website (such as a broken link, which may or may not be specific to a particular IOCCC entry) that is not related to a particular IOCCC entry, the best way you can help is to submit a fix to -the IOCCC web site. See FAQ 5.4 for information on submitting fixes -to the IOCCC web site.
-If you do not have a IOCCC web site fix, and just wish to report a -general IOCCC web site problem, we ask that you first look at the +the IOCCC website. See FAQ 5.4 for information on submitting fixes +to the IOCCC website.
+If you do not have a IOCCC website fix, and just wish to report a
+general IOCCC website problem, we ask that you first look at the
IOCCC issues to see
if the problem has already been reported. If it has been reported,
feel free to add a comment to the issue. If you do not find an it
@@ -2227,10 +2227,10 @@ has been reported, then fee free to open a
-
FAQ 5.4: How may I submit a fix to the IOCCC web site?
+FAQ 5.4: How may I submit a fix to the IOCCC website?
For IOCCC web site problems that relate to a particular IOCCC entry, please +
For IOCCC website problems that relate to a particular IOCCC entry, please see FAQ 5.2 for information on how submit a fix to an IOCCC entry.
You may open a GitHub pull request against the master branch @@ -2241,7 +2241,7 @@ entry. See also the FAQ 6.10 How does someone make a change to a file and submit that change as a GitHub pull request for more information about pull requests.
Nearly all HTML files on the IOCCC web site +
Nearly all HTML files on the IOCCC website are built from markdown files. If you see lines containing:
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
@@ -2377,7 +2377,7 @@ variety of kinds.
not an issue and note that some issues are simply missing files, dead URL(s) or
something like that.
-FAQ 6.2: May I mirror the IOCCC web site?
+FAQ 6.2: May I mirror the IOCCC website?
We are not accepting mirror requests at this time, sorry. However you are free to fork the IOCCC winner repo. We do ask that your fork keep up to date with the latest changes when possible.
@@ -2476,7 +2476,7 @@ in the case of bin directory tool
-to help build HTML content for the official IOCCC web site.
+to help build HTML content for the official IOCCC website.
For example, the index.html file for each IOCCC entry contains
selected information about the authors. Tools from the bin directory
use the content of these JSON files to generate the index.html files for each IOCCC
@@ -2551,7 +2551,7 @@ be the exact JSON string as shown above.
As of Thu Nov 30 23:51:12 UTC 2023, the JSON value MUST be “1.0 2023-06-10”.
The author_JSON_format_version would only changed when the overall format
of the these files is modified: and then only those who maintain the
-official IOCCC web site would be the one to do this
+official IOCCC website would be the one to do this
in conjunction with changes to bin directory tools.
author_handle
"author_handle" : "Yusuke_Endoh",
@@ -2702,7 +2702,7 @@ information on Mastodon.
be a JSON string or it MUST be a JSON null. The github JSON string MUST
start with an at sign (_@_) and MUST be a valid GitHub username.
The IOCCC uses GitHub to hold the official winner repo of the IOCCC,
-and hosts official IOCCC web site on GitHub pages.
+and hosts official IOCCC website on GitHub pages.
The IOCCC GitHub handle is:
@ioccc-src
If the author wishes to not specify an GitHub handle, or if the GitHub handle is
diff --git a/faq.md b/faq.md
index e18247601..618a2e472 100644
--- a/faq.md
+++ b/faq.md
@@ -14,7 +14,7 @@
## Section 1 - [History of the IOCCC](#faq1)
- [1.0 - How did the IOCCC get started?](#faq1_0)
- [1.1 - Why are some years missing IOCCC entries?](#faq1_1)
-- [1.2 - What is the history of the IOCCC web site?](#faq1_2)
+- [1.2 - What is the history of the IOCCC website?](#faq1_2)
- [1.3 - How has the IOCCC size limit rule changed over the years?](#faq1_3)
@@ -68,8 +68,8 @@ other inconsistencies with the original entry?](#faq4_3)
- [5.0 - How may I help the IOCCC?](#faq5_0)
- [5.1 - How do I report a bug in an IOCCC entry?](#faq5_1)
- [5.2 - How may I submit a fix to an IOCCC entry?](#faq5_2)
-- [5.3 - How may I report an IOCCC web site problem?](#faq5_3)
-- [5.4 - How may I submit a fix to the IOCCC web site?](#faq5_4)
+- [5.3 - How may I report an IOCCC website problem?](#faq5_3)
+- [5.4 - How may I submit a fix to the IOCCC website?](#faq5_4)
- [5.5 - How may I correct or update IOCCC author information?](#faq5_5)
- [5.6 - What should I do if I find a broken or wrong web link?](#faq5_6)
@@ -77,7 +77,7 @@ other inconsistencies with the original entry?](#faq4_3)
## Section 6 - [Miscellaneous IOCCC](#faq6)
- [6.0 - How did an entry that breaks the size rule 2 win the IOCCC?](#faq6_0)
- [6.1 - Is there a list of known bugs and (mis)features of IOCCC entries?](#faq6_1)
-- [6.2 - May I mirror the IOCCC web site?](#faq6_2)
+- [6.2 - May I mirror the IOCCC website?](#faq6_2)
- [6.3 - May I use parts of the IOCCC in an article, book, newsletter, or instructional material?](#faq6_3)
- [6.4 - Why do you sometimes use the first person plural?](#faq6_4)
- [6.5 - What is an author handle?](#faq6_5)
@@ -467,7 +467,7 @@ For example, we [submitting to the IOCCC](faq.html#submit), we have people
to submit remarks about entry in markdown format. Every
[winning IOCCC entry](years.html) uses a `README.md` markdown file
as the basis for forming the `index.html` web page for that entry.
-All generated HTML pages on the [Official IOCCC web site](https://www.ioccc.org/index.html)
+All generated HTML pages on the [Official IOCCC website](https://www.ioccc.org/index.html)
start with some markdown content.
**IMPORTANT**: Please read the [IOCCC markdown best practices](markdown.html) guide
@@ -576,15 +576,15 @@ make is much more likely for the IOCCC to be held in a yearly basis later on.
-### FAQ 1.2: What is the history of the IOCCC web site?
+### FAQ 1.2: What is the history of the IOCCC website?
#### In the beginning of www.ioccc.org
-The long history of the [official IOCCC web site](https://www.ioccc.org) can be
+The long history of the [official IOCCC website](https://www.ioccc.org) can be
viewed at the [Internet Wayback Machine Wayback Machine](https://web.archive.org).
-One can [view several thousand snapshots showing how the IOCCC web site has
+One can [view several thousand snapshots showing how the IOCCC website has
evolved](https://web.archive.org/web/20230000000000*/www.ioccc.org) going back
as far as [1998 Dec 12
www.ioccc.org](https://web.archive.org/web/19981212030016/https://www.ioccc.org/).
@@ -593,7 +593,7 @@ On 2020 Dec 31, the IOCCC source tree was moved to the [IOCCC winner
repo](https://web.archive.org/web/20210101211346/https://www.ioccc.org/) on
[GitHub](https://github.com). From this point on, the [official IOCCC web
site](https://www.ioccc.org) became a [GitHub Pages](https://pages.github.com)
-web site.
+website.
#### 2020 Dec 28 bzip2 compressed tarball archive
@@ -631,7 +631,7 @@ c0663537cb88d39b74285a930ff1a668c6d5968b](https://github.com/ioccc-src/winner/co
On 2020 Dec 30, with [commit
c0663537cb88d39b74285a930ff1a668c6d5968b](https://github.com/ioccc-src/winner/commit/c0663537cb88d39b74285a930ff1a668c6d5968b),
-the [official IOCCC web site of 2022 Dec
+the [official IOCCC website of 2022 Dec
29](https://web.archive.org/web/20221231001721/https://www.ioccc.org/) was
uploaded into the [Official IOCCC winner
repo](https://github.com/ioccc-src/winner).
@@ -686,11 +686,11 @@ and [Sat Jan 29 21:56:53 2022
an [IOCCC judge](https://www.ioccc.org/judges.html) made edits to
their local repository with occasional pushes to the [Official IOCCC winner
repo](https://github.com/ioccc-src/winner) and the [Official
-www.ioccc.org web site](https://www.ioccc.org/index.html). After
+www.ioccc.org website](https://www.ioccc.org/index.html). After
that time and until the **Great Fork Merge**, very few changes
were made to the [Official IOCCC winner
repo](https://github.com/ioccc-src/winner) and the [Official
-www.ioccc.org web site](https://www.ioccc.org/index.html) most of
+www.ioccc.org website](https://www.ioccc.org/index.html) most of
which were news updates.
While the [temp-test-ioccc
@@ -702,12 +702,12 @@ first [push into the temp-test-ioccc
repo](https://github.com/ioccc-src/temp-test-ioccc/commit/edbc3089e1b755d85a020af7975bbc7df3737a5f)
occurred on Sun Sep 18 11:15:49 2022 -0700.
-At this same time, the [temp-test-ioccc web site](https://ioccc-src.github.io/temp-test-ioccc/) went live.
+At this same time, the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/) went live.
Edits were made by an [IOCCC judge](https://www.ioccc.org/judges.html)
to their local [git](https://git-scm.com) repository and [were pushed into the temp-test-ioccc
repo](https://github.com/ioccc-src/temp-test-ioccc/commit/2f20ae8451ada03f4601ac727d10e1d8630861a8)
-and to the [temp-test-ioccc web site](https://ioccc-src.github.io/temp-test-ioccc/).
+and to the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/).
The [first accepted pull request](https://github.com/ioccc-src/temp-test-ioccc/pull/15)
made directly to the [temp-test-ioccc
@@ -750,7 +750,7 @@ request](https://github.com/ioccc-src/winner/pulls).
[gen-years.sh](%%REPO_URL%%/bin/gen-years.sh) tool.
* Setting up to generate the top level [authors.html file](authors.html), renamed
from `winners.html`, via the [gen-authors.sh](%%REPO_URL%%/bin/gen-authors.sh) tool.
-* Making use of a new and improved [IOCCC CSS](%%REPO_URL%%/ioccc.css) for web site consistency
+* Making use of a new and improved [IOCCC CSS](%%REPO_URL%%/ioccc.css) for website consistency
* Etc.
#### 202y mm dd The Great Fork Merge
@@ -762,7 +762,7 @@ of the [IOCCC winner repo](https://github.com/ioccc-src/winner).
On 202y mm dd, the temporary repo was merged back into the [IOCCC winner
repo](https://github.com/ioccc-src/winner) resulting in many, many substantial improvements
-to the [official IOCCC web site](https://www.ioccc.org).
+to the [official IOCCC website](https://www.ioccc.org).
@@ -979,7 +979,7 @@ feed](https://fosstodon.org/@ioccc).
* Upload the winning code to the [Official IOCCC winner repo](https://github.com/ioccc-src/winner)
-* Update the [Official IOCCC web site](index.html), and in particular
+* Update the [Official IOCCC website](index.html), and in particular
display this year's winning IOCCC entries at the top of the [IOCCC
winning entries page](years.html).
@@ -1239,7 +1239,7 @@ sharing might not work sometime, but it is the future. Fedora, also developed by
RHEL, has switched to a Wayland session as it’s default windowing system (And it
works flawlessly on my Laptop).
-See the [Wayland](https://wayland.freedesktop.org) web site for more details.
+See the [Wayland](https://wayland.freedesktop.org) website for more details.
**IMPORTANT NOTE**: We do **NOT** know if IOCCC entries will run under
**Wayland**. Some IOCCC entries that use X11 might be OK while other IOCCC
@@ -1375,7 +1375,7 @@ See the above note for details.
First, see the above note on [installing and starting Xorg](#X11_general).
-See the [X.org](https://x.org/wiki/) foundation web site.
+See the [X.org](https://x.org/wiki/) foundation website.
**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated).
See the above note for details.
@@ -2200,14 +2200,14 @@ though of course for both you may specify a rule or rules to run.
Although one can clone the entire [winner
-repo](https://github.com/ioccc-src/winner) to get the entire web site and all
+repo](https://github.com/ioccc-src/winner) to get the entire website and all
entries, we also provide, as a convenience, a way to download individual entries
as well as a way to download a year's winning entries.
Please note that some of the links in the html files will not work! This is
because you are not downloading the full website. If you want to view the entry
with links intact you should clone the repo or view it on the [official IOCCC
-web site](https://www.ioccc.org) instead.
+website](https://www.ioccc.org) instead.
#### Individual winning entry tarballs
@@ -2551,7 +2551,7 @@ cases, however, this had to be done even without `clang` objections.
-## Section 5: Updating or correcting IOCCC web site content
+## Section 5: Updating or correcting IOCCC website content
@@ -2575,7 +2575,7 @@ while a (mis)feature is not considered a bug and should **not be fixed**.
In cases where the bug is known, the entry's [known bugs](bugs.html) file
section may offer you important fixing clues.
-### We welcome your help on fixing the IOCCC web site
+### We welcome your help on fixing the IOCCC website
@@ -2655,23 +2655,23 @@ have the final say in the matter.
-### FAQ 5.3: How may I report an IOCCC web site problem?
+### FAQ 5.3: How may I report an IOCCC website problem?
-If you discover a problem with the IOCCC web site that is related
+If you discover a problem with the IOCCC website that is related
to a particular IOCCC entry, please see [FAQ 5.1](#report_bug) for
information about reporting a bug in an IOCCC entry, and see [FAQ
5.2](#fix_an_entry) for information on how to submit a fix to an IOCCC entry.
-If you discover a problem with the IOCCC web site (such as a broken link, which
+If you discover a problem with the IOCCC website (such as a broken link, which
may or may not be specific to a particular IOCCC entry) that is **not related
to a particular IOCCC entry**, the best way you can help is to submit a fix to
-the IOCCC web site. See [FAQ 5.4](#fix_web_site) for information on submitting fixes
-to the IOCCC web site.
+the IOCCC website. See [FAQ 5.4](#fix_web_site) for information on submitting fixes
+to the IOCCC website.
-If you do not have a IOCCC web site fix, and just wish to report a
-general IOCCC web site problem, we ask that you first look at the
+If you do not have a IOCCC website fix, and just wish to report a
+general IOCCC website problem, we ask that you first look at the
[IOCCC issues](https://github.com/ioccc-src/winner/issues) to see
if the problem has already been reported. If it has been reported,
feel free to add a comment to the issue. If you do not find an it
@@ -2681,11 +2681,11 @@ issue](https://github.com/ioccc-src/winner/issues).
-### FAQ 5.4: How may I submit a fix to the IOCCC web site?
+### FAQ 5.4: How may I submit a fix to the IOCCC website?
-For IOCCC web site problems that relate to a particular IOCCC entry, please
+For IOCCC website problems that relate to a particular IOCCC entry, please
see [FAQ 5.2](#fix_an_entry) for information on how submit a fix to an IOCCC entry.
You may open a [GitHub pull request](https://github.com/ioccc-src/winner/pulls)
@@ -2700,7 +2700,7 @@ request](#ull_request) for more information about pull requests.
#### Some HTML files should NOT be directly modified
-Nearly all HTML files on the [IOCCC web site](https://www.ioccc.org)
+Nearly all HTML files on the [IOCCC website](https://www.ioccc.org)
are built from [markdown](https://daringfireball.net/projects/markdown/) files.
If you see lines containing:
@@ -2900,7 +2900,7 @@ something like that.
-### FAQ 6.2: May I mirror the IOCCC web site?
+### FAQ 6.2: May I mirror the IOCCC website?
We are not accepting mirror requests at this time, sorry. However you are free to fork the [IOCCC winner repo](https://github.com/ioccc-src/winner). We do ask that your fork keep up to date with the latest changes when possible.
@@ -3049,7 +3049,7 @@ information about authors of IOCCC entries and is used to help form
HTML files as well to contact an author.
The content of these JSON files are used by tools from a [bin directory tool](bin/index.html)
-to help build HTML content for the [official IOCCC web site](https://www.ioccc.org).
+to help build HTML content for the [official IOCCC website](https://www.ioccc.org).
For example, the `index.html` file for each IOCCC entry contains
selected information about the authors. Tools from the [bin directory](bin/index.html)
use the content of these JSON files to generate the `index.html` files for each IOCCC
@@ -3157,7 +3157,7 @@ As of _Thu Nov 30 23:51:12 UTC 2023_, the _JSON value_ **MUST** be _"1.0 2023-06
The _author_JSON_format_version_ would only changed when the overall format
of the these files is modified: and then only those who maintain the
-[official IOCCC web site](https://www.ioccc.org) would be the one to do this
+[official IOCCC website](https://www.ioccc.org) would be the one to do this
in conjunction with changes to [bin directory tools](bin/index.html).
@@ -3444,7 +3444,7 @@ be a _JSON string_ or it **MUST** be a _JSON null_. The `github` _JSON string_
start with an at sign (_@_) and **MUST** be a valid GitHub username.
The IOCCC uses GitHub to hold the [official winner repo of the IOCCC](https://github.com/ioccc-src/winner),
-and hosts [official IOCCC web site](https://www.ioccc.org) on GitHub pages.
+and hosts [official IOCCC website](https://www.ioccc.org) on GitHub pages.
The IOCCC GitHub handle is:
diff --git a/inc/index.html b/inc/index.html
index b3e850f6c..6405089a0 100644
--- a/inc/index.html
+++ b/inc/index.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
diff --git a/inc/md2html.cfg b/inc/md2html.cfg
index 9c8114726..510ea1026 100644
--- a/inc/md2html.cfg
+++ b/inc/md2html.cfg
@@ -139,11 +139,11 @@ bin/README.md
-s
TITLE=The International Obfuscated C Code Contest
-s
- DESCRIPTION=Tools used to build and maintain the IOCCC web site
+ DESCRIPTION=Tools used to build and maintain the IOCCC website
-s
- KEYWORDS=IOCCC, tools, web site tools, bin
+ KEYWORDS=IOCCC, tools, website tools, bin
-s
- HEADER_2=IOCCC tools used build and maintain the IOCCC web site
+ HEADER_2=IOCCC tools used build and maintain the IOCCC website
-D
../
diff --git a/inc/topbar.default.html b/inc/topbar.default.html
index deff2b969..3f28d1e5b 100644
--- a/inc/topbar.default.html
+++ b/inc/topbar.default.html
@@ -94,7 +94,7 @@
@@ -239,7 +239,7 @@
- Fixing the web site
+ Fixing the website
diff --git a/index.html b/index.html
index e2f8fadc9..2551398a0 100644
--- a/index.html
+++ b/index.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -383,12 +383,12 @@
THIS IS AN EXPERIMENTAL IOCCC WEB SITE
-IMPORTANT: This is NOT the official IOCCC web site!
+IMPORTANT: This is NOT the official IOCCC website!
Please visit www.ioccc.org for the official IOCCC web.
-Please do NOT bookmark nor link to this experimental web site!
+Please do NOT bookmark nor link to this experimental website!
When this experiment is finished, this site will go away!
This test web tree is part of the temp-test-ioccc GitHub repo.
-This web site will be undergoing major changes, so expect many broken links, typos and other problems.
+
This website will be undergoing major changes, so expect many broken links, typos and other problems.
If you wish to recommend changes (understanding that things may be rapidly changing out from under your copy),
then consider making pull requests against the temp-test-ioccc GitHub repo.
What follows is the actual index.html file
diff --git a/index.md b/index.md
index 6f381fe27..249d57f85 100644
--- a/index.md
+++ b/index.md
@@ -1,17 +1,17 @@
# THIS IS AN EXPERIMENTAL IOCCC WEB SITE
-**IMPORTANT: This is NOT the official IOCCC web site!**
+**IMPORTANT: This is NOT the official IOCCC website!**
Please visit [www.ioccc.org](https://www.ioccc.org/index.html) for the official IOCCC web.
-Please do **NOT** bookmark nor link to this [experimental web site](https://ioccc-src.github.io/temp-test-ioccc/)!
+Please do **NOT** bookmark nor link to this [experimental website](https://ioccc-src.github.io/temp-test-ioccc/)!
When this experiment is finished, this site **will go away**!
This test web tree is part of the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc).
-This web site will be undergoing major changes, so expect many broken links, typos and other problems.
+This website will be undergoing major changes, so expect many broken links, typos and other problems.
If you wish to recommend changes (understanding that things may be rapidly changing out from under your copy),
then consider making pull requests against the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc).
diff --git a/judges.html b/judges.html
index c9384d0af..46b97ff56 100644
--- a/judges.html
+++ b/judges.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
diff --git a/license.html b/license.html
index 52ca4dcc1..c39dcdcdd 100644
--- a/license.html
+++ b/license.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
diff --git a/location.html b/location.html
index 4c708c97a..659d28b8e 100644
--- a/location.html
+++ b/location.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
diff --git a/markdown.html b/markdown.html
index 20e69f25c..9ebce793f 100644
--- a/markdown.html
+++ b/markdown.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -388,7 +388,7 @@ For example, we submitting to the IOCCC, we have p
to submit remarks about entry in markdown format. Every
winning IOCCC entry uses a README.md markdown file
as the basis for forming the index.html web page for that entry.
-All generated HTML pages on the Official IOCCC web site
+All generated HTML pages on the Official IOCCC website
start with some markdown content.
See the markdown syntax guide.
See also CommonMark Spec.
diff --git a/markdown.md b/markdown.md
index 37b216b82..3be81312f 100644
--- a/markdown.md
+++ b/markdown.md
@@ -5,7 +5,7 @@ For example, we [submitting to the IOCCC](faq.html#submit), we have people
to submit remarks about entry in markdown format. Every
[winning IOCCC entry](years.html) uses a `README.md` markdown file
as the basis for forming the `index.html` web page for that entry.
-All generated HTML pages on the [Official IOCCC web site](https://www.ioccc.org/index.html)
+All generated HTML pages on the [Official IOCCC website](https://www.ioccc.org/index.html)
start with some markdown content.
See the [markdown syntax](https://www.markdownguide.org/basic-syntax) guide.
diff --git a/news.html b/news.html
index 21a16b446..8840f3f4d 100644
--- a/news.html
+++ b/news.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -390,7 +390,7 @@ major events such as the opening of a new IOCCC, or who won.
information on Mastodon.
2024-05-30
A number of issues from minor fixes have been applied to the
-temp-test-ioccc web site
+temp-test-ioccc website
via the temp-test-ioccc repo.
437 commits have been applied since 2024-04-20, bringing the total
number to 5260 commits to date. The
@@ -424,7 +424,7 @@ This will speed up the start date of IOCCC28.
It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
IOCCC.
2024-04-30
-The web site now is viewing by mobile devices such as cell phones
+
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 hamburger-style menu icon in place of
drop-down menus at the very top of the page (called the topbar).
@@ -446,8 +446,8 @@ warnings, nor info** messages, changes involving fixing invalid
links to local files have been corrected, and changes involving the
topbar are now HTML 5 conforming.
2024-04-20
-Nearly all of the temp-test-ioccc web site
-web site has undergone editorial review. Nearly all IOCCC winning entries
+
Nearly all of the temp-test-ioccc website
+website has undergone editorial review. Nearly all IOCCC winning entries
compile on modern systems and many have try.sh scripts to help you run them.
For those that cannot compile and/or do not work, we have made a
Bugs and (Mis)features page.
@@ -455,26 +455,26 @@ For those that cannot compile and/or do not work, we have made a
All generated HTML pages are now conform to HTML 5 with the
Nu Html Checker reporting no error, warnings, nor info messages.
The IOCCC judges have contracted with a web designer
-to improve the overall look of the web site, while maintaining
+to improve the overall look of the website, while maintaining
the utilitarian look and feel, and without introducing any
glaring “dancing bears” and other frivolous web features.
We are working towards what we call the
Great Fork Merge
-where the contents of the temp-test-ioccc web site
-will be merged into the Official IOCCC web site.
+where the contents of the temp-test-ioccc website
+will be merged into the Official IOCCC website.
Stay tuned!
2024-02-29
-We continue to make good progress on web site. In the temp-test-ioccc GitHub repo we have made nearly 4600 changes to date!
+We continue to make good progress on website. In the temp-test-ioccc GitHub repo we have made nearly 4600 changes to date!
All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the bin directory.
2023-05-22
-We have been busy preparing for an important / significant update to this web site. In the temp-test-ioccc GitHub repo we have made nearly 2645 changes to date.
+We have been busy preparing for an important / significant update to this website. In the temp-test-ioccc GitHub repo we have made nearly 2645 changes to date.
While you are free to look at the temp-test-ioccc GitHub repo,
-please do not link to it as this repo and related web site will disappear once the main
+please do not link to it as this repo and related website will disappear once the main
IOCCC winner repo has been updated.
Also be aware that the temp-test-ioccc GitHub repo
is undergoing rapid changes. There are broken links and other things in mid-change.
Once we are ready to update the IOCCC winner repo
-and its associated web site,
+and its associated website,
we will post a news article warning of the pending change that is about to arrive.
These 2645+ changes in the temp-test-ioccc GitHub repo
include diverse things such as:
@@ -537,7 +537,7 @@ of the most recent news item.
2022-12-18
As per the suggestion of Toni Mikkola
(_@Virtaava@home.social_) we now maintain a
-status.json page on this web site.
+status.json page on this website.
In addition to the IOCCC-style easter egg, you may count on
the JSON status page having a JSON member with name of “contest”
that will have a value of either “closed” or “open”.
@@ -598,7 +598,7 @@ to upload the above mentioned compressed tarball: when the contest is open of co
We plan to hold in 2023, what we will call IOCCCMOCK, a trial IOCCC contest where the
judges will go through the motions (without judging the content) of an IOCCC:
testing the above mentioned tools and testing the submit server.
-We are working on complete rebuild of this web site as well.
+We are working on complete rebuild of this website as well.
2022-01-15
Source code has been released for version 0.24 2022-01-15 of the
mkiocccentry tool,
@@ -624,7 +624,7 @@ we will do so by committing their code to the
Winning entries
of the IOCCC repo, so that people will be able immediately
view the winning source.
-We plan to refactor and modernize the IOCCC web site.
+
We plan to refactor and modernize the IOCCC website.
We also plan to build a new and improved way to submit entries the next IOCCC.
As a result of all this work we need to do,
we plan to hold IOCCC28 in 2023 instead of 2021.
diff --git a/news.md b/news.md
index 5fee077a5..91c5efbc9 100644
--- a/news.md
+++ b/news.md
@@ -12,7 +12,7 @@ information on Mastodon.
## 2024-05-30
A number of issues from minor fixes have been applied to the
-[temp-test-ioccc web site](https://ioccc-src.github.io/temp-test-ioccc/)
+[temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo.
437 commits have been applied since 2024-04-20, bringing the total
@@ -55,7 +55,7 @@ IOCCC.
## 2024-04-30
-The web site now is viewing by mobile devices such as cell phones
+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 _hamburger-style_ menu icon in place of
drop-down menus at the very top of the page (called the _topbar_).
@@ -85,8 +85,8 @@ _topbar_ are now HTML 5 conforming.
## 2024-04-20
-Nearly all of the [temp-test-ioccc web site](https://ioccc-src.github.io/temp-test-ioccc/)
-web site has undergone editorial review. Nearly all [IOCCC winning entries](years.html)
+Nearly all of the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
+website has undergone editorial review. Nearly all [IOCCC winning entries](years.html)
compile on modern systems and many have `try.sh` scripts to help you run them.
For those that cannot compile and/or do not work, we have made a
[Bugs and (Mis)features](bugs.html) page.
@@ -97,38 +97,38 @@ All generated HTML pages are now conform to HTML 5 with the
[Nu Html Checker](https://validator.w3.org/nu/) reporting **no error, warnings, nor info** messages.
The [IOCCC judges](judges.html) have contracted with a web designer
-to improve the overall look of the web site, while **maintaining
+to improve the overall look of the website, while **maintaining
the utilitarian look and feel**, and without introducing any
glaring "_dancing bears_" and other frivolous web features.
We are working towards what we call the
**[Great Fork Merge](https://github.com/ioccc-src/temp-test-ioccc/issues/2239)**
-where the contents of the [temp-test-ioccc web site](https://ioccc-src.github.io/temp-test-ioccc/)
-will be merged into the [Official IOCCC web site](https://www.ioccc.org/index.html).
+where the contents of the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
+will be merged into the [Official IOCCC website](https://www.ioccc.org/index.html).
Stay tuned!
## 2024-02-29
-We continue to make good progress on web site. In the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc) we have made nearly 4600 changes to date!
+We continue to make good progress on website. In the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc) we have made nearly 4600 changes to date!
All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the [bin](bin/index.html) directory.
## 2023-05-22
-We have been busy preparing for an important / significant update to this web site. In the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc) we have made nearly 2645 changes to date.
+We have been busy preparing for an important / significant update to this website. In the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc) we have made nearly 2645 changes to date.
While you are free to look at the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc),
-please **do not link to it** as this repo and related web site will disappear once the main
+please **do not link to it** as this repo and related website will disappear once the main
[IOCCC winner repo](https://github.com/ioccc-src/winner) has been updated.
Also be aware that the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc)
is undergoing rapid changes. There are broken links and other things in mid-change.
Once we are ready to update the [IOCCC winner repo](https://github.com/ioccc-src/winner)
-and its associated web site,
+and its associated website,
we will post a news article warning of the pending change that is about to arrive.
These 2645+ changes in the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc)
@@ -207,7 +207,7 @@ of the most recent news item.
As per the suggestion of [Toni Mikkola](https://fosstodon.org/@Virtaava@home.social)
(_@Virtaava@home.social_) we now maintain a
-[status.json](status.json) page on this web site.
+[status.json](status.json) page on this website.
In addition to the IOCCC-style _easter egg_, you may count on
the JSON status page having a JSON member with name of **"contest"**
@@ -294,7 +294,7 @@ We plan to hold in 2023, what we will call **IOCCCMOCK**, a trial IOCCC contest
judges will go through the motions (without judging the content) of an IOCCC:
testing the above mentioned tools and testing the submit server.
-We are working on complete rebuild of this web site as well.
+We are working on complete rebuild of this website as well.
## 2022-01-15
@@ -331,7 +331,7 @@ we will do so by committing their code to the
of the IOCCC repo, so that people will be able immediately
view the winning source.
-We plan to refactor and modernize the IOCCC web site.
+We plan to refactor and modernize the IOCCC website.
We also plan to build a new and improved way to submit entries the next IOCCC.
As a result of all this work we need to do,
**we plan to hold IOCCC28 in 2023 instead of 2021**.
diff --git a/next/guidelines.html b/next/guidelines.html
index acfbb8e94..762ccb1c9 100644
--- a/next/guidelines.html
+++ b/next/guidelines.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -432,8 +432,8 @@ at any time.
| The submit URL should be active on or slightly before 2020-Jan-15 12:21:37 UTC.
Please wait to submit your entries until after that time.
The official rules, guidelines and iocccsize.c tool will be available
-on the official IOCCC web site on or slightly before start of this IOCCC.
-Please check the IOCCC web site “How to enter” link:
+on the official IOCCC website on or slightly before start of this IOCCC.
+Please check the IOCCC website “How to enter” link:
https://www.ioccc.org/index.html#enter
on or after the start of this IOCCC to be sure you are using the correct
versions of these items before using the IOCCC entry submission URL.
@@ -1004,7 +1004,7 @@ This is done prior to posting the winners to the wide world.
The IOCCC no longer uses twitter. IOCCC entries will be announced
by a git commit to the IOCCC entries repo:
https://github.com/ioccc-src/winner
-that, in turn, updates the offivial IOCCC web site:
+that, in turn, updates the offivial IOCCC website:
https://www.ioccc.org/index.html
In addition a note is posted to the IOCCC Mastodon account:
https://fosstodon.org/@ioccc
@@ -1099,7 +1099,7 @@ from the @IOCCC twitter handle.
to be sure they are seeing the most recent tweets.
The judges will then post an initial announcement of who won, the name
of their award, and a very brief description of the winning entry
-on the IOCCC web site:
+on the IOCCC website:
https://www.ioccc.org/whowon.html
We will also attempt to submit a brief announcement story to /.:
https://slashdot.org
@@ -1110,7 +1110,7 @@ the winning authors are given a chance to review the judges comments,
and test our Makefile. This review process typically takes a few weeks.
Sometime after the initial announcement, and once the review
by the winners has been completed, the winning source will be
-posted to the IOCCC web site:
+posted to the IOCCC website:
https://www.ioccc.org/years.html
NOTE: previous winners are available at that URL
@@ -1119,7 +1119,7 @@ posted to the IOCCC web site:
The IOCCC no longer uses twitter. IOCCC entries will be announced
by a git commit to the IOCCC entries repo:
https://github.com/ioccc-src/winner
-that, in turn, updates the official IOCCC web site:
+that, in turn, updates the official IOCCC website:
https://www.ioccc.org/index.html
In addition a note is posted to the IOCCC Mastodon account:
https://fosstodon.org/@ioccc
diff --git a/next/guidelines.md b/next/guidelines.md
index da52b2dba..269db19c0 100644
--- a/next/guidelines.md
+++ b/next/guidelines.md
@@ -84,8 +84,8 @@ The IOCCC submission URL:
Please wait to submit your entries until after that time.
The official rules, guidelines and iocccsize.c tool will be available
-on the official IOCCC web site on or slightly before start of this IOCCC.
-Please check the IOCCC web site "How to enter" link:
+on the official IOCCC website on or slightly before start of this IOCCC.
+Please check the IOCCC website "How to enter" link:
```
https://www.ioccc.org/index.html#enter
@@ -897,7 +897,7 @@ by a git commit to the IOCCC entries repo:
https://github.com/ioccc-src/winner
```
-that, in turn, updates the offivial IOCCC web site:
+that, in turn, updates the offivial IOCCC website:
```
https://www.ioccc.org/index.html
@@ -1031,7 +1031,7 @@ to be sure they are seeing the most recent tweets.
The judges will then post an initial announcement of who won, the name
of their award, and a very brief description of the winning entry
-on the IOCCC web site:
+on the IOCCC website:
```
https://www.ioccc.org/whowon.html
@@ -1052,7 +1052,7 @@ and test our Makefile. This review process typically takes a few weeks.
Sometime after the initial announcement, and once the review
by the winners has been completed, the winning source will be
-posted to the IOCCC web site:
+posted to the IOCCC website:
```
https://www.ioccc.org/years.html
@@ -1072,7 +1072,7 @@ by a git commit to the IOCCC entries repo:
https://github.com/ioccc-src/winner
```
-that, in turn, updates the official IOCCC web site:
+that, in turn, updates the official IOCCC website:
```
https://www.ioccc.org/index.html
diff --git a/next/index.html b/next/index.html
index dfd541f7f..ec39c9c4e 100644
--- a/next/index.html
+++ b/next/index.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
diff --git a/next/rules.html b/next/rules.html
index 3d7e95657..29dfddfcc 100644
--- a/next/rules.html
+++ b/next/rules.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -439,7 +439,7 @@ for important information on how to submit to the IOCCC.
| The submit URL should be active on or slightly before 2020-Jan-15 12:21:37 UTC.
Please wait to submit your entries until after that time.
The official rules, guidelines and iocccsize.c tool will be available
-on the official IOCCC web site on or slightly before start of this IOCCC.
+on the official IOCCC website on or slightly before start of this IOCCC.
Please recheck on or after the start of this IOCCC to be sure you
are using the correct versions of these items before using the IOCCC
entry submission URL.
@@ -602,7 +602,7 @@ in the subject of your email message when sending email to the judges.
The rules and the guidelines may (and often do) change from year to
year. You should be sure you have the current rules and guidelines
prior to submitting entries.
-| See the Official IOCCC web site for additional information.
+| See the Official IOCCC website for additional information.
For the updates and breaking IOCCC news, you are encouraged to follow
the twitter handle:
@IOCCC
diff --git a/next/rules.md b/next/rules.md
index 8b43fa140..ce15ff03b 100644
--- a/next/rules.md
+++ b/next/rules.md
@@ -86,7 +86,7 @@ for **important information** on how to submit to the IOCCC.
Please wait to submit your entries until after that time.
The official rules, guidelines and iocccsize.c tool will be available
-on the official IOCCC web site on or slightly before start of this IOCCC.
+on the official IOCCC website on or slightly before start of this IOCCC.
Please recheck on or after the start of this IOCCC to be sure you
@@ -388,7 +388,7 @@ The rules and the guidelines may (and often do) change from year to
year. You should be sure you have the current rules and guidelines
prior to submitting entries.
-**`|`** See the [Official IOCCC web site](../index.html) for additional information.
+**`|`** See the [Official IOCCC website](../index.html) for additional information.
For the updates and breaking IOCCC news, you are encouraged to follow
the twitter handle:
diff --git a/nojs-menu.html b/nojs-menu.html
index 9500391f8..93bbf7c13 100644
--- a/nojs-menu.html
+++ b/nojs-menu.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -401,7 +401,7 @@
FAQ
How to enter the IOCCC
Fixing IOCCC entries
-Fixing the web site
+Fixing the website
Fixing author info
About
diff --git a/nojs-menu.md b/nojs-menu.md
index 244bd4866..e502ff5a5 100644
--- a/nojs-menu.md
+++ b/nojs-menu.md
@@ -18,7 +18,7 @@
* [FAQ](faq.html)
* [How to enter the IOCCC](faq.html#fix_an_entry)
* [Fixing IOCCC entries](faq.html#fix_an_entry)
-* [Fixing the web site](faq.html#fix_web_site)
+* [Fixing the website](faq.html#fix_web_site)
* [Fixing author info](faq.html#fix_author)
## About
diff --git a/status.html b/status.html
index 11a20ccbb..3eb63c281 100644
--- a/status.html
+++ b/status.html
@@ -138,7 +138,7 @@
@@ -283,7 +283,7 @@
- Fixing the web site
+ Fixing the website
@@ -441,7 +441,7 @@ registered email address.
Announce who are authors of this year’s winning IOCCC entries via the @IOCCC mastodon
feed.
Upload the winning code to the Official IOCCC winner repo
Update the Official IOCCC web site, and in particular
+
Update the Official IOCCC website, and in particular
display this year’s winning IOCCC entries at the top of the IOCCC
winning entries page.
Update the IOCCC news page.