Weave Code
Page Bundle Laravel Package
integrated/page-bundle
integrated/page-bundle is a Laravel package for adding structured page management to your application. It offers a foundation for editable, route-aware pages that integrate with existing Laravel projects, with minimal setup and room to extend the content model to fit your needs.
Provides the possibility for the user to create pages on Integrated websites, and front-end editing when combined with the website-bundle
Frequently asked questions about Page Bundle
- Is integrated/page-bundle a Laravel package or a Symfony bundle?
- Despite the Laravel and PHP framing around it, integrated/page-bundle is a Symfony bundle. It ships Symfony conventions: a DependencyInjection extension with a configuration tree, tagged service definitions, and bundle-registered routing and templates. There is no service provider, no facade, no config-publish path, and no Illuminate contracts. Laravel has no loader for any of that, so stack fit on a Laravel-first project is low.
- Can I install integrated/page-bundle in a Laravel application?
- Composer may install the code, but nothing in Laravel will boot it, so a direct install gets you nowhere. Do not try to shim it in: the impedance mismatch across container, config, routing, and templating will cost more than the realistic alternatives. The three viable postures are a headless Symfony sidecar that exposes published content to Laravel, full Symfony adoption for the content surface only, or reimplementing the page entity plus inline editing natively in Laravel, which is often cheapest for a small page model.
- Does integrated/page-bundle include front-end inline editing out of the box?
- Page creation comes from page-bundle, but in-context front-end editing only works when it is combined with website-bundle. That makes the advertised value a two-package dependency, and the second package carries the same maturity risk. A spike on page-bundle alone will tell you almost nothing about the actual editor experience, so evaluate the pair together.
- Which PHP and Symfony versions does integrated/page-bundle support?
- The overview does not document a version matrix, and no external consumers are visible to confirm it. Ask the maintainer for the exact PHP and Symfony version ranges and whether releases follow SemVer. Treat coupling to a specific Symfony major version as a real upgrade risk until you have that answer in writing.
- What persistence layer does integrated/page-bundle use, and does it own its database tables?
- Expect Doctrine ORM assumptions, since that is the Symfony default and the maintainer has published nothing to the contrary. Ask whether the bundle owns its schema, how migrations are shipped, and whether it can coexist with an existing content schema in your application. If it cannot share a database cleanly, the sidecar posture becomes the only low-friction option.
- Does integrated/page-bundle support drafts, scheduled publishing, and versioning?
- Editorial workflow is not documented in the overview, so nothing here confirms draft or publish states, scheduled publishing, revision history, or preview tokens. These are standard requirements for marketing and landing pages, and retrofitting them is not trivial. Put them to the maintainer as explicit yes-or-no questions before you commit to a roadmap.
- How is authorization enforced for page editing in integrated/page-bundle?
- The authorization model is not documented, so you need to know who may edit pages and, more importantly, how that is enforced server-side rather than merely hidden in the UI. Inline front-end editing also raises CSRF, sanitization of edited HTML, and whether the edit surface can be separated from the public render path. Get answers on all three before exposing the editor to anyone.
- Is integrated/page-bundle production-ready given it has zero stars and zero dependents?
- Zero stars and zero dependents means no external consumers validating the public API, no third-party issue reports, and no signal on upgrade discipline or release cadence. A high score with no adoption is more likely abandonment or private-use-only than an undiscovered gem. The MIT license is clean for commercial use, but there is no warranty and no support obligation, so read the source and check CI status and last commit date.
- Does integrated/page-bundle handle SEO slugs, redirects, sitemaps, and localization?
- Slugs, meta titles, and meta descriptions are advertised out of the box. Redirect handling, sitemap generation, and i18n or localization are not mentioned and must be verified against the source. If SEO is a core requirement, confirm each item individually rather than assuming the SEO-ready claim covers them.
- Is there a JSON or GraphQL read API in integrated/page-bundle, or is rendering Twig-only?
- The package does not document a read API, and rendering is most likely server-side Twig only. That matters if you plan a headless sidecar, because Laravel would need either an API or a shared read model to consume published pages. Ask the maintainer directly, and if no API exists, plan for a documented JSON or CSV export of pages, revisions, and media references so an exit does not mean content loss.
Weaver
How can I help you explore Laravel packages today?