JEKYLL CMS
The Jekyll CMS for every site
Maintain your Jekyll dev workflow. Provide content creators with powerful visual tools to complement your static site generation.
Ruby simplicity meets content flexibility.
CloudCannon syncs directly with your Jekyll repository. Content managers publish updates through our streamlined interface while you retain full control over your templates, includes, and site configuration.
Version-controlled content publishing
Content contributors work within isolated branches, test modifications in preview builds, then merge changes to deploy. Your local Jekyll development continues without any interference.
Visual site building. Jekyll elegance intact.
Craft Liquid templates and includes following Jekyll’s conventions. Content teams build comprehensive pages visually with live preview feedback.
Static excellence. Worldwide delivery.
Jekyll's reliable static generation combined with CloudCannon's optional hosting creates exceptionally fast websites globally. Pre-compiled pages, asset optimization, and intelligent caching deliver outstanding user experiences.
More creating. Less managing.
Direct your development energy toward building new features instead of handling content changes. Deploy fresh Jekyll websites rapidly with your existing template library and styling frameworks.
Real results from Jekyll experts
Digital marketing agency Vyral Marketing manage hundreds of client websites with CloudCannon's Git-based CMS — and with finely tuned Jekyll templates and intact dev workflows, they're able to rapidly deploy a new site in around 4 hours.
Three steps to visual editing with Jekyll
Build with Jekyll
Build your static Jekyll site locally with your preferred stack and structure.
Configure with CloudCannon
Configure collections, set editing rules, and transform your shortcodes and content blocks into visual components.
Hand off confidently
Hand off to non-technical editors who can update content visually — without touching your code.
No vendor lock-in. Period.
Your Jekyll code and content stays in Git.
Your repos stay yours.
Tiaan Fairchild
Software Engineer
