BooshCMS features
A CMS your client can use,
and actually owns
You build the site and the components. They write, arrange and publish. Nobody meets a branch, a filename or a class name, and the content never leaves their repository.
Posts, and everything else that repeats
The schema you wrote becomes the form they fill in.
Blog posts, team members, reviews, FAQs: anything uniform and repeatable is a collection, one Markdown file per entry. The editing form is generated from that collection’s schema, so a field you typed as a date gets a date picker and a field you typed as a choice gets a list.
- One file per entry, so two people can edit at once
- The form is generated, never hand-built
- Pictures get a picker, dates get a date field
- Save without publishing, using a draft flag
Pages built from your components
They arrange the blocks. You decide what the blocks are.
A page is an ordered list of sections, and the sections on offer are exactly the components you built. The client adds, reorders and removes them; they cannot invent a new one, and they cannot break the design by trying.
- Add, reorder and remove sections
- Each block’s form comes from its Props interface
- Only the components you built are offered
- Nothing in a page can be lost on save
A preview that is the actual site
Full, tablet and phone: rendered, not approximated.
The preview panel runs the real site with the real components and the real CSS. What the client sees while they are editing is what visitors will get, at whichever width they choose to check.
- Full, tablet and phone widths
- The real components, not a mock-up
- Updates as they type
- Refresh on demand when they want it
Images and files
Drop one in. It ends up in the right folder.
Pictures are added through a picker, stored in the repository alongside the content, and given the alt text the schema asked for. The client never chooses a path, and never has to think about where a file should go.
- Drag in a picture, get a picker everywhere it is used
- Alt text prompted where the schema requires it
- Files committed with the content they belong to
- No separate media library to keep in sync
Publishing, on your terms
Straight live, or past you first.
Set the publish mode when you hand the site over. Direct means their save goes live; review means it waits for you. Either way the change is an ordinary commit, so the site’s history is the git history and nothing is hiding in a database.
- Direct publishing where you trust it
- A review step where you would rather look
- Every change is a normal commit
- Unpublished changes are counted and shown
The content stays theirs
Markdown, in their repository, forever.
There is no platform holding the content and no monthly bill arriving with your name on it. If the client ever stops using BooshCMS, or stops working with you, they keep every word and picture, in a format anything can read.
- Markdown and images in their own git repo
- No CMS server to host or patch
- No seat licences as their team grows
- Leaving costs them nothing but the app
Safe while you are still building
They can write before the site is finished.
The client can be adding content while you are still working on components, because the two live in different places. Their edits and your commits meet in git rather than fighting over one document, and the app tells them plainly when a page is not theirs to edit.
- Listing pages and dynamic routes stay read-only
- A page you have not marked editable is view only
- Their work and yours reconcile in git
- The app says which pages they can change
Ready to try BooshCMS?
Buy it once and it is yours, on your own machine, with your data in a file you can open. If it turns out not to suit how you work, tell us.