Re: [csswg-drafts] CSS WG drafts server (#12054)

> > I’d like to suggest that y’all very strongly consider not setting up such a replacement server but instead just having everything served from https://w3c.github.io/csswg-drafts/ URLs — just as we do with all our other working groups — and stop there.
> 
> I disagree with that part. Using GitHub (or whatever) to generate the site is fine, but serving it from a URL we control is preferable. I don't foresee GitHub going out of business tomorrow, but neither is it wise to count on a business keeping things things as they are, and free, forever. It might stay, it might change, it might be discontinued eventually. And for anyone saying I'm paranoid, please see https://www.failory.com/google/code or https://www.yahoo.com/entertainment/yahoo-announces-shutdown-social-platform-034108123.html.
> 
> I don't care what back-end we use to make our service work, and I'm totally OK with it being powered by GitHub pages if that's the most convenient thing these days. But keeping control of the domain name and URL space is a good thing.

I agree. I believe we can rely on spec-prod to generate the snapshots of the specs and commit them to GitHub pages but we should keep control of the URLs and use some proxy to these specs. I haven't used the [custom domain feature](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages) with GitHub pages but it could be an option.


-- 
GitHub Notification of comment by deniak
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12054#issuecomment-3846853724 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 4 February 2026 11:19:39 UTC