[meta] Co-authoring CSS Design Principles with the TAG #7835
Description
Opening this issue with my TAG hat on. 🎩
As many of you are aware, we maintain a Web Platform Design Principles document. The goal of these principles is to assist people designing new web platform features, so that more design issues can be caught and fixed before TAG design reviews. A secondary goal down the line is to help authors create web platform consistent APIs.
While the scope of the document spans the entire web platform, there is a section for CSS Design Principles. We have been proactively reaching out to CSS WG members for review when a CSS design principle comes up, and several TAG members are also CSS WG members themselves (@atanassov @hober @LeaVerou @plinss). However, it was recently pointed out to us that there should be a more structured involvement of the CSS WG in editing these principles.
We do think there is value in a single Design Principles document, and wouldn't want to fragment it and scatter it in multiple places, and we do think this is within the purview of the TAG as it relates to Web architecture. However, we also see a lot of value in relevant WGs having a more active role in editing and reviewing the principles relevant to their domain. We were wondering what this collaboration could look like. Ideas that came up when we discussed this today was a design principles TAG - CSS WG task force, or a label in our design principles repo for that the CSS WG could monitor to discuss relevant issues, but we're open to any other ideas.
One thing to keep in mind when discussing process is that PRs are the only way of editing this document, even for us. We do not directly commit to it, ever. So the process is currently identical for TAG members editing it or anyone else.