A clear manager
Configure template variables and repeatable blocks, with instructions for editors.
BIG FISH / MODX support
MODX website maintenance
Maintain MODX templates, snippets, plugins and custom fields. Develop the website so editors can work comfortably and new sections follow a consistent model.
One-off or ongoing · scoped around your project
Service description / RU + EN
TV: description
01TV: description
02Snippet → template
03Public HTML
Fictional data. No production systems are connected.
SUPPORT × DESIGN × DEVELOPMENT
A familiar team.
The next stage of your product.
Reliable output
Check templates, event handlers and final HTML in each language.
Planned updates
Account for MODX, PHP, extras and custom modifications together.
EXPLORE THE JOURNEY
From a manager field
to the right page block.
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
01 / MODX support
Editor
A service description changes in a custom field. Check the language and template binding.
How the work is estimated ↘Service description / RU + EN
TV: description
01TV: description
02Snippet → template
03Public HTML
Fictional data. No production systems are connected.
02 / MODX support
Processing
A snippet reads the value and builds the block without reinterpreting embedded control syntax.
How the work is estimated ↘Service description / RU + EN
Snippet → template
✓TV: description
02Snippet → template
03Public HTML
Fictional data. No production systems are connected.
Check passed. The next stage can be approved.
03 / MODX support
Page
Verify the public URL, anchors, form and both themes after targeted cache refresh.
How the work is estimated ↘Service description / RU + EN
Public HTML
✓TV: description
✓Snippet → template
03Public HTML
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.
MODX 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
Templates and content structure
Record which resources use each template and which template variables are bound to it. Repeated cards become manageable blocks instead of requiring editors to change HTML.
A shared chunk can affect dozens of pages. Identify its usage before editing and select representative pages for checks. Include empty fields and long values in those checks.
IN DETAIL / 02
Snippets, plugins and events
Review rendering code, extras and event execution order. Pay particular attention where HTML, JSON and template syntax meet.
After a change, inspect final HTML for content, forms, canonical and language links and structured data. Saving a template successfully in the manager does not prove the visitor receives a correct page.
IN DETAIL / 03
Caching and languages
MODX, extras, PHP and the browser can cache different things. Identify the layer retaining stale data, invalidate it specifically and then check the public server response.
In multilingual projects, check localized fields, links and forms for each language. Editing Russian content must not silently replace English. Migrations preserve resource identifiers and mappings.
IN DETAIL / 04
Updates and recovery
Test MODX or PHP updates with extras and custom code on a copy first. Preserve files, the database and original version details. A major migration is separated from routine content edits.
Recovery planning accounts for template variable values and new materials: reverting a template should not discard editorial work. Instructions describe fields, event handlers and control URLs.
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.