CSS current work & how to participate (original) (raw)
If you want to help
Raise issues via GitHub. (You will need to create an account on GitHub first.) Github contains copies of the editors' drafts of the CSS specifications and ‘Houdini’APIs.
The contributor guidelines explain in more detail what role GitHub issues play in the development of CSS specifications.
If you are raising issues on a specific CSS module, please prefix the title of your issue with the appropriate spec code (given in the ‘Status of this document’ section) in brackets, e.g. ‘[css3-flexbox] error in margin calculations’. This will help the editors find and track your comments.
If you work for a W3C member organization, you can also join the CSS working group and come to its meetings. To participate, you need to commit to (on average) 1 day per week. Contact Chris Lilley and your organization's W3C AC representative. The group's minutes are public and posted on the CSS WG blog.
There are many ways to keep up to date with new publications by the CSS WG. The ‘What's new?’ section above shows the most recent drafts and it also has an Atom feed. Publications are announced on the CSS WG's blog and its
Atom feed, and the group's
Mastodon account. First drafts from all W3C working groups appear on the public-review-announce mailing list and its RSS feed. The latest publications from all W3C working groups are at the top of the Technical Reports page, which also has an
The archived mailing list www-style@w3.org has the agenda and the minutes of the meetings of the working group. You cansubscribe yourself. title="New W3C publications" > RSS feed.
About the test suites
The CSS working group spends a lot of time on developing the CSS test suites along with the CSS specifications. By providing a test suite for each module as soon as the module is published, CSS implementations conform to the specification much earlier; also people have an easier time understanding the formal text of the spec.
Raising issues via GitHub is preferred: see theWeb-platform tests repository.
Mark-up conventions
The Bikeshed source mark-up of the specifications follows certainconventions (which is used for automatic processing).