Getting started
Kirby CMS
Working with Fountain is essentially working with Kirby CMS.
You’ll encounter typical Kirby concepts such as controllers, blueprints, and routes. Fountain was built from the ground up since Kirby 3, so it follows the same conventions.
In the box
After installing Fountain you’ll have access to a bunch of blueprints and templates, with controllers and routes in place help you build your website.
| Type | Info | Location |
|---|---|---|
| Blueprints | Pre‑configured page structures | /site/plugins/fountain/blueprint/pages |
| Templates | PHP files that render your pages | /site/plugins/fountain/templates |
| Controllers | Backend logic for specific pages | /site/plugins/fountain/controllers |
| Routes | URL patterns that map to controllers | /site/plugins/fountain/routes |
Customising templates and blueprints
-
Copy the files. Copy from Fountain folder and put e.g. in
/site/blueprints/pages/. These files will override Fountains and you can customize how you prefer. -
Keep the core fields Removing or renaming essential fields can break Fountain’s functionality. Stick to the original structure unless you’re sure of the impact
-
Add new tabs in the blueprint for custom content Creating your own tab with you content is a good way to customize.
Installation
- Kirby CMS Any web host that supports PHP.
- Python Fountain relies on a Python backend for certain tasks.
- Docker A Dockerfile is included so you can spin up a container with tools like DDev or OrbStack.
Hosting
As Fountain has specific requirements, you need a hosting provider allowing installation or to run a VPS. Fountain will also provide hosting on request, please reach out if so. There’s a few guides to help you e.g. use …