Re: [csswg-drafts] Replace the https://drafts.csswg.org/ backend (#7500)

I’m not going to weigh in on the actual debate, since I'm finding myself agreeing with both sides as I read this thread.

However, I'd like to address this:

> #### Cons
> The only downside I am aware of is that GitHub Pages has some limitations the current [drafts.csswg.org](https://drafts.csswg.org/) doesn’t have — most notably an inability to do server-side redirects and an inability to set arbitrary HTTP response headers.
> 
> However, those limitations in GitHub Pages are well-known and well-understood, and there are workarounds or mitigations.
> 
> Lack of server-side redirects is probably the most-serious limitation — but it can be addressed by using client-side redirects instead. Admittedly not optimal, but does work — as evidenced by the fact [andreubotella.com/csswg-auto-build](https://andreubotella.com/csswg-auto-build/) is already using it.

Netlify is very similar to GitHub Pages, but also supports [headers](https://docs.netlify.com/routing/headers/) and [redirects](https://docs.netlify.com/routing/redirects/) with a very easy declarative syntax, and I'm sure they'd be delighted to host this for free, since they host open source projects for free as well.

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


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

Received on Monday, 18 July 2022 15:02:25 UTC