search

w3c / tr-design

CSS used by W3C specs (this repo is not about the w3.org/TR index page)
https://w3c.github.io/tr-design/src/README
Other
64 stars 29 forks source link

Link to Lower Level #292

Open fantasai opened 2 years ago

fantasai commented 2 years ago

@svgeesus was pointing out that it's not obvious how to get from e.g. Snapshot 2021 back to Snapshot 2020 etc. because they are separate publications, rather than a dated sequence like earlier and newer versions of a draft. But we have this same problem with levelled specs in general: e.g. Cascade 4 doesn't have an obvious header link to Cascade 3 or to the set of Cascade specs.

Is there something we can do with in the headers and/or w3.org/TR/ that can help make a sequence of specs easier to relate?

deniak commented 2 years ago

This is something we haven't emphasized so far as we were not sure how the concept of 'series' (group of specifications with different levels) would go but we have the cover pages for the series, e.g. CSS and css-cascade, which takes the shortname without the level as parameter. You could expose these links in the headers if this is useful.

With the upcoming TR redesign and the introduction of families (GH repo), the specifications of the same series will be grouped together.

plehegar commented 2 years ago

We left up to the editors to add those information indeed, without constraining them. Rethinking the approach with our handling of series seems the right think to do indeed.