New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is 'Keep it short and simple' too vague? #29
Comments
No it is not too vague to be helpful as a "Tip." In fact, it perfectly models what it advocates by being short and simple itself. |
"Keep content short and simple" it straight forward and self explanatory. |
agree |
Prefer "keep content short and simple" |
hummm.... a few points on this:
/me teases Kevin on this -- we need to "eat own dog food" on with this one! -- it's kinda like tersify! ;-) |
I agree with Shawn about the qualifier. Sometimes the intent of web content is not to keep it short and simple but to give very detailed information when teaching about something, for example the WCAG 2.0 page is not to be kept short and simple. I think we an use "Keep it Short and Simple". This is in the writing section of tips, so people should know "it" is about the writing/content of the web pages. |
My initial thought is to remove this because it suggests "dumbing things down" or imposing a newspaper's editorial writing style. Upon further reflection, I think this advice is for making all content more accessible, and should be kept. |
[EOWG Meeting 26 Jun](http://www.w3.org/2015/06/26-eo-minutes.html#item03): Resolved to add qualifier to initial sentence in tip to mention context.
EOWG Meeting 26 Jun: Resolved to keep a form of 'Keep content short and simple'. Further discussion lead to alternative suggestions captured in #42. EOWG Meeting 26 Jun: Resolved to add qualifier to initial sentence in tip to mention context. |
Refers to Keep content short and simple tip in 'Writing'.
The tip had referenced the KISS (Keep it simple, stupid) principle which is a common adage in design. The 'it' in this case may be too vague to be helpful?
The text was updated successfully, but these errors were encountered: