We produce a technical architecture overview — hosting, key integrations, how major systems connect — written for a technical but non-code-level audience, distinct from deep, line-by-line code documentation which is a separate, more granular product.
Technical architecture document
A technical architecture overview — hosting, integrations, how systems connect — for a technical, non-code audience.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to the site, hosting, and key integration configurations
- Confirmation of the intended audience, so the level of detail is pitched correctly
- Your preferred document format
This or something else?
| You want a technical overview of how your site’s major systems fit together, for a technical but non-code-level audience | This fix covers it |
| You want deep, code-level documentation of custom functions and hooks | Theme & codebase documentation generation, in the Integrations & Automation bucket, a more granular, developer-facing version |
| You want hosting specifically documented in detail, not the broader architecture | Hosting & infrastructure summary document, a more focused, related document |
| You want this as part of a full developer onboarding bundle | Onboarding pack for incoming developer |
What we do
- Review hosting, key integrations, and how major systems connect
- Document this at a level suited to a technical but not necessarily code-fluent audience
- Note any significant architectural decisions or constraints worth flagging
- Compile into a clear, organised overview document
- Review for accuracy before finalising
What is included
- A technical architecture overview document
- Coverage of hosting, integrations, and system connections
- Notes on significant decisions or constraints
- A final accuracy review
Not included
- Deep, code-level documentation of custom functions and logic — a separate, more granular fix
- Detailed hosting-specific documentation beyond the architectural overview — a separate, related document
- Fixing anything identified while documenting
- Ongoing updates as the architecture changes
Questions about this fix
Who is the intended reader for this document?
Someone technical enough to understand system architecture but who doesn't necessarily need or want to read actual code — a technical stakeholder, a new hire before they dive into code specifics, or you yourself for reference.
Is this the same as the code-level documentation?
No, that goes into actual functions and hooks; this stays at the level of how major pieces fit together, without the code-level detail.
Will this include specific server configuration details?
At a summary level relevant to the overall architecture — for a deeper, dedicated hosting document, that's a separate, more focused fix.
How is this useful if I'm not planning any changes to my architecture?
It's valuable as a reference regardless — for troubleshooting, for a new team member's context, or simply for your own clarity about how everything actually fits together.
Does this need updating if I add a new integration?
A significant architectural change would benefit from a documentation update to stay accurate and useful.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.