Weave Code
Content Bundle Laravel Package
sylius/content-bundle
Sylius ContentBundle adds CMS-style content management to Sylius e-commerce applications. It provides entities and admin tools for creating and managing static pages, reusable content blocks, and rich text, helping storefronts publish informational content without custom development.
[READ-ONLY] Sylius CMS specific features and integration with Symfony CMF.
Frequently asked questions about Content Bundle
- Can I install sylius/content-bundle in a Laravel application?
- No. It is a Sylius/Symfony bundle built on Symfony bundle registration, DI container config, the Sylius ResourceBundle layer and Doctrine ORM mappings, so a composer require in a Laravel app would pull a Symfony/Sylius dependency tree and fail at container compilation long before any content renders. There is no adapter layer, and writing one would strip out the Sylius and CMF wiring that gives the package its value. Treat the stack mismatch as a hard rejection condition rather than a risk to work around.
- What does Sylius ContentBundle actually do?
- It adds CMS-style content management to Sylius e-commerce applications: static pages, reusable content blocks, rich text, and admin tools for creating and managing them. It also integrates with Symfony CMF dynamic routing so content objects are referenced by route records and resolved at request time. In practice it lets a Sylius storefront publish informational content without custom development.
- Is sylius/content-bundle still maintained?
- No. The repository is archived and read-only, so there are no upstream fixes, no PHP version bumps and no security response. It targets an older Sylius/Symfony generation, and its constraints will not resolve against current Symfony. Any defect you hit becomes a permanent internal liability.
- Why can't Symfony CMF dynamic routing be used in Laravel?
- CMF resolves content by looking up a route record and then loading the referenced content object through Symfony's routing and DI layers. Laravel has no equivalent route registry, and its route model binding expects Eloquent models resolved from route parameters. You can reproduce the behaviour with a catch-all fallback route plus a slug resolver service backed by a content_routes table, but that is a reimplementation, not an integration.
- How would I rebuild Sylius ContentBundle's content model in Laravel?
- Model pages and blocks as Eloquent models, with a contents table plus a content_routes table holding slug, locale, content_type and content_id so a catch-all route can resolve a URL to content. Admin CRUD maps onto a resource controller with Filament or Nova, and blocks map onto polymorphic block types rendered by Blade components. Cache the slug resolver, because every storefront request will hit it.
- What Laravel CMS alternatives cover the same use cases?
- Mature Laravel options such as Statamic, Filament-based admin panels and headless CMS setups cover static pages, reusable blocks, menus and localization with active maintenance. Which one fits depends on scope: versioning, drafts, scheduled publishing and slug history with redirects are the features that usually push teams toward a custom build. If content must be a first-class entity that products or promotions reference, a custom polymorphic model is usually the better answer.
- What are the risks of depending on an archived Composer package?
- There are no security patches, no PHP or framework version bumps, and no issue history to mine when something breaks. Risk compounds down the dependency tree: the Symfony CMF routing packages this bundle relies on are themselves in legacy or maintenance status, which is hard to inventory. With 7 stars and 0 dependents there is also no production usage signal and no community to consult.
- Does sylius/content-bundle work with the current Symfony version?
- Unlikely. The technical evaluation notes that the package targets an older Sylius/Symfony generation and that its constraints will not resolve against current Symfony, let alone a modern Laravel runtime. Because the repository is archived, nobody is going to widen those constraints. Check the composer.json requirements against your target versions before spending any time on it.
- How do I handle slugs, redirects and sitemaps if I rebuild this in Laravel?
- A content_routes table with slug, locale, content_type and content_id gives you resolution; add a status column so retired slugs return 301s instead of 404s. Generate sitemaps from the same table so the SEO contract, including canonical slugs, slug history and structured data, lives in one place. Cache resolved routes and invalidate them when content is published.
- Can I copy code from sylius/content-bundle into my Laravel app?
- The recommendation is to borrow the patterns rather than the code, and to confirm the license before transplanting any implementation. The ideas worth taking are the polymorphic content model, the route registry that decouples URLs from content, and the decoupled admin CRUD layer. None of the Symfony-specific wiring will survive the port anyway.
Weaver
How can I help you explore Laravel packages today?