Resource Front End Standards

Agency developers should:

• Move quickly.
• Collaborate.
• Be consistent.
• Write quality code.

Following a style guide helps fulfill these requirements. When our code is cohesive it is easier to read and navigate; there is less friction in collaboration and innovation can flourish.

The purpose of our style guides is not to strictly enforce one way of writing code, but rather to provide a mostly agreed-upon approach. A project's developer lead or architect has the freedom to deviate from these standards when appropriate.

JavaScript

• JavaScript
• jQuery

Style Sheets

• CSS
• Sass

Markup

• HTML

Sublime Text Packages

To aid in style conformity, this project contains a number of "dot" configuration files.

• .sublime-settings Sublime Text Settings
• .editorconfig EditorConfig
• .jsbeautifyrc JsFormat
• .jshintrc SublimeLinter
• .csscomb.json CSSComb

Contributing

Resource is an OPEN agency and we strongly encourage collaboration and participation in the larger developer community. See our open issues and participate in the conversation.

Creating Issues

• Provide a descriptive title.
• Each issue should have at least two labels:
  1. Issue type (Flaw, Enhancement, etc.)
  2. Document affected (JavaScript, CSS, etc.)

About Resource

Resource is the largest independent digitally-led agency. We build OPEN brands that empower consumers through creativity, technology, and content. Marketers turn to us for our ability to innovate and deliver results.

License

2014 © Resource LLC
Licensed under the MIT License