Staging-first updates
Extensions and core updates are tested before they reach the live site.
A Joomla site needs a routine: tested updates, working backups, security checks and someone who notices before a small issue becomes an outage. A care plan gives you that routine without hiring a full-time developer.
No obligation. We review the current site before recommending a plan or quoting one.
A plan should make the site safer and more predictable, not just move a monthly invoice.
Extensions and core updates are tested before they reach the live site.
A backup is only useful if it can be restored. We verify the process.
Access review, update discipline, file monitoring and clear escalation steps.
Checks that catch the site being down before a customer does.
Small content and template changes without opening a new project each time.
What changed, what was found and what needs a decision next.
The first month is about establishing a baseline and a safe update rhythm.
We review the version, extensions, host, backups and access.
Critical compatibility or security issues are scoped before a routine plan starts.
We agree secure access, a staging path and a rollback method.
The first batch is applied and tested with your approval.
Updates, checks and a report on an agreed schedule.
Organisations that want a named technical owner without a full-time hire.
Enquiries, orders or member access should not depend on “someone will look at it”.
A plan gives you capacity and a clear escalation path.
A schedule and staging process turn maintenance into a routine.
Keep the current site stable while the new one is prepared.
“They are very knowledgeable about Joomla!® and were very helpful throughout the project, even though we were not 100% sure about what we wanted to do.”
What is and is not included.
Staging-first updates, backup checks, security monitoring, uptime checks and a monthly report. Edit time and response targets are agreed per plan.
We can maintain it while a migration is planned, but Joomla 3 is unsupported. A care plan is not a substitute for moving to a supported release.
If a change we applied causes the issue, fixing it is part of the service. Pre-existing problems or new feature work are scoped separately and explained before work begins.
In most cases, yes. We review the hosting, PHP and backup setup first and only recommend a move if it is necessary for support or performance.
Plans are quoted according to the number of sites, update complexity, response expectations and edit allowance. We confirm the scope in writing before billing.
Pick the next question that matches your situation.
Send the site address, version and what you worry about most. We will review the baseline and propose a plan in writing.