Compatibility
Check the combination of core, PHP, theme and extensions before updating.
BIG FISH / WordPress support
WordPress website maintenance
Maintain WordPress themes, plugins, the editor and integrations. Keep content editing familiar while checking how updates affect forms, catalogues and checkout.
One-off or ongoing · scoped around your project
Checkout
Theme + plugins
01Theme + plugins
02Basket test
03Compatible update
Fictional data. No production systems are connected.
SUPPORT × DESIGN × DEVELOPMENT
A familiar team.
The next stage of your product.
Manageable content
Develop editor blocks and templates so your team can build consistent pages.
A working store
For WooCommerce, check basket, payment, delivery and order transfer to the back office.
EXPLORE THE JOURNEY
Update a plugin.
Keep checkout working.
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
01 / WordPress support
Inventory
Record the active theme, extensions and custom work. Select an update and prepare a copy.
How the work is estimated ↘Checkout
Theme + plugins
01Theme + plugins
02Basket test
03Compatible update
Fictional data. No production systems are connected.
02 / WordPress support
Test
Check products, basket, delivery and sandbox payment on staging.
How the work is estimated ↘Checkout
Basket test
✓Theme + plugins
02Basket test
03Compatible update
Fictional data. No production systems are connected.
Check passed. The next stage can be approved.
03 / WordPress support
Publish
Release the compatible change and monitor new orders, errors and notifications.
How the work is estimated ↘Checkout
Compatible update
✓Theme + plugins
✓Basket test
03Compatible update
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.
WordPress 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
Core, plugins and PHP
Inventory active extensions, licences and custom code. Updating one component can affect a theme or integration, so compatibility is checked across the entire journey. The PHP version is selected for the requirements of the components in use.
Back up files and the database before changes and check that the backup is usable. Prepare updates on staging and record their outcome. Unused extensions are considered for removal after checking dependencies.
IN DETAIL / 02
Theme and block editor
Changes use appropriate extension mechanisms: a child theme, a custom plugin or project components. Editing third-party theme files without accounting for updates risks losing custom work.
New sections use reusable blocks and clear design constraints. Check long headings, different image sizes and mobile layouts. Editor instructions explain which elements the client can change independently.
IN DETAIL / 03
WooCommerce and integrations
Store support checks the whole order journey: product variants, stock, discounts, basket, delivery, payment and emails. Test payments use the provider’s sandbox, without charging real money.
We also examine repeated notifications and CRM exchange. Delivering an event twice should not create a second order. When an integration fails, record what has already been accepted and arrange retries without losing new orders.
IN DETAIL / 04
Performance and operation
Investigate database queries, plugins, images and external requests separately. Public page caching and a personal basket need different rules: one customer’s data must not be served to another.
Review administrator roles, unused accounts and backup access. Reports record changes, test results and remaining limitations. Support ends with a verified outcome, not the click of an update button.
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.