We write a plain-language guide for your content team — how to create and publish content, use key features (blocks, custom fields, media), and avoid common mistakes — tailored to your actual site rather than a generic WordPress tutorial.
Editor guide for content team
A plain-language guide for your content team, written for how your site actually works.
- 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
- Admin access to understand the actual editing experience your content team uses
- Confirmation of which tasks matter most to include
- Your preferred format (a document, a series of short guides)
This or something else?
| You want a plain-language guide specific to how your content team actually publishes on your site | This fix covers it |
| You want a recorded video walkthrough instead of a written guide | Recorded admin walkthrough video, a different format for similar content |
| You want a formal, step-by-step SOP specifically for publishing, not a general guide | Publishing standard operating procedure, a more procedural, checklist-style document |
| You want WooCommerce-specific operations documented, not general content editing | WooCommerce operations manual |
What we do
- Review the actual content creation and publishing experience on your site
- Identify the tasks and features most relevant to your content team
- Write clear, plain-language instructions tailored to your specific setup
- Include common mistakes worth flagging
- Review for clarity and accuracy
What is included
- A tailored editor guide for your content team
- Coverage of the tasks and features most relevant to them
- Notes on common mistakes to avoid
- A clarity and accuracy review
Not included
- A recorded video walkthrough — a separate, different format if you’d prefer that instead
- A formal, procedural SOP for publishing specifically — a separate, more structured document
- WooCommerce-specific operational documentation — a separate, related document
- Ongoing updates as your site’s editing experience changes
Questions about this fix
How is this different from WordPress's own documentation?
This is specifically tailored to how your site actually works — your theme's blocks, your custom fields, your specific workflow — rather than generic instructions that may not match your actual setup.
Would a video walkthrough be more useful than a written guide?
Depends on your team's preference — some people learn better from written reference material they can search, others from watching a video; we can produce either, or discuss which fits your team better.
Will this cover WooCommerce product editing too?
General content editing, yes; if WooCommerce-specific operations are a significant, separate need, the dedicated operations manual covers that in more depth.
How technical does this assume the reader is?
Written in plain language for someone who needs to publish content but isn't necessarily technical — no assumed familiarity beyond basic computer use.
Does this need updating if the site's editing experience changes?
Yes, a significant change (a new page builder, new custom fields) would need the guide updated to stay accurate.
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.