Notes from the Baton team.
How Baton works, what is new, and what we learn handing sites over.
How Can a Client Edit Their Own Website Without a CMS?
A client can edit text, images and links directly on the live page without a CMS. Here is how it works, what it can and cannot do, and when a CMS is still the better choice.
Read the postBaton vs a CMS: What Is the Difference and Which Do You Need?
A CMS and an in-page editor solve different problems. This is a plain comparison of how they work, what each is good at, and how to choose.
What to Look For in a Website Handover Tool
A checklist for choosing a tool that lets clients edit a finished website safely: control, undo, review, ownership and fit with your stack.
Who Actually Owns the Website? The Handover Question Nobody Asks Until It Hurts
Domains, hosting, code, analytics and email: a website is several things with several owners. Here is how to sort out who owns what before launch, and avoid the awkward emails later.
The Five-Minute Edit That Costs You Half a Day
Small post-launch edit requests look free, but each one carries a context switch. Here is how to work out what they cost and how to sort them so clients own the right ones.
How to Hand Over a Website to a Client Without Endless Back-and-Forth
Learn how to hand over a website, give clients the right editing access, and reduce repeated post-launch requests.