Weave Code
Cms Bundle Laravel Package
orbitale/cms-bundle
Orbitale CMS Bundle is a lightweight, extensible content management bundle for Symfony. It provides pages, menus, and reusable content blocks with admin tooling, Twig integration, SEO-friendly URLs, and a flexible structure for building and managing multilingual websites.
A simple lightweight CMS bundle for Symfony
Frequently asked questions about Cms Bundle
- Does Orbitale CMS Bundle work with Laravel?
- No. orbitale/cms-bundle is a Symfony bundle built around Symfony's HttpKernel, dependency injection container, event dispatcher, routing and annotations, Twig, and typically Doctrine ORM, and none of those map onto Laravel's service container, Eloquent, Blade, or routing pipeline. There is no Laravel service provider, facade, or published Laravel integration. Even with a compatibility shim, you would effectively be running a second framework alongside Laravel.
- Can I install orbitale/cms-bundle with Composer in a Laravel project?
- Composer will let you add the package, but that does not make it usable. The bundle registers Symfony compiler passes, services, and routes that Laravel never boots, so nothing renders and the admin tooling will not appear. You would also hit version constraints against the Symfony components Laravel already requires. Treat a successful composer require as a false positive, not a working install.
- Which Symfony versions does orbitale/cms-bundle support?
- Version 4.1.0 targets Symfony 6.0 and raises the minimum from Symfony 5.0 to 5.3 as a declared backward-compatibility break. That ceiling is already behind Laravel 11 and 12, which track Symfony 7 components, so Composer conflicts are likely on current Laravel releases. The 4.1.0 release also added a CI matrix across PHP and Symfony versions, which is a positive signal but a single data point.
- What are Laravel-native alternatives to Orbitale CMS Bundle?
- The realistic comparison set is Statamic, which is commercial and Laravel-native, Filament with custom content models, October CMS, or a headless CMS such as Directus, Strapi, or Contentful consumed over an API. Each option either keeps you inside the Laravel runtime or stays cleanly outside it, with no second framework to operate. Choosing among them depends on whether you need authoring UX, workflows, localization, or just structured content delivery.
- How would I use Orbitale CMS content inside a Laravel application?
- You cannot reuse the bundle's code, but you can reuse its ideas. Port the small page and block data model into Eloquent migrations and expose it through Blade or Filament, or run a Symfony sidecar that exposes a content API and cache its responses in Laravel. The sidecar path adds a second runtime and deployment pipeline, so it is only worth it if the content model is genuinely a fit.
- Is orbitale/cms-bundle actively maintained?
- It is best described as intermittently maintained. Version 4.1.0 arrived after a multi-year gap, alongside an explicit CI matrix and a stated compatibility target, but the project has roughly 63 stars, no visible dependents, a single maintainer, and no published security response process. One release is a data point, not a cadence, and there is no published support or end-of-life policy for Symfony majors.
- What features does Orbitale CMS Bundle provide?
- It offers tree-organized pages with nested routing, reusable content blocks and widgets, Doctrine ORM persistence for pages and menus, front-end inline editing for content managers, Twig integration, SEO-friendly URLs, and an extensible architecture for custom page types. Multilingual sites are supported through its page and menu structure. It is a flexible alternative to rigid template-driven CMS setups, but only within Symfony.
- What is the risk of adopting orbitale/cms-bundle as a dependency?
- The main risk is ownership: with one maintainer and near-zero downstream consumers, your team becomes the de facto maintainer of an unfamiliar Symfony codebase on day one. The 4.1.0 release also shipped a backward-compatibility break in a minor version, so you cannot plan against an implied semver policy. Add a security review, because the bundle handles admin-authenticated content and has no visible vulnerability disclosure process.
- How do I test or spike Orbitale CMS Bundle before committing to it?
- Run a capability spike in a throwaway Symfony sandbox rather than a Laravel app, confirming that the content model matches your actual requirements for pages, blocks, versioning, workflows, and localization. If it fits, capture the schema and admin UX as requirements rather than code, then implement on Eloquent with Blade or Filament. Only after that should you weigh the sidecar option.
- Why is orbitale/cms-bundle listed alongside Laravel packages if it isn't one?
- Composer packages are often indexed by purpose such as CMS, content, or admin rather than by framework, so a Symfony bundle can surface in a Laravel package search. Discovery in a list is not compatibility: check the package's requires block and its framework assumptions before evaluating features. In this case the framework-model gap, not the feature set, is the blocker for Laravel teams.
Weaver
How can I help you explore Laravel packages today?