Recent changes
35934 changed pages · Atom feed · Recent comments · Recently added · Recent ratings
Wednesday November 04 2026
- A CSP audit for every release (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Check before each release that the theme still works under a strict Content Security Policy - report-only mode on a test siteaccess, the browser console, a grep for inline code, and external resources. - Declaring compatibility (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Tell users and tools which Exponential and PHP versions a theme release works with - composer.json require, the README's requirements, extension.xml dependencies and the release notes - consistently. - Keeping dependencies up to date (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Keep the libraries, fonts, icon sets and extensions a theme depends on current - an inventory, where updates are announced, testing an update, and checking licenses again. - Deprecating a setting or a template (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Step by step - rename a theme setting while still reading the old name, replace a template while keeping an include of the old one, and remove both later - with the changelog entries for each step. - A deprecation policy (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Decide and publish how your theme retires settings, templates, view modes and operators - announce, keep working, warn, remove in a later step - so users have time to adapt. - End of life (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
End maintenance of a theme responsibly - decide, look for a successor or new maintainer first, give notice, publish a last release, keep it installable, and archive - so users are never stranded without warning. - Following Exponential releases (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Where to watch for changes that affect a theme - the changelogs in doc/changelogs, release tags and GitHub releases of the repository, the upgrade notes in doc/eng-us/bc, project news and RSS - and a weekly routine. - Forking a theme (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
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. - Handling security reports (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
What to do from the moment a security report arrives - acknowledge, reproduce privately, assess, fix, release, credit - and what to do when the report arrives in a public issue. - Handing a theme over to a new maintainer (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Pass a theme to a new maintainer so users notice nothing but continuity - choosing someone, a handover period, documentation, access, the repository and package, and announcing it. - JavaScript library upgrades (jQuery 4, no YUI) (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Bring a theme's JavaScript up to date with the libraries Exponential ships - jQuery 4.0.0 with Migrate and jQuery UI 1.14.2 through ezjscore, YUI removed - what to search for, what to replace, and how to test. - Keeping a fork in sync (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
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. - Checklist: one maintenance cycle (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
One maintenance cycle of a theme as a checklist - watch, test, audit, fix, release, communicate - each item linked to the page that explains it. - The maintenance life cycle: start here (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
The map for keeping a theme alive after its first release - following Exponential releases, upgrade testing, per-release accessibility, CSP and performance audits, security fixes, deprecation, end of life, handover… - A maintenance calendar (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
A rhythm for theme maintenance - weekly watching, per-release testing and audits, quarterly dependency and license reviews, a yearly review of support policy and compatibility - as a calendar to adapt. - A performance audit for every release (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Check that a release did not make the theme slower - page weight, number of requests, image sizes, layout shift and largest contentful paint on the page list - and compare with the previous release. - PHP version compatibility (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Keep a theme's PHP code (operators, modules, classes) working on every PHP version Exponential supports - PHP 8.0 is the oldest, PHP 7.4 usable without support - with php -l per version, what typically breaks, and how… - Publishing a security release (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
Release a security fix for a theme - fix, version, tag and release first, then describe the problem plainly with affected versions and the action users must take, and tell the channels where your users are. - Pull requests to someone else's theme (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
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. - Reading a changelog as a designer (Updated, Markdown page)
Markdown documentation (help center) · Maintenance life cycle · Changed 01:08 pm
What to look for in an Exponential changelog when you maintain a theme - templates you override, design settings, operators, JavaScript libraries, security headers, PHP versions, accessibility - with real examples from…
