- From: Iain via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Jul 2016 14:14:35 +0000
- To: public-css-archive@w3.org
As while the case may be 'simpler' due to consistency and being a short word, I don't see that as an outstanding reason (good reason, but not great) to ignore design terminologies and implement them for future use especially in something so design-heavy as the CSS grid syntax. Again, this goes back to consistency between design and development. Hypothetical Scenario (and this does happen already when applying design to development): * Designer uses certain terminologies to explain design * Developer becomes confused as *they've heard some of the terms before but not all of them* * Developer and Designer eventually get frustrated over two terms that mean the same thing but they don't know what they mean as they never heard that term the other knows * This may lead to bickering over the use of words and need to find the right term to call it * Time and effort is then wasted over confusion when it could have been prevented. That's just one scenario but this happens when two words mean the same thing but can be very confusing for a lot of people, whether it's due to education, discipline etc. and this is why I want the appropriate properties and values to use design terms to make it a more understandable, easier flow for designers and developers instead of different words for the same thing. This is also make CSS Grid accessible and easier to learn from a designer's point of view as it will make the use of it easier to understand and how to apply CSS Grid to their designs. -- GitHub Notification of comment by iainspad Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/353#issuecomment-235906963 using your GitHub account
Received on Thursday, 28 July 2016 14:14:43 UTC