Build a Website Playbook Your Team Actually Uses

When only one person knows how your site works, updates stall. A short, structured playbook gets every teammate aligned without bloating your to-do list.

What to include

Tech overview: explain that the site is built in Astro, deployed via Cloudflare Pages, and performance-tested.
Update paths: outline when to use the Fernside CMS and when to submit a support ticket.
Approval rules: state who signs off copy, design, and analytics changes.
Asset inventory: list where logos, photography, and testimonials are stored.

Format ideas

A single Notion or doc page with anchored sections.
Embedded Looms showing how to edit the CMS or brief a new component.
A printable checklist for people who prefer offline workflows.

Sample checklist

[ ] Clarify the desired outcome and deadline
[ ] Gather all copy, imagery, and links
[ ] Decide if it’s a CMS edit or ticketed task
[ ] Reference the relevant page (URL + screenshot)
[ ] Log success metrics to review later

Keep it visible

Link the playbook inside your CMS dashboard.
Mention it during onboarding for new team members.
Review it quarterly alongside your site performance report.

Outcomes you’ll notice

Faster approvals because everyone follows the same system.
Cleaner analytics as updates are documented and measured.
Less stress when someone is on leave—any teammate can action the basics.

Want help assembling it?

Every week without a clear playbook is another week of miscommunication, stalled updates, and missed deadlines. The longer you wait, the more institutional knowledge stays locked in one person’s head.

We can facilitate a short workshop, map your workflows, and provide a branded playbook template as part of a Studio Site engagement. We only take on a few builds each month — check availability and we’ll confirm your earliest slot within 24 hours.