A one-page questionnaire to help your team establish effective frontend guidelines, so that you can write consistent & cohesive code together.

• What are some general principles your team should follow when writing HTML? (for example, authoring semantic HTML5 markup, accessibility, etc. See these resources for inspiration)

• Are you using an HTML preprocessor (such as HAML, Jade, etc)?
• Are you using a templating engine (such as Mustache, Handlebars, etc)?
• Does your backend architecture influence the frontend markup in any way (for example, WordPress will add wp-paginate to a class in your markup)? If so, can you highlight these conventions?

• Spaces or Tabs?
• What does HTML commenting look like?

• What are some general principles your team should follow when writing CSS? (For example, modularity, avoiding long selector strings, etc. See these resources for inspiration)

• Is your team using a CSS methodology (such as SMACSS, BEM, or OOCSS? If yes, where is the documentation for that methodology?
• Are you deviating from the methodology in any way? If so, can you highlight these conventions?

• Is the team using a preprocessor (such as Sass or Less)?
• What are the guidelines for using that preprocessor (check out Sass Guidelines for inspiration)?
• Are you using a CSS base (such as Normalize or a reset)?
• Are you using any CSS postprocessors (such as Prefixfree or Autoprefixer)?
• Are there specific CSS techniques you're utilizing (such as critical CSS)?

• Is the team using a framework (such as Bootstrap or Foundation)? If yes, where is the documentation for that framework?
• Are you deviating from the framework in any way? If so, can you highlight these conventions?

• Spaces or Tabs?
• Spacing around rules?
• Grouping properties?
• What does CSS commenting look like?

• What are some general principles your team should follow when writing JavaScript? (See these resources for inspiration)

• Are you using a JavaScript framework (such as jQuery, Ember, Angular, etc)?
• Where is the documentation for those frameworks?
• Are you using any polyfills or shims (such as any of these)?
• What third-party scripts are dependencies for your project (such as scripts for form validation, graphs, animation, etc)?

(See these resources for inspiration)

• Spaces or Tabs?
• What does JS commenting look like?
• What patterns are you following?

• Are you using a task runner (such as Grunt or Gulp)?
• Are you using a dependency manager (such as Bower or Composer)
• Are you using any scaffolding tools (such as Yeoman)
• Are you using any tools to reinforce frontend style (such as Editor Config or linters)?
• Are any other specific pieces of software that are needed to work on this project?

• What version control system are you using for your frontend code (such as Git or Subversion)?
• Where is your version-controlled code hosted (such as Github or Bitbucket) ?
• Do you use a version control workflow (such as gitflow, centralized, feature-branch, etc)?
• Who's responsible for managing and governing the version controlled code??
• Where are issues tracked?

It's important to recognize the difference between "support" and "optimization". You should do your best to support as many environments as possible while simultaneously optimizing for the environments that make the most sense for your business and users.

• What browsers are you optimizing for?
• What devices are you optimizing for?
• Are you using a graded browser support system?
• Are there specific components that require more specific grading?

• Are you using a pattern library tool to document your front-end architecture?
• Where does your documentation live? What are the links to the documentation?
• Who's responsible for maintaining and governing the documentation?
• What happens when the guidelines are updated?

Feel free to modify or extend (such as adding specific sections for performance, accessibility, etc) this document for your own organization's needs. For questions, comments, additions, and corrections, please open an issue on Github and/or reach out to @brad_frost on Twitter.