httpd.apache.org: Dealing with historical/outdated pages (was: Re: Ancient Contributors page)

[Philippe Cloutier]

On 6/12/2026 3:34 PM, Rich Bowen wrote:

On Jun 12, 2026, at 3:23 PM, Roy T. Fielding <field...@gbiv.com> wrote:

  I also haven't edited the website since it was moved to XML automation;
apparently that was just enough of a barrier to prevent any further 
contributions (odd given
that most of my IETF work was also in XML). I suffer from 
inscrutablescriptaphopia.

….Roy

FWIW, the website is markdown now. It’s just the manual that’s weird bespoke 
XML.

I keep looking for ways to improve the “historical artifact” nature of so much 
of our website, and I feel like I’m always riding the fence between losing 
history and making it look like this is a modern project that’s still relevant. 
Possibly intentionally splitting the site in “historical” and “current” 
sections would be an approach that could work.

I may misunderstand what you are proposing, but I am skeptical about your proposal. To make an analogy with Wikipedia, it has countless outdated pages, and countless current pages, but pages in the first group have nothing logical in common, besides getting insufficient love. The English Wikipedia only (tries to) group outdated pages in a category to track pages which need work: https://en.wikipedia.org/wiki/Category:Articles_with_obsolete_information

I fail to see how httpd webpages could be split. What I agree would be a good idea would be to add warnings on outdated content. Wikipedia templates allow doing it at the article section level, as in the following case: https://en.wikipedia.org/wiki/International_Civil_Aviation_Organization#Environment Template:Update also allows specifying a date, quantifying how bad the problem is.

--
🅭🄍: https://www.philippecloutier.com/Common+infrastructure+licensing#list

Philippe Cloutier

Or are you saying there is content which you consider "historical", in the sense that it *should not* be updated? Perhaps examples of what you suggest qualifying as historical would clarify.

OpenPGP_0x8A37FF445EA6611D.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature