Maintenance life cycle
Keeping themes and extensions alive: upgrades, compatibility, security fixes and retirement.
25 pages
- Adopting an abandoned theme Take over a theme whose author stopped maintaining it - ask first, then continue in the original repository if you are given access, or fork it under a new name; and how old extensions from the community archive can be…
- Forking a theme When to fork a theme and when to contribute instead, how to fork with history so you can still exchange changes, what the GPL asks of a fork, and how to tell users what your fork is.
- Contributing back upstream Send fixes and improvements back to the themes, extensions and the Exponential project you build on - what to contribute, how to prepare a change, and why it pays off in less maintenance for you and shared growth for…
- Pull requests to someone else's theme Prepare a pull request that a maintainer can merge quickly - small and focused, explained, tested, with screenshots for visual changes and no unrelated or private content - and how to respond to review.
- Keeping a fork in sync Bring the original theme's fixes into your fork regularly - an upstream remote, fetch and merge, resolving conflicts in templates, and keeping your own changes small so merges stay easy.
Documentation license
This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.
Exponential Copyright © 1998-2026 Exponential Foundation and 7x