The community for developers
Developers build most of what the community shares: sites, extensions, fixes and tools.
Contents
Learning
| Resource | What it is |
|---|---|
| Develop with Git | Installing and working with Git clones of the kernel and extensions |
| Extension development | A book in eight parts, from user to extension developer to maintainer |
| Template language and Template operators | The template language reference |
| Standards | Coding standards, naming prefixes, security, testing |
| Training books | "three original developer training books (700+ pages combined)" (Community places) |
| Application creators, Website creators | Building applications and sites |
Working with the code
- Install from Git clones so that a fix is "a branch in your fork and a pull request away" (When something goes wrong).
- Watch the repositories you depend on; read the changelogs (Staying informed).
- Test your extensions against
mainbefore a release (Testing releases).
Giving back
| Contribution | Page |
|---|---|
| Fix a bug or add a test in the kernel | Contributing code |
| Review someone else's pull request | Reviewing and being reviewed |
| Publish an extension | Sharing extensions and themes |
Add a composer.json to an extension that lacks one, a call for volunteers on the roadmap | Roadmap |
| Answer technical questions | Answering questions |
| Mentor a new developer | Mentoring |
Rules every developer meets
- Commit messages with
Added:,Updated:,Fixed:,Removed:orRenamed:; the manifest line for every changed file; squash and rebase (CONTRIBUTING.md). - New code uses the
expprefix; existingeZ*identifiers are never renamed (Naming prefixes). - The CLA for kernel contributions (The CLA explained).
- AI-assisted code: you are responsible for it and say when a substantial part was generated (
CODE_OF_CONDUCT.md).
Related pages
- Paths through the community
- Talking points for developers
- Ecosystem: start here
- Develop with Git
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.