- From: Drew Peifer via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Mar 2020 23:41:58 +0000
- To: public-css-archive@w3.org
As a current developer, I am most interested in seeing: A) A list of stable features presented in a relatively easy to understand structure, with option to deep dive (the team expert should not be the only one who can read the documentation) B) That list should be documented and hosted by an authoritative organization / site (a github repo's README is semi-authoritative to devs, but not to anyone else) C) Any best-practices determined by the authoritative organization / site should be glaringly obvious in their UI presentation (no excuse for ignoring them) D) A clear list of the advantages of using these features / practices, and the perils of not doing so (**crucial** to bridging the gap from dev team to business team, it should not be on Joe Developer's shoulders to summarize and sell the entirety of CSS4 in a 30 min meeting) As a former analyst, the above items are what I would have needed in my hand to take to leadership in order to convince them that we needed to take action regarding an upgrade, patch, or defining new practices. If any of these elements were missing, especially D, I think they would have likely interpreted it as a "developer want" instead of a "product need", and that's where the issue would have concluded. -- GitHub Notification of comment by Drewpeifer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-595500726 using your GitHub account
Received on Thursday, 5 March 2020 23:42:00 UTC