Skip to content
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

Open
johnpuddephatt opened this issue Jan 23, 2015 · 10 comments
Open

Create a writing style guide #4

johnpuddephatt opened this issue Jan 23, 2015 · 10 comments

Comments

@johnpuddephatt
Copy link
Contributor

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

@nitriques
Copy link
Member

This is old, but still relevant: http://24ways.org/2011/front-end-style-guides/

@bernardodiasc
Copy link
Member

@nitriques, I also misunderstood the topic at first sight, this is about Writing Styleguides :)

@bernardodiasc bernardodiasc changed the title Creating a style guide Create a writing style guide Jan 23, 2015
@johnpuddephatt
Copy link
Contributor Author

Well, it's content style really – which is both written style and presentation!

Thanks @nitriques.

@nitriques
Copy link
Member

My pleasure! Feel free to ping me here or on twitter for anything Symphony related :)

@johnpuddephatt
Copy link
Contributor Author

I've completed a very early draft of the style guide. A couple of key things to bear in mind:

  • Some of this is going to be quite subjective. It's a style guide after all. Disagreement with it is very much welcomed
  • There is no need to aim for this to be exhaustive from the outset. Instead we should aim to provide some basic guidelines that would steer a newcomer in the right direction, and then add to it over time if we notice common problems in submitted documentation

Draft here on the wiki

@bernardodiasc
Copy link
Member

Seems perfect.

Just do not quite understand this:

Limited use of contractions is okay because it makes your writing sound natural, and can add nuance to your writing (don’t typically sounds softer than do not).

@johnpuddephatt
Copy link
Contributor Author

Contractions = can't, won't, don't, etc.

With that clarification does it make sense, or still not?

@bernardodiasc
Copy link
Member

Now does! Thanks for clarification.

@bernardodiasc
Copy link
Member

I think I got confused in this part: ("don’t" typically sounds softer than "do not")

The quotes is a suggestion.

@johnpuddephatt
Copy link
Contributor Author

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!

On 23 Jan 2015, at 23:27, Bernardo Dias [email protected] wrote:

I think I got confused in this part: ("don’t" typically sounds softer than "do not")

The quotes is a suggestion.


Reply to this email directly or view it on GitHub #4 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants