Fixed `#todo` link in `2024/macke/README.md`.
Improved markdown paragraph size of `inc/rules.*.hdr` files.
Fixed FAQ link generated by `bin/status2html.sh` for the pending state.
Improved the markdown written by `bin/status2html.sh` for various states.
Changed `bin/status2html.sh` VERSION to "2.0.2 2025-12-02".
Changed IOCCC Rules to version **29.15 2025-12-01**.
Changed IOCCC Guidelines to version **29.08 2025-12-02**.
Changed IOCCC FAQ to version **29.05 2025-12-02**..
Ran `make update` to perform the above.
Fixed `#todo` link in `2024/macke/README.md`.
Improved markdown paragraph size of `inc/rules.*.hdr` files.
Ran `make quick_www tar timestamp` to perform the above.
This includes a number of blocks of text in the wrong place.
Some typos were fixed but just like with the rules a very thorough job
was not done and there are deliberate typos in the guidelines as well.
It should be a bit clearer now, except perhaps the guidelines that are
deliberately confusing (or those I missed).
Fixed broken links.
Restored text that was accidentally removed during the emergency
recovery of guidelines some days back.
Moved some text that was in the wrong place.
The formatting of the markdown files was changed for shorter lines (for
those viewing the markdown in a viewer rather than a web browser).
Added a <div id> to 2024/index.html so the guidelines (or maybe rules)
could link to the important note from the judges in IOCCC28.
Restore rewording of rule 2b done by @SirWumpus.
Fixed links between rules and guidelines.
Add guideline about "Rule 2 - Size restrictions" not changing soon.
Expand "Guidelines for Rule 13 - No carriage returns in prog.c".
Put the word, "restrictions" into "Rule 2 - Size restrictions".
While this is a **GOOD IDEA**, the concept needs to be rolled out
over all of the rules, not just "Rule 2 - Size restrictions".
Changed IOCCC Rules to version **29.13 2025-12-01**.
Changed IOCCC Guidelines to version **29.06 2025-12-01**.
Ran `make quick_www` to perform the above.
unstructured and hard to find specific guidelines when scattered.
Add some rule guideline based from the general section. Shuffle
related paragraphs under relevant sections.
Added a number of change bars to the rules & guidelines.
Recommend recommend that all markdown files in your submission observe
[IOCCC markdown guidelines](../markdown.html).
Made use of "_..._" consistent in the rules & guidelines.
Updated some the fun guidelines.
Performed some whitespace cleanup in the rules & guidelines.
Changed IOCCC Rules to version **29.12 2025-12-01**.
Changed IOCCC Guidelines to version **29.04 2025-12-01**
Ran `make quick_www` to perform the above.
Improved Rule 1.
Added Guidelines for Rule 1.
Improved Rule 3.
Added missing Guidelines for Rule 3.
Reordered guidelines sections under the "General Guidelines".
Set level 2 for "General Guidelines" subsections.
Changed IOCCC Rules to version **29.11 2025-11-30**.
Changed IOCCC Guidelines to version **29.03 2025-11-30**.
Ran `make quick_www` to perform the above.
The FAQ has a new item that is referred to in the guidelines updates.
The guidelines has some link fixes and other minor changes.
Some fun was corrected in the guidelines as well but kept a fair bit
shorter than before (i.e. shorter than IOCCC28). In particular because
some code from the mkiocccentry (from some contributors) is no longer
extant, and because said code was not even a complete program, only
refer to two programs that were strictly written by someone other than
the judges. Those paragraphs are only one sentence (they used to be
more than one) and the rest of the mkiocccentry repos is not mentioned
(this was the longest one and it went into other things that while fun
were not relevant). This keeps it light, fun, very short and more
importantly correct both to the rule about submissions must be a
COMPLETE C program and other rules as well.
Some typo fixes were made.
I believe this commit resolves the problems from yesterday although I
did not go through the file extremely carefully as I know @SirWumpus
also wants to go through it and so does Landon, so I kind of rushed
through it.
Attempt to fix HTML5 errors.
Remove Makefile section from Guidelines as
this is in the FAQ.
Added links to Makefile FAQ in Guidelines.
Ran `make quick_www` to perform the above
TODO: Complete the correction for issue #244 ("Restore guidelines").
TODO: Continue to revise and improve the IOCCC guidelines as needed.
TODO: Fix typos/nits in the `next/guidelines.md` if needed.
TODO: Fix typos/nits in the `next/rules.md` if needed.
This is a checkpoint correction for issue #244 ("Restore guidelines")
which in turn was a correction for issue #243 ("Fixes and minor
improvements in rules").
Remove code that put the contest status at the top
of the guidelines page.
Change `bin/gen-status.sh` VERSION to "2.1.0 2025-11-29",
Fix `next/guidelines.md` so that `next/guidelines.html`
is rendered correctly.
Update sitemap and status (due to recent news mod).
Ran `make quick_www` to perform the above
TODO: Complete the correction for issue #244 ("Restore guidelines").
TODO: Continue to revise and improve the IOCCC guidelines as needed.
TODO: Fix typos/nits in the `next/guidelines.md` if needed.
TODO: Fix typos/nits in the `next/rules.md` if needed.
Somehow the guidelines got clobbered during an edit. It is not clear to
me if every link is okay in this but from a quick look at it it some of
the links if not all were certainly updated. It will require another
pass in the browser but this is an emergency commit.
The links to rules should all be good. This includes in news.html,
quick-start.html, next/submit.html, 2024/index.html (it had been
modified to refer to next/rules.html instead of 2024/rules.html) as well
as the guidelines and rules themselves (under next/).
Various typo fixes. I'm afraid there are likely others but I must let
others deal with that as I am out of time.
Removed FAQ about mastodon push notifications. When I added the FAQ
about push notifications for mastodon I was incorrect. The web browser
interface suggests it but I never got a push notification even before
Apple broke them. There seems to be no way at this time to get them. I
note that there was a screenshot in the FAQ but this file still is in
the repo possibly.
I regenerated the html files but it's possible I forgot to do one at the
last minute.
Landon Curt Noll