Making a decision on the move-out branch about guides HOT 5 CLOSED

I think it's nice to have a convention for what the Heroku apps are named (such as "fdn-staging"), so we should rewrite that rule to be cosmetic.

I think the branch prefix is a cosmetic/convention thing. The important thing there is that there's consistency with naming.

Commit message formats are another cosmetic convention. That rule should probably be rewritten.

I agree on moving new project defaults and protocol guidelines out. I'd prefer to have code design guidelines in a separate document. It's nice to be able to read the entire document we have now and know that everything in there is cosmetic. I'd be fine with having them in the same repo if we're willing to have separate files.

I think there are three useful documents we could have here: Style, Protocol, and Best Practices.

from guides.

Sounds good on those specific examples.

Sounds good on one repo. How's this for a plan?

• Rename this style-guide repo to guides.
• Move style-guide/README.md to guides/style.md.
• Move protocol repo to guides/protocol.md.
• Delete protocol repo.
• Create guides/best-practices.md.
• Review what remains in development-handbook repo that we haven't covered.
• Move remaining development-handbook items into appropriate place in guides.
• Delete development-handbook repo.

from guides.

Yeah, I'm in favor of that plan with one addition: there are a few recipe-style things in the development-handbook that we could move to the blog. I left a bunch of comments on the pull request. I'd like feedback from at least one other developer before merging.

from guides.

there are a few recipe-style things in the development-handbook that we could move to the blog

Good call. A number of them were blog posts to begin with:

• font-face.md
• remote-pair-programming.md

from guides.

Closing this issue to focus discussion on #21.

from guides.