For Jekyll sites
One dashboard for every static site you build for clients
Keep the git repo. Give clients a place to edit content and read form submissions, without giving them the repo.
Connect a GitHub repo in a few minutes
Sites running on MabelStack
-
willbarker.dev Personal site and blog
-
voyija.com Travel planning app
-
mabelstack.com This page
You build it in git. Your client 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 clients can touch
Define forms and the structure of data files. Everything else stays as you wrote it.
-
03
Invite the client
They edit and read submissions. Each change is a commit.
What clients can do
FORMS
Form submissions without a backend
Paste an endpoint into your HTML. Submissions land in an inbox your client 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 client can fill in
Declare the fields once: text, images, lists, choices. Testimonials, team pages and settings become forms.
ALL YOUR SITES
Twenty clients, one login
See which sites have unread submissions or unpublished drafts, and invite each client to their own site only.
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 client 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 sites your clients rely on.
- 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 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.