Open lcn2 opened 1 week ago
Glad you want this after the next IOCCC as I could not possibly do this until then! But as you asked me if I wanted to do this (as I did quite well with other Wayback Machine tasks) .. please assign this to me. Thanks.
After the Great Fork Merge we will need to transfer this issue to the Official IOCCC winner repo.
After the Great Fork Merge we will need to transfer this issue to the Official IOCCC winner repo.
Makes sense.
Suggestion: rather than make all in news.html make it in one of the following locations:
The reason is to make the news page not really long.
Another option that might be better yet is below.
Have a subdirectory called news with the current news file being recent.html. The top level news.html can be a symlink to that file OR in the menu it can link to it.
Then separate the old news based on the year. Or maybe based on which IOCCC it was (does the 28th contest at the 29th end up having the news in between the two or would it be in the 29th?).
Downside to this idea is that there would be a lot of files. If that's a problem it might be by every N years (maybe 5 but not sure)?
On the other hand the fact the news isn't updated that often might mean not many files are even needed and it could even be a single old file (archived news) and the recent news. Or even just one file.
Personally I think the last idea might be the most ideal but maybe a subdirectory is useful (but it might not be either).
We can discuss the above later of course: you can let it sit in the back of your mind and I can too (well the back of MY mind!). But of course if either of us (or for that matter anyone else) have any thoughts we can discuss those too.
Soon I will be back at the FAQ but I have not long before another break: a phone call. Unfortunately sometimes the call is late so I have to sit there waiting not being productive.
Even so I think I can get a reasonable amount done today.
Oh! I see that the top comment (now?) even suggests some of what I suggested. So perhaps the fact we both thought of that one individually that idea is the best one?
Is there an existing issue for this?
Describe the feature
It might be fun to restore old news items and make them available.
We don’t propose adding then to
news.md
directly as that might make the resulting web page excessively long and full of mostly outdated news items. Instead one might add them to some newarchive/news/
directory. The bottom of thenews.md
file could indicate that older news items are available via somearchive/news/index.html
(viaarchive/news/README.md
markdown file) file.The
archive/news/README.md
file could have sections by calendar year with a table of contents at the top.When the existing
news.md
file needs old news to be “cleaned out”, instead of removing them, such news items could be moved over into thearchive/news/README.md
file.Relevant images, screenshots or other files
N/A
Relevant links
news.html
Anything else?
Remarks from the original TODO item
On possible idea is to adopt some sort of archival news page as suggested by comment-2158965619. If that is done, some way back machine digging and/or repo history digging should be done to recover some historical news that has been "lost".
We suggest that a new directory
archive/news/
be created so that old news from, say 2019 could go intoarchive/news/2019.news.md
from whicharchive/news/2019.news.html
would be built by bin tools. The filearchive/news/README.md
would hold an inventory/table of contents linking to the individual archived news year pages and the bin tools could use that README to formarchive/news/index.html
.The bottom of the top level
news.md
would always hold some sort of "for older IOCCC news, see the IOCCC news archive" that would link to thearchive/news/index.html
archived news page.Consider if we should or shouldn't think out
news.md
and retain high level items. However, also consider comment-2158965619 as a reason not to thin out the news.See also 2003 website archive as per comment-2180597422.
Priority
This issue should be considered after IOCCC28 is complete.