CMS / DXP Featured
Ibexa
A content repository, not a table per page type: Content, Locations, languages, siteaccess.
Ibexa’s particularity is the repository: a Content item has fields and translations; Locations place it in a tree. URL aliases, languages and siteaccesses are first-class. That is closer to a DXP than to “one Doctrine entity per page”.
Strengths: editorial workflows, an Admin UI, Twig content views, REST and GraphQL on the same model. Multilingual is not an afterthought.
Limits: Content Types are not your business schema. Orders, stock, billing stay in Symfony/Doctrine. Mixing the two without a boundary is how projects rot.
