-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create a writing style guide #4
Comments
This is old, but still relevant: http://24ways.org/2011/front-end-style-guides/ |
@nitriques, I also misunderstood the topic at first sight, this is about Writing Styleguides :) |
Well, it's content style really – which is both written style and presentation! Thanks @nitriques. |
My pleasure! Feel free to ping me here or on twitter for anything Symphony related :) |
I've completed a very early draft of the style guide. A couple of key things to bear in mind:
|
Seems perfect. Just do not quite understand this:
|
Contractions = can't, won't, don't, etc. With that clarification does it make sense, or still not? |
Now does! Thanks for clarification. |
I think I got confused in this part: ("don’t" typically sounds softer than "do not") The quotes is a suggestion. |
Ah, yes. Sorry when I drafted it I put the two words in italics, but when I copied it over from Google Docs this was lost!
|
One of the aims of the new documentation site is that it be as easy as possible for any member of the Symphony community to contribute.
While this is a really positive move, it does introduce one potential issue: consistency.
While there will always be a degree of quality control during the merging process, things will be much smoother if we have an established style guide we can point potential contributors to.
A couple of example style guides:
Tuts+
Webplatform.org
The text was updated successfully, but these errors were encountered: