Front-End standards documentation has long been a goal of ours as an established team of development professionals. The pace of team member additions and new projects made this a priority at the tail end of 2017. Today, we’re proud to introduce and share with everybody, O3’s “Front-end (HTML & CSS) coding standards.”

Why Documentation?

By documenting an agreed upon set of standards and best practices for our development team, we’re able to provide a consistent bar for development quality, making sure our code is formatted consistently (like one developer wrote it regardless of team size), and easily onboard team members.

In addition, these standards and the maintenance of them is meant to spur discussion about process and the evolution of web standards – ultimately helping us be better developers and better code shepherds for each other and our clients.

Our Use

The efficiencies in having standards documentation are huge. Whether it be onboarding a developer to our team, adding a developer to a new project, or aiding in maintaining a high level of quality and consistency of code on a long term project with a large team, our development process has already benefited greatly by following these best practices.

The Benefits

We hope that you and your team learn from our standards and find ways to implement and evolve them to suit your development team’s needs. As we continue to refine our processes and our front-end best practices evolve, we’ll continue to update these standards.

Check out the front-end guidelines repo!

Were these best practices helpful? Are they something you could see your team using or do you have thoughts on how we can update them? Let us know how you’re using these standards to succeed by contacting us below!