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 has been 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/blueprints |
| Templates | PHP files that render your pages | /site/plugins/fountain/templates |
| Controllers | Backend logic for specific pages | /site/plugins/fountain/controllers |
| Models | Page models | /site/plugins/fountain/models |
| Routes | URL patterns that map to controllers | /site/plugins/fountain/routes |
Customising templates and blueprints
- Copy the files.
- Keep the core fields
- Add new tabs in the blueprint for custom content
Copy from Fountain folder and put e.g. in /site/blueprints/pages/. These files will override Fountains and you can customize how you prefer. Removing or renaming essential fields can break Fountain’s functionality. Stick to the original structure unless you’re sure of the impact. Creating your own tab with you content is a good way to customize.
Hosting
As Fountain has specific requirements, you need a hosting provider that allows you to install custom software. There are a few, e.g. Uberspace.
You can also run your own Virtual Private Server from e.g. Hetzner. With Docker support in Fountain you can easily host your Fountain-installation on e.g. Railway.
Nymark Type can also provide hosting on request or help out with hosting, please reach out if so.