- From: Shaun Rashid via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Feb 2020 19:47:34 +0000
- To: public-css-archive@w3.org
I have been debating this in my head for the past week. Based on recent experience within the company I work for, I do think that packaging groups of CSS modules into "marketable" versions has more benefits than drawbacks especially when it comes to having the priority conversation with non-technical (or even non-frontend) stakeholders. A recent example is that the team wanted to introduce custom properties into our code base. Using "CSS4" with stakeholders allowed us to frame the discussion as an upgrade as opposed to wanting to use a particular technology. The conversation with stakeholders is much more straight forward when we can say that we want to "upgrade to CSS 4.x" and outline the specs that make that up as opposed to we want to upgrade to use "module A, version 3", "module B, version 2", "module C, version 2". While technically it makes no difference, I feel like having these "versioned groups" allows people who are not familiar with the specs to grok and scope what it means to adopt newer levels of the specs. -- GitHub Notification of comment by shaunrashid Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-586634962 using your GitHub account
Received on Saturday, 15 February 2020 19:47:36 UTC