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

> I don't think there's a way around it while Shepherd is used as the anchor database for Bikeshed. But my understanding is that Bikeshed is, on the long run, planning to switch to [Webref](https://github.com/w3c/webref), which is backed by [Reffy](https://github.com/w3c/reffy) – and it seems like Reffy could indeed be used in the CI workflow.

Thanks for mentioning that — I’d forgotten that the known plan was for Bikeshed to move way from Shepherd.

I notice there’s an open issue at https://github.com/tabatkins/bikeshed/issues/1761 and there’s no response there, I do seem to remember from discussion in the WHATWG Matrix room that there’s agreement on moving to Webref. Looking back, I found one mention at https://matrixlogs.bakkot.com/WHATWG/2022-05-02#L11 but I seem to recall there having been more discussion about it there than just that.

As far as Respec, it’s not clear to me that Respec is actually currently relying on the Shepherd spec anchor/link database. But even it were, I think the plan there too would be to switch to using Webref instead.

And anyway that concern would not be relevant for CSS specs, since (as far as I know) no CSS specs are using Respec.

> a stopgap solution that only serves drafts but means that Bikeshed and Respec no longer autolinks to the current state would be **bad**

@svgeesus To be clear for the record here, if Bikeshed and Respec were using Webref, then when considering alternative solutions for serving CSS specs, we’d at least not have need for concern about that potential _“Bikeshed and Respec no longer autolinks to the current state”_ problem, right?



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


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

Received on Friday, 15 July 2022 11:37:31 UTC