- From: Keith Cirkel via GitHub <noreply@w3.org>
- Date: Fri, 13 Feb 2026 19:46:41 +0000
- To: public-css-archive@w3.org
> It's not my decision, but a solution that breaks all existing links to a wiki that has around a 20 year history and is supposed to be a stable repository of knowledge doesn't seem like the best approach. At the very minimum, we should have something at the old URLs that can translate and redirect or proxy to the new ones. We could consider a read-only static site (perhaps hosted on gh-pages) that mirrors the content of the github wiki, which can maintain the URL structure including the domain. > FWIW, the DokuWiki software and the existing wiki isn't a large burden, and by itself, can be hosted on an inexpensive server. The only current dependency on the legacy server is user registration. That seems reasonable, but it seems that any individual hosting leaves the WG at the whim of their appetite for continuing to do so. While I agree moving to proprietary platforms might not be a _positive_ step, it at least provides some secutity because platforms have monetary incentive to continue operating, and if they deprecate features there will be probably a long migration window. As for bot traffic, another benefit on hosting on a platform is that they're generally a lot cheaper and a lot more robust to traffic spikes than the cost involved of running/sysadmining a server and dealing with this. Traffic to the wiki - even with the bot traffic - likely wouldn't even register as a blip in the dashboards at one of these platform providers, but for an individual might result in some stressful days trying to maintain/update it. -- GitHub Notification of comment by keithamus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12054#issuecomment-3899102405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 February 2026 19:46:42 UTC