Jekyll CMS for teams
Let your marketing team edit your Jekyll site
A git-based CMS for non-technical editors. Your team writes posts, updates pages and reads form submissions. You keep the repo, and every save is a commit.
Connect a GitHub repo in a few minutes
FOR TEAMS
Stop being the bottleneck for typo fixes
Testimonials, blog posts and a wrong date on the pricing page should not wait for a developer. Your teammates, like Sam in the dashboard above, edit the site themselves, and you review the commits.
-
MARKETING SITE
Product and startup marketing sites
Marketing changes pricing copy, swaps testimonials and posts launch notes on a site like voyija.com, while the developers ship the product.
-
BLOG
A company blog with several authors
Each author has their own login to draft and publish posts. Every post lands in the repo as a commit you can review.
-
DOCS
Docs and changelogs edited by non-devs
Support and product write help pages and release notes in Markdown, without opening a pull request.
-
VOLUNTEERS
Nonprofit and club sites run by volunteers
Volunteers post news and events and answer the contact form. The site stays on free static hosting, and whoever built it is not on call.
Sites running on M.A.B.E.L.
-
willbarker.dev Personal site and blog
-
voyija.com Travel planning app
-
mabelstack.com This site
You build it in git. Your team needs to edit it.
Mabel sits on the repo you already have and writes plain files back to it.
-
01
Connect the repo
Sign in with GitHub and pick the repository. Posts, pages and data files are found automatically.
-
02
Set up what editors can touch
Define forms and the structure of data files. Everything else stays as you wrote it.
-
03
Invite editors
Each editor gets their own login, limited to the sites you choose. They edit and read submissions, and each change is a commit.
What editors can do
FORMS
Form submissions without a backend
Paste an endpoint into your HTML. Submissions land in an inbox your team can read, filter and mark handled, and arrive by email on the schedule you choose.
CONTENT
An editor for posts and pages that leaves your front matter alone
Markdown with images and drafts. Keys Mabel does not recognise are written back untouched.
## Step 1: measure, don't guess A client's WordPress site was taking six to eight seconds to load a category page. The first step is a **number**, not an opinion.
DATA FILES
Turn a YAML file into a form your editors can fill in
Declare the fields once: text, images, lists, choices. Testimonials, team pages and settings become forms.
Your repo stays yours
Every save is a commit to your repository. Stop using Mabel and the files are still there, in the format Jekyll reads.
- a3f9c21 Add Joel testimonial
- 7c14e08 Update about.md
- 5be2d90 Publish: Debugging a slow site
- 19d03aa Contact form: change notification emails
Pricing
Priced per site. Start free, upgrade when a site goes live.
Each site has its own plan. Keep sites in build on Free, put live ones on Pro, and busy ones on Power.
-
Free
$0
For sites in build. Upgrade when it goes live.
- Up to 2 free sites
- Private or public repos
- Posts, pages and data files
- 3 editors per site
- 50 form submissions a month
- Submissions kept for 30 days
-
Pro
RECOMMENDED$5 per site, per month
For live sites.
- 5 editors per site
- 1,000 form submissions a month
- Submissions kept for 12 months
- Form file uploads (10 MB per file, 1 GB per site)
- Webhooks and email digests
-
Power
$15 per site, per month
For larger teams, high-traffic sites and busy forms.
- Everything in Pro
- 25 editors per site
- 25,000 form submissions a month
- Submissions kept for 3 years
- Form file uploads (25 MB per file, 20 GB per site)
Host free on Netlify, Cloudflare Pages or GitHub Pages. Mabel is the only bill.