This is an experimental setup. It tries to configure 11ty in a way that it can read directly from Kirby's content folder.
In contrast to the Eleventy Kit, this would not need any form of headless approach. 11ty can just grab the same data that Kirby stores. It truly gives you the best of both systems.
Such a setup could be running on cheap shared hosting, with the single purpose to give personal access to Kirby’s panel. Then you can edit content for your 11ty site on the go and profit from Kirby’s panel features.
Content changes could then be automatically commited in your git repo and pushed to Github for example. This would then trigger a deployment of your 11ty site – through Netlify or any other similar provider.
- Clone this repo
- Run
npx @11ty/eleventy --serveto start 11ty - Run
php -S localhost:8181 kirby/router.phpto start Kirby - Visit
http://localhost:8181/panelto access your panel
This is still an experiment. It seems to be very promising but has a couple remaining things to fix.
- Configure 11ty to read from Kirby’s content folder (.eleventy.js)
- New frontmatter plugin for Kirby
- Fix watcher issues after a page is being deleted
- Remove Kirby’s sorting numbers form 11ty permalinks
- Setup basic blog
- Fix links to assets in Kirby’s textareas
- Proper support for drafts (see https://github.com/11ty/eleventy-base-blog/blob/main/eleventy.config.drafts.js)
- Better ways to copy images and other assets, but still keep them colocated in Kirby’s page folders
- Add git auto commits and pushes when content changes