Editorial workflows
Check categories, publishing and staff access to content.
BIG FISH / Joomla support
Joomla website maintenance
Maintain Joomla articles, navigation, modules and extensions. Develop the website while preserving URLs, editor permissions and its established visual identity.
One-off or ongoing · scoped around your project
Article / News section
Article draft
01Article draft
02Editor review
03Article published
Fictional data. No production systems are connected.
SUPPORT × DESIGN × DEVELOPMENT
A familiar team.
The next stage of your product.
Consistent navigation
Preserve menu, language and page relationships when restructuring.
Compatible extensions
Plan updates around components, modules and the template.
EXPLORE THE JOURNEY
A new article.
A controlled publication.
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
01 / Joomla support
Draft
An editor prepares an article and chooses its category. Publishing access follows their role.
How the work is estimated ↘Article / News section
Article draft
01Article draft
02Editor review
03Article published
Fictional data. No production systems are connected.
02 / Joomla support
Review
The responsible person checks modules, menu placement and mobile layout.
How the work is estimated ↘Article / News section
Editor review
✓Article draft
02Editor review
03Article published
Fictional data. No production systems are connected.
Check passed. The next stage can be approved.
03 / Joomla support
Publish
The article appears at its agreed URL. Check language, access and related pages.
How the work is estimated ↘Article / News section
Article published
✓Article draft
✓Editor review
03Article published
Fictional data. No production systems are connected.
A CLEAR PROCESS
See the result.
At every stage.
- 01
Request and priority
Clarify the outcome, business impact and conditions.
- 02
Estimate and agreement
Agree scope, cost and acceptance criteria before starting.
- 03
Work and validation
Prepare changes on a copy and verify related journeys.
- 04
Release and report
Publish the agreed result and update documentation.
SCOPE AND PRICING
The support
your product needs.
Hour packages are available for ongoing support. Individual tasks receive a separate estimate. Hosting, licences, third-party services and urgent work terms are specified in the proposal; they are not automatically included.
Joomla supportOne-off or ongoing
A precise quote follows a discussion of your project.
DOCUMENTATION
Project knowledge.
Stays with you.
Document coverage follows the agreed task. Secrets are stored separately from shared instructions.
Project record
Environments, versions, services, owners and access-management rules.
Release procedure
Pre- and post-release checks, backup and recovery conditions.
Change log
What changed, when it was released and how to verify it.
Team instructions
Content editing and new features without editing source code.
IN DETAIL / 01
Articles, menus and modules
Joomla output depends on categories, menu items and module assignments as well as articles. Before adding a page, check how it fits into this structure.
When moving content, record old URLs and necessary redirects. Navigation, breadcrumbs and language associations should lead to the intended content rather than an unintended component view.
IN DETAIL / 02
Permissions and publishing
Define author, editor and administrator roles. Test each role with dedicated accounts, including access to restricted material and publishing rights.
If approvals are used, document stages and owners. Instructions cover the journey from draft to publication and how to correct published content.
IN DETAIL / 03
Extensions and templates
Inventory third-party components, modules and plugins. Check compatibility with the intended Joomla and PHP versions, licences and custom modifications. Major version transitions are estimated as separate migrations.
Separate view customizations from files replaced by updates. Check forms, search, login, menus and custom components on staging, then repeat essential checks in production.
IN DETAIL / 04
Operation and documentation
Check file and database backups, email delivery and background schedules. Cache settings account for personalized pages.
The project record lists extensions and menu and module configuration rules. After release, the client retains clear everyday instructions and a change record for future maintenance.
FAQ
Before we start.
Do you only support your own projects?
Our main approach is to continue developing products we built. Projects from other teams are reviewed first: code, access and risks determine whether ongoing support is feasible.
Do we need a monthly subscription?
No. Individual tasks can be agreed separately. Ongoing support suits a regular stream of changes and a planned backlog. Use and rollover of hours are defined in the contract.
How quickly will you fix an error?
We first identify impact and cause. Response times, working hours and urgent contact arrangements are agreed separately. Resolution time depends on the fault and external services.
What do we receive?
A verified outcome, change description and report for the agreed scope. New functionality comes with updated instructions. Documentation depends on the task.
BIG FISH / MAINTENANCE
Find the right solution
for your project.
NEXT STEP
Your product can do more.
Let’s keep it moving.
Tell us what you want to change or which problem to solve. We will start with the task and propose a suitable way to work.