Fork CMS

Last reviewed Sep 13, 2026 · 740 words

Fork CMS has been around since 2010, sits at 1,170 stars, and is a better editor experience than WordPress out of the box for the one thing it was built for: a small, mostly static business or organisation site maintained by people who are not developers. That is a narrower promise than WordPress makes, and the trade is a community a hundredth the size. If you are a developer who will build the site once and hand the keys to an editor, it is worth a look. If you expect to install plugins to solve problems, it is not.

Built for the person who edits, not the person who installs

The backend (at /private on a Fork site) is opinionated in a way WordPress never managed: pages, blog, FAQ, contact forms, locations, and a media library are core modules with consistent screens, not a marketplace of competing plugins with different interfaces. Editors get an inline editor, page templates the developer defined in advance, and a publish workflow that does not expose 40 settings tabs. The built-in SEO module gives every page a meta title, description, canonical URL, and index/follow toggles as standard fields rather than a plugin upsell. The analytics module shows your Google Analytics numbers inside the backend. Multilingual is native: each page exists per locale with locale-aware URLs, and it works without the bolt-on translation plugins that make multilingual WordPress a chore.

Developers get Symfony, Twig, and a short learning curve

Fork is built on Symfony components with Twig templates and a plain theme structure, so a PHP developer used to modern frameworks feels at home faster than in WordPress's global-function world. Themes are a directory of Twig templates plus page-template definitions; modules follow a Symfony-flavoured shape with front-end actions, widgets, and a backend counterpart. Requirements are boring: PHP, MySQL or MariaDB, Composer, Apache or Nginx, and 256 MB of RAM is genuinely enough for a marketing site. The Docker route works, but bare-metal LAMP is how most existing Fork sites run: composer install, point the web root at the right directory, run the web installer. One warning for developers: check which Symfony major the current release depends on before you build on it, because a CMS that lags the framework by a version or two is the norm here, and that lag constrains which third-party libraries you can pull in alongside it.

The module ecosystem is the honest limit

WordPress wins on plugin count by orders of magnitude and it is pointless to pretend otherwise. Fork's third-party modules number in the dozens and many have not been touched in years. E-commerce, a booking system, a members area, an integration with a specific CRM: you are writing it, or picking a different CMS. Development pace on the core has also slowed; releases arrive, but the days of a busy Belgian agency driving it forward are behind it. Before committing, look at the date of the last tagged release and the open issue count, and decide whether "stable and quiet" reads as calm or as abandoned to you. For a five-page site that changes twice a year, calm is fine.

Where it sits among the alternatives

For a developer-built content site with a non-technical editor, the closest competitors in the CMS category are Grav (flat files, no database, Twig, a livelier ecosystem) and Kirby (paid licence, superb editor experience, flat files). Fork's advantages over both are the relational database (real multi-editor workflows, real search), the multilingual model, and the MIT licence. Against WordPress it wins on editor calm and loses on everything measured in plugin count. If you want a headless or API-first setup, look elsewhere entirely; Fork is a classic server-rendered CMS.

What I'd do

If I were building a bilingual brochure site for a small organisation, handing it to an office manager, and expecting to touch it twice a year, I would consider Fork seriously: install on a 256 MB LAMP box, define three page templates, switch on the SEO module, and walk away. For anything that will grow features over time, I would pick WordPress and accept the plugin sprawl, or Grav if a database is unwelcome. Fork is a sharp tool for a small job; the mistake is buying it for a big one.