I think some obsolete pages probably still provide valuable information for
developers as a way to show things we considered and decided not to implement or
things we implemented and decided to remove. It's a useful resource if we ever
want to revisit those past ideas, or as a reference to show things we tried and
why they failed.
But some pages probably really don't provide much value anymore, e.g. steps to
do XYZ that are no longer relevant. Those kinds of pages are probably safe to
delete. For example, the old "Release Workflow" page probably doesn't provide
value anymore and can be deleted.
Maybe what we do is create a new top-level "Archive" or "Obsolete" page, and we
can move any obsolete pages that we want to keep around to be child pages of
that page? That will keep pages around for reference, but reduce clutter in the
sidebar page tree. We could also add a banner at the top of those pages in case
anyone finds a page via a search engine.
As a first step, if we don't want to think about obsolete vs delete, we could
move all obsolete pages to the archive, and then think about which pages to
actually delete at later date.
On 2025-10-31 03:16 PM, Mike Beckerle wrote:
So we're building up a body of wiki pages that are obsolete.
The wiki gets indexed by search engines. That could lead people to obsolete
information.
Should we just delete obsolete pages?
Maybe move them to an obsolete pages area so that their URLs will clearly
show they are obsolete?
Or just edit their titles to add "Obsolete" as the first word?
The issue is that these pages often have some residual value, and it's not
like these are checked in to a git repo. Once we delete the pages I think
they are gone forever.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
