Weave Code
Website Bundle Laravel Package
integrated/website-bundle
Integrated Website Bundle packages the core pieces of a public-facing site—page routing, content management, and reusable front-end components—into one installable PHP dependency, so teams can launch and maintain a website without stitching together separate libraries.
Provides a website front-end for content in Integrated
Frequently asked questions about Website Bundle
- Is integrated/website-bundle a Laravel package?
- No. Despite being catalogued as a Laravel/PHP dependency, integrated/website-bundle is a Symfony bundle that provides routing, controllers, and Twig templates for content managed in the Integrated CMS. A Laravel team cannot simply composer require it and get native Laravel integration. Treat it as a separate deployable website surface and evaluate whether your team can own a Symfony runtime.
- What does Integrated Website Bundle actually include?
- It bundles page and content management with flexible templates, menu and navigation builders, and global website settings for branding and SEO. It also includes service-provider style integration plus publishable views and migrations. Architecturally, it is the public-facing rendering layer for the Integrated CMS rather than a general-purpose library.
- Can I install Integrated Website Bundle in an existing Laravel application?
- Not as a standard dependency. In a Laravel-first organisation the realistic patterns are a satellite Symfony site reverse-proxied from the main app, or a headless bypass that consumes Integrated's content API directly. Only native Symfony adoption realises the bundle's stated lift; the other patterns turn it into a reference implementation.
- Which Symfony, PHP, and Twig versions are supported?
- The reviewed metadata does not document supported PHP, Symfony major, or Twig versions, and there is no published support or EOL matrix. Those constraints are hard blockers that can only be confirmed at spike time. Verify them before committing to a procurement or architecture decision.
- How do I install and configure the bundle?
- The README excerpt provided is empty, so installation steps are not confirmed in the reviewed material. Expect the usual Symfony bundle flow: Composer require, bundle registration, configuration, and publishing assets or migrations. Confirm the exact commands and required environment against the repository before scoping work.
- Does the bundle require a hosted Integrated CMS or can it be self-hosted?
- It is not documented whether the bundle requires a hosted Integrated instance, a self-hosted backend, or supports either. The content delivery mechanism, whether API, database, or in-process service container, is also unclear. Confirm backend cost and degradation behaviour during an outage before relying on it.
- How customizable are the templates, routes, and front-end assets?
- Templates, route conventions, and SEO logic are encoded in the rendering layer, so once your design lives inside bundle templates, customisation can become fork maintenance. The documented override mechanism for templates, routes, and assets is not verified in the reviewed metadata. Ask what is overridable versus opinionated before adopting.
- What are the alternatives if we are a Laravel-first team?
- For Laravel-first teams the main alternative is to skip the bundle and consume Integrated's content API headlessly from Laravel or a JavaScript front end. That loses the prebuilt templates but eliminates a second runtime and deploy pipeline. Laravel-native CMS packages are another option if you do not need Integrated specifically.
- Is Integrated Website Bundle production-ready and well maintained?
- Evidence of production readiness is essentially absent: zero stars, zero dependents, and no public issues to mine for failure modes. It is published by the organisation that sells Integrated, so compatibility is bound to a commercial relationship rather than a community contract. Release cadence, semver discipline, and security disclosure process are undocumented, so treat it as investigate, never adopt.
- Does it support multilingual sites, previews, drafts, and editorial workflows?
- Coverage for multilingual content, multi-site setups, preview and draft states, and editorial workflows is not documented in the reviewed metadata. It is unclear whether these are bundled or must be built by your team. The upgrade path across Symfony majors is also undocumented, so confirm ownership before planning a long-lived site.
Weaver
How can I help you explore Laravel packages today?