Communicate whether user is viewing a snapshot and help navigate to living document
Status signals:
Development status
Implementer guidance
Adopter guidance
Standardization plan
5 of 14
Maturity: Draft
Device: Desktop
6 of 14
Maturity: Draft
Device: Desktop
Snapshot
7 of 14
Maturity: Abandoned
Device: Desktop
Snapshot
8 of 14
Maturity: Transferred
Device: Desktop
Snapshot
9 of 14
Maturity: Draft
Device: Mobile
10 of 14
Design notes
Distinguish front matter look and feel from TR spec
Removed CG logo intentionally
Make clear “not a W3C standard” up front
For clear communication, new section on usage guidance
If snapshot, help user navigate to latest document
Provide template usage guidance after status section
Use “traditional” status section to provide custom guidance
Use colors to convey (along with text) where caution advised
11 of 14
Design discussion topics
Seeking feedback on clarify of status signals and organization of information
12 of 14
Anticipated metadata approach
A few are mechanical (last modified, group status)
Some have well-known sources for some specs/CGs
E.g., browser specs have well-maintained data sources on implementation, intent to implement, adoption signals, test suites
For the rest, GitHub-based workflows with escalation paths:
E.g., start with an issue in the spec repo asking about standardization plan
If no reply, GitHub notification to the Chairs
If no reply, CG Staff outreach
13 of 14
Metadata discussion topics
How opinionated should usage guidance be?
Binary usage guidance:
Strong community support: Yes
Strong implementer participation: Yes
Specification stable: Yes
Or enumeration:
Community support: Strong
Implementer participation: Good
Or “just the facts”
X implementers have indicated interest, 0 have objected
N implementers participate
14 of 14
Next steps
CG Chair lunch today!
If you have comments on mockups this week, please find us in Kobe
Though these are mockups, style expected to resemble them
Will be implemented in HTML and supported in respec and bikeshed
We will create documentation for editors on the Usage Guidance section
Beta testing period (for 3-6 months expected start Q1 2026) will allow for more structured feedback (including on style, documentation, implementation in respec and bikeshed, tooling)