johnpapa/angular-styleguide

This repository is a style guide, a written set of rules and conventions for Angular development teams. Angular is a popular framework for building web applications. The problem it addresses is consistency: when a team builds a large app together, different developers can write code in very different ways, making it hard to read each other's work, onboard new members, or maintain the codebase over time. A style guide solves this by agreeing upfront on how things should be structured and written, and explaining the reasoning behind each choice. The guide covers practical decisions like how to name files, how to organize code into modules, and which patterns to follow when building Angular components and services. It includes versions for both Angular 1 and Angular 2. The Angular team reviewed and endorsed this guide, which is why it became a widely adopted community reference. You would use this when starting an Angular project with a team and wanting a solid starting point for coding conventions, or when trying to improve consistency in an existing codebase. The content is documentation only, there is no runnable code. It is language-agnostic in the sense that it is written prose, though the small amount of supporting editor tooling in the repo is in Vim Snippet format.