awesome-guidelines
Programming style, best practices, and coding conventions.
A curated collection of links to coding style guides and best-practice documents covering dozens of programming languages, frameworks, platforms, and development tools in one place.
Awesome Guidelines is a curated collection of links to coding style guides and best-practice documents across a wide range of programming languages, frameworks, and development tools. If you have ever needed to know what conventions a given language community recommends for naming variables, formatting code, or structuring a project, this list points you to those resources in one place.
The collection is organized by category. The programming languages section covers dozens of languages, from common choices like Java, Python, Go, and JavaScript to less common ones like Brainfuck, Fortran, and Erlang. Each entry links to one or more official or community-maintained guides that describe how code in that language is typically written and why.
Beyond individual languages, the list also covers development environment setup guides, platform-specific conventions for systems like Android and iOS, style guidelines for popular frameworks, and recommendations for content management systems. There is also a tools section with links to guidance on things like version control workflows and documentation practices.
This kind of list is useful when you are starting a project in a language you have not used much, when you are joining an existing team and want to match their conventions, or when you want to review what the broader community considers good practice. The entries include both official sources from language designers and well-known community efforts, such as the Google style guides and the Airbnb JavaScript guide.
The repository is part of the Awesome series, a broader GitHub tradition of community-maintained link collections on specific topics.
Where it fits
- Find the official or community-recommended style guide for a programming language you are starting to use on a new project.
- Onboard onto a new team by reviewing the naming, formatting, and structure conventions the broader community follows for your stack.
- Check what formatting and project structure rules apply to a framework or platform such as Android or iOS before writing your first file.