- How do I install litecms/page in a Laravel application?
- Install it with composer require litecms/page; the service provider is auto-discovered. Then publish the config, migrations, and Blade views, and run php artisan migrate to create the pages table. Because Page is a first-party LiteCMS module, confirm the core requirements and supported framework versions before you wire it into an existing app.
- Does litecms/page work without the LiteCMS core package?
- The package metadata does not state whether the Page model and routing can be used standalone, so treat this as an open question to answer in a spike. LiteCMS Page is a first-party content module for LiteCMS, and if it hard-depends on litecms/core then adopting the page module means adopting the whole CMS layer. Settle that before you socialize any estimate, because it decides whether this is a two-day spike or a roadmap item.
- How does slug-based page routing work in LiteCMS Page?
- Each page is an Eloquent model with a slug, title, and body, and the package registers routes that resolve a requested slug to the matching page. A configurable route prefix keeps page URLs under a path you control. Because slugs are user-authored, plan for collision handling and for content being reachable by any wildcard match.
- Which Laravel and PHP versions does litecms/page support?
- No support matrix, release cadence, or stated support policy is published in the package metadata. That is a spike item: pin a LiteCMS core, Laravel, and PHP combination and prove it in CI before promising a support window. Assume you will absorb the next Laravel major bump yourself.
- Can I change the pages table name and the route prefix?
- Yes, the package is described as configurable for both table names and the route prefix. Publish the config file, adjust the values, and keep the published migrations in sync with any renamed table. Verify the migrations are idempotent and non-destructive on re-run and apply cleanly on your database, including Postgres.
- Is there a built-in admin interface for managing pages, and how is access controlled?
- LiteCMS Page ships a ready-made admin interface built from Blade views, routes, and menu entries, which you mount behind your existing authentication. What is not documented is how authorization is enforced: it may rely on LiteCMS ACL, Laravel Gate or policies, or nothing at all. Confirm that before exposing page CRUD to real users.
- How do I render a page in a Blade template?
- Pages are rendered through a publishable Blade view, so you can output the page body inside a standard template and use normal Laravel layout conventions. Publish the view and adapt the markup to your design system. Treat the stored body as untrusted HTML and sanitize or escape it before output.
- Is litecms/page safe to use in a production application?
- Budget for review rather than assuming it is handled. A page module typically exposes an unauthenticated public route alongside a privileged admin CRUD, stores WYSIWYG HTML, and resolves content by wildcard slug, so stored XSS, slug collision, and unintended exposure are all realistic risks. There is no evidence of an independent security review, so plan to audit routing, authorization, and output escaping yourself.
- Does it support revisions, drafts, i18n, hierarchical pages, or multi-site content?
- Treat the documented content model as flat, slug-addressed pages with a title, slug, and body; revisions, scheduled publishing, i18n, hierarchical pages, and custom fields are not described. Multi-site and tenancy scope is also unstated, and page modules commonly assume a single site. If your requirements include any of these, plan to extend the schema and routing yourself.
- Is litecms/page actively maintained and tested, and how does it compare with building pages myself?
- The package has zero stars and zero dependents with a single maintainer, which means no community bug-finding, no third-party patches, and a bus factor of one. There is no evidence of a published test suite or CI you can run against your pinned framework version, so write your own smoke tests. The realistic alternatives are adopting LiteCMS wholesale, or using this package as a reference implementation and building page CRUD natively in roughly one to three weeks.