- Is sulu/article-bundle a Laravel package?
- No. sulu/article-bundle is a Symfony bundle built specifically for Sulu CMS, not a Laravel package. It has no Laravel service provider, no Illuminate integration, and no Composer autodiscovery path for Laravel. In a Laravel codebase, the viable approach is to run Sulu as a separate content service and consume it over an API boundary.
- How do I install sulu/article-bundle?
- Install it with Composer inside a Sulu application, then register the bundle in the Sulu kernel bundle list. Configure article types and templates, initialize the schema and content repository, and build and deploy the Sulu admin assets. You also need to configure permissions and verify your PHP, Symfony, Doctrine, and PHPCR versions match the bundle requirements.
- Does sulu/article-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets Sulu CMS starting from version 2.0 and is structurally coupled to Sulu's bundle registration, admin UI, ContentMapper, route providers, security, and persistence layer. Laravel versions are not supported for embedding this package. Use a decoupled Sulu content service if you need Sulu articles alongside Laravel.
- Which Sulu versions are compatible with SuluArticleBundle?
- The README badge states Sulu compatibility of >=2.0. You should check the require section in composer.json for the exact supported Sulu, PHP, Symfony, and persistence constraints. The bundle tracks the Sulu core line, so align every Sulu bundle and your Symfony version to avoid blocking security patches.
- Can I use SuluArticleBundle in a Laravel app via Composer?
- Installing it into a Laravel app will not give you working article management. The bundle depends on Sulu bundle registration, the React admin UI, ContentMapper and structure metadata, route providers, permissions, and Sulu's persistence layer. The only practical pattern is deploying Sulu separately and integrating Laravel through HTTP or queues.
- How do I configure article types in SuluArticleBundle?
- Define article types and templates with fields, localization rules, route and URL patterns, author defaults, SEO defaults, and any taxonomies your editors need. The bundle supports managing different article types through separated lists in the Sulu administration interface. The main effort is content modeling and editorial workflow design with the content owners, not the initial wiring.
- Is SuluArticleBundle performance optimized for article storage?
- Yes. The bundle exists to provide a performance-optimized way to manage localized, content-rich articles in Sulu, separate from page content. Articles can be stored and indexed through Sulu's persistence and optional search infrastructure. If search indexing is in scope, plan who owns index health and synchronization.
- How do I test a SuluArticleBundle integration?
- Test inside a Sulu application rather than a Laravel test suite. Validate bundle registration, article type and template configuration, schema initialization, admin asset build, permissions, localization behavior, routing, and rendering. For a Laravel integration, test the API or queue boundary to Sulu instead of testing the bundle directly.
- What are the production concerns with SuluArticleBundle?
- The Sulu admin asset pipeline must build and deploy correctly, because a broken build blocks editors, not just developers. Article storage and schema evolution across Sulu majors are the main upgrade hazard, so data migrations need planning beyond a Composer update. Version coupling is also high, and a stale pin can block Symfony security patches.
- What are alternatives to SuluArticleBundle for a Laravel application?
- If your application is Laravel-first, evaluate a Laravel-native content model or a headless CMS rather than embedding this Symfony bundle. If Sulu is already your CMS, keep SuluArticleBundle inside Sulu and integrate Laravel over an API or queue. Avoid forcing a Symfony kernel into the Laravel runtime just to use article management.