Style terms
Consistency, readability, and the rules that make teams sane
Coding style is not about aesthetics — it is about communication. Consistent formatting, naming conventions, linting rules, and documentation standards reduce cognitive load and make code reviews faster and less painful. This category covers the conventions and tooling that help teams write code that reads as if one thoughtful person wrote it all.
Class Naming Convention PHP 5.0+
PHP classes must use PascalCase (UpperCamelCase) per PSR-1 — each word capitalised, no underscores, descriptive nouns or noun phrases.
2mo ago
style beginner
Code Documentation Standards PHP 5.0+
When, what, and how to document — the right balance between self-documenting code and explicit documentation for APIs, non-obvious decisions, and complex algorithms.
2mo ago
style beginner
Commit Message Best Practices
Clear commit messages that explain why a change was made, not just what — enabling efficient git log navigation, automated changelog generation, and informed code archaeology.
2mo ago
style beginner
CHANGELOG — Keeping a Good One
A human-readable log of notable changes per release — distinct from git commit history — following Keep a Changelog conventions.
2mo ago
style beginner
Conventional Commits
A commit message specification — type(scope): description — enabling automated changelogs, semantic versioning, and machine-readable history.
2mo ago
style beginner