This documents your site’s actual data structure — every custom post type, taxonomy, and field group, what they’re for, and how they relate to each other — useful when a site’s structure has grown organically over time and nobody currently has a clear, complete picture of it written down anywhere.
Data structure documentation report
Every custom post type, taxonomy, and field documented in one clear reference.
- 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 review the site’s code, database, and admin structure comprehensively
- Confirmation of any specific areas you’re most interested in having documented in detail
- Your preferred report format, if you have one
This or something else?
| You want your site’s custom post types, taxonomies, and field structures documented comprehensively | This fix covers it |
| You want a specific data issue diagnosed and fixed, not documentation of the current structure | The relevant specific fix instead, once you know what needs fixing |
| You want field data mapped to schema, not documented for internal reference | Custom field to schema mapping, a different kind of output |
| You’re planning a significant restructuring and want recommendations, not just current-state documentation | Worth discussing directly — this documents what exists, recommending changes is a separate, further conversation |
What we do
- Review the site’s custom post types, taxonomies, and field groups comprehensively
- Document what each is for and how they relate to each other
- Note any inconsistencies or unclear naming conventions found along the way
- Compile findings into a clear, organised, written reference document
- Include practical detail (field keys, post type slugs) useful for future development work
- Review the documentation for accuracy before considering it final
What is included
- Comprehensive documentation of custom post types, taxonomies, and field structures
- Clear explanation of what each is for and how they relate
- Notes on any inconsistencies found along the way
- A written, organised reference document
Not included
- Fixing any inconsistencies or issues found while documenting — a separate, related fix if you want those addressed
- Recommending a restructured data model — this documents current state, not future direction
- Ongoing updates to the documentation as your site’s structure changes
- Documenting third-party plugin functionality unrelated to your custom data structures
Questions about this fix
Why would I need this if the structure already works fine?
Working structure and understood structure are different things — this is most valuable when the original builder is no longer involved, a new developer needs to get up to speed quickly, or nobody currently has a clear, written picture of what exists and why.
Will this fix any inconsistencies you find while documenting?
Not automatically — we note what we find, and fixing those is a separate, related task you can choose to pursue once you see what's actually there.
How detailed will this documentation actually be?
Detailed enough to be genuinely useful for future development work — specific field keys, post type slugs, and relationships, not just a high-level, vague summary.
Will this help if I'm planning to hire a new developer?
Yes, this is exactly the kind of documentation that helps a new developer understand your site's structure quickly, rather than needing to reverse-engineer it from scratch.
Does this need to be updated if I add new custom fields later?
The documentation reflects the structure as of when it's produced — keeping it current as you add new structures would need a follow-up update at that time, since it's not something that maintains itself automatically.
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.