The CMS your team can’t break
I'm editable. So is everything on this page with a dotted line around it. Click me and start typing.
Rewrite this page. Every word on it is live, no admin panel required. Hit publish when you’re done and see how far you get.
- Click any text and type over it.
- Swap the photo further down, then try to publish it with no alt text.
- Change who you are and watch parts of the page lock.
- Build a page by dragging sections onto a blank one.
Nothing you do here reaches my site. Your changes stay in this browser.
The page builder
Need a new page? Drag the sections in.
Need a new page? Tap to add sections.
You get a menu of sections I've designed for your site. Drop them onto a blank page, put them in any order, pick light or dark or which side the image sits on, then click in and write. Nobody's nudging pixels, so every page you build still looks like the rest of the site.
You get a menu of sections I've designed for your site. Add them to a blank page, reorder them, pick light or dark or which side the image sits on, then tap in and write. Nobody's nudging pixels, so every page you build still looks like the rest of the site.
Sections
Drag a section onto the page, or press Add. Nothing here is saved.
Tap Add to drop a section onto the page. Nothing here is saved.
A blank page. Drop a section here.
Images
Swap the photo. Then try to publish without alt text.
Most systems let you publish an image nobody using a screen reader can understand. Tiffin refuses.
Required, because someone using a screen reader gets this instead of the photo. Tiffin writes the suggestion; you decide whether it's right.
Go go gadget permissions
Change who you are. Watch the page change with you.
This is the part a website builder can't do. One permission check decides who may edit each content element, and the same check runs again on the server, so the buttons and the rules can never disagree.
You can edit everything on this page, and take over a content element somebody else is editing.
Your center's own page
A director can write here, because this content element belongs to their center. Try it, then switch to Member.
Another center's page
Same site, different center. A director of Center A can read this and nothing more. The server agrees.
The audit log
Everything you just did, written down
Who changed what, and when, with the before and after kept for every save. When a page is wrong on a Monday morning, this is the difference between knowing and guessing.
- Nothing yet. Change something on the page and it shows up here.
What it does
What's holding this together
Everything above, you did on your own. These are the parts that keep it predictable once your whole team has a login and the site is already live.
A page builder
Pick from a menu of sections designed for your site, drag them onto a blank page and write. Every new page matches the rest of the site, because nobody's placing anything by hand.
One permission check
One function decides who sees the Edit button and who gets to save. They can't drift apart. That's how most custom setups leak.
Drafts, and a visitor's eye view
Your draft is yours until you publish it. Everyone else, logged out included, still sees the published version, and "preview as visitor" shows you exactly what they get.
Every version kept
Every save, publish and restore is stored with its author and the time in Eastern. Restore an old one as a draft, read it, then publish it normally.
Two people, one content element
Editing takes a lock on that content element. Everyone else sees "Dana is editing" and their edit buttons gray out. A lock whose owner closed their laptop expires on its own, and an admin can clear one in a click.
Nobody overwrites anybody
Your editor remembers the version it opened. If somebody saved first, your save is refused with "someone else saved a newer version" and a reload button. Nothing goes missing without you being told.
Alt text, enforced
Publishing is refused while any image in the draft has no alt text. Not a warning you can click past. For anyone taking federal money, that's a requirement.
Paste that can't break the page
Paste from Word and the formatting is dropped, with a note saying what went. A heading has no line break in it at all, so nobody can snap your layout in half with the Enter key.
The page updates itself
Open pages check for new content every few seconds while you're looking at them, and stop when you walk away. Publish something and a visitor reading it sees it in about five seconds.
The flow
What happens when you hit publish
You click Edit
That takes the lock on that content element. Anybody else sees your name on it and can't edit it until you publish. The rest of the page stays open to them.
You save a draft
Nothing autosaves. Your draft is stored as a new version, and visitors keep seeing the published page.
You check it as a visitor
One click shows you the published-only view, so you can see what everyone else sees before you commit.
You publish
The draft becomes the live version in one statement, with an audit row. If an image is missing alt text, this is where it stops.
The lock goes back
Your lock is released and anyone reading the page sees your change within about five seconds, without reloading.
Questions
What people ask about Tiffin
Do I get Tiffin with a website build?
Why not just use WordPress or Squarespace?
What happens if two people edit the same thing?
Can I get back something somebody deleted?
Do my editors need training?
Does it work for a university center?
What does it cost?
The rest of the system
A CMS on its own is one piece
Want this on your own site?
Twenty-five minutes. Tell me who needs to publish, what they keep getting stuck on, and I'll tell you whether this is the right fit or whether something simpler would do.