Neos

Neos is a PHP CMS that grew out of the TYPO3 project — originally released as TYPO3 Neos before becoming an independent project in 2015. It is built on the Flow PHP framework and takes a fundamentally different approach to content management than most CMSes: rather than storing content as pages with blocks, everything in Neos is a node in a content repository tree.

This node-based model is what makes Neos flexible for complex editorial requirements. A content node — an article, a product description, a media item — is stored independently of any specific page or template. The same node can be referenced and rendered differently across multiple pages and contexts. For multi-channel publishing or sites where content reuse matters, this is a meaningful architectural advantage over traditional page-based CMSes.

In-context editing is the primary interface for editors. Click on a content element in the browser and an editing panel opens in-place. New nodes are dragged onto the page from a content panel. For editorial teams who need to see the result of their changes as they work, this removes the back-and-forth between a backend editor and a frontend preview.

The rendering system uses Fusion, a Neos-specific language for mapping content nodes to their presentation. Fusion is powerful and handles complex rendering logic cleanly, but it has no counterpart in other systems — there is no transferable experience from Twig, Blade, or other PHP template languages.

The honest limitation is accessibility. Neos has a mature architecture and a stable product, but its community is predominantly German-speaking and European. With 265 GitHub stars and thin English documentation outside the official docs, teams outside that ecosystem will find the learning curve steeper than the alternatives.