Jekyll Admin is a plugin from the Jekyll project itself. You add one line to your Gemfile, run the site locally, and an editing interface appears at /admin. It lets you create and edit posts, pages, collections, data files, static files and the site configuration without opening a text editor.
It is MIT licensed and lives at jekyll/jekyll-admin on GitHub. The last release, v0.12.0, shipped in February 2025, and the last commit we found, in June 2025, only bumped a CI action. The repository is not archived, but it is in maintenance mode at best. Compare it with the others in our Git-based CMS roundup.
How does Jekyll Admin work?
It is a Jekyll plugin with a small Ruby HTTP API and a JavaScript front end. It runs inside bundle exec jekyll serve, reads the files in your working folder, and writes changes straight back to them. There is no Git integration of its own. Commits, branches and deploys stay in your normal workflow.
Is it a CMS for editors or a tool for developers?
Mostly a tool for developers. The README gives no authentication guidance, because the plugin is meant for your own machine. An editor needs Ruby, Bundler and a clone of the repository, and has to commit and push by hand. Exposing the admin on a public server without a login in front of it would let anyone write to your content.
That makes it a fit for a single author who already runs Jekyll locally, or for a developer who wants a form view of data files. It does not suit a marketing team.
Where are the limits?
- No roles or accounts. There are no users, no approval step and no audit trail beyond Git.
- No hosted mode. Nothing publishes for you, and drafts are only what is on your disk.
- Thin media handling. Static files appear as a section, but we found no media library, resizing or CDN.
- Thin maintenance: Fixes and Jekyll compatibility updates are not guaranteed.
When would we use something else?
For a Jekyll site with real editors, we would put Decap or Sveltia CMS in front of the repository, since both run as a static admin page and sign editors in through GitHub or GitLab. Pages CMS is the quickest hosted option on GitHub. CloudCannon fits teams that want accounts and visual editing. Past a few hundred entries, or with relational content, choose a full headless CMS.
What can we do for a Jekyll Admin team?
- Review whether the site should stay on Jekyll at all, or move to Hugo or Astro. See our Jekyll development and Hugo development services.
- Add a Git-based editor with a proper login, and write the config for your collections.
- Move the content to a fuller CMS, mapping frontmatter fields to a schema and keeping redirects intact.
- Hire a Jekyll developer for upgrades and theme work.
