Collecting Best Practices and Experiences around the W3C Registry Mechanism
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 84
- Forks
- 69
- Avg merge
- 14h 52m
- Merged PRs (30d)
- 2
Description
During the TPAC24 Breakout on Registries, I have presented (Google slides | W3C WoT WG GitHub) two resources created by two W3C WGs about registries.
- WoT WG Analysis on Registries within W3C and outside: https://github.com/w3c/wot/blob/main/registry-analysis/Readme.md
- TTWG Boilerplate: https://w3c.github.io/ttwg/boilerplate/registry/
@frivoal has mentioned I should tag him and @fantasai to find a place to store or at least link these documents. The initial agreement was somewhere in the Guide document. This way, those who start with the registry mechanism do not have to start from scratch and we can collect best practices over time.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Guide document and the two linked registry resources: the WoT WG registry analysis and the TTWG boilerplate. Determine where the Guide should store or link them and how best practices can be collected over time. Done means the relevant registry guidance is placed or linked in the Guide with an agreed structure.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100