- What is liberusoftware/module-cms-pages used for?
- liberusoftware/module-cms-pages is a Laravel module for creating and managing editable CMS pages. It provides admin CRUD, slugs, publishing controls, and Blade rendering so your application can serve routable static content. It is the provider-neutral Pages implementation that owns the domain behavior and data, while optional surface packages translate its public contracts.
- How do I install the Laravel CMS pages module?
- Install it with Composer using the package name liberusoftware/module-cms-pages, then register the module as required by your Laravel or Liberu CMS setup. Because the package owns Pages domain data, review and run its migrations in your application. Confirm the install steps against the package README and your framework version.
- Which Laravel versions are supported and is the package maintained?
- The overview provided here does not list supported Laravel versions, so check the package composer.json constraints before installing. Also verify PHP version requirements and compatibility with your Liberu CMS version. Maintenance status should be checked on Packagist and the repository because the repository is not specified in this context.
- How do I configure admin CRUD for CMS pages?
- Admin CRUD is part of the module's core Pages management, letting you create, edit, and manage CMS page records. The exact configuration and admin surface depend on how you integrate the module within Liberu CMS or your Laravel application. Use the public contracts rather than coupling custom code to internal implementation details.
- How are slugs and routable page URLs handled?
- Pages include slugs so they can be routable static content in your application. Slug values are managed through the module's Pages domain behavior and admin CRUD. The overview does not define slug uniqueness, redirect, or URL-prefix rules, so review the public contracts and configuration before customizing routing.
- How do publishing controls work for CMS pages?
- Publishing controls let you manage whether a CMS page is available or withheld from public routing. The module owns this domain behavior as part of its Pages implementation. Exact status names and defaults are not specified in the overview, so check the package contracts and migrations for the available fields.
- Can I render CMS pages with Blade templates?
- Yes, Blade rendering is included among the module's core capabilities for CMS pages. It integrates with Liberu CMS to add routable static content that can be rendered in Laravel Blade views. If you need other surfaces, the optional API, Filament, Livewire, React, Vue, or Nuxt packages can translate the public contracts.
- Do I need Filament, Livewire, React, Vue, or Nuxt to use this package?
- No, you do not need those packages to use the core Pages implementation. liberusoftware/module-cms-pages is provider-neutral and owns the domain behavior and data. The API, Filament, Livewire, React, Vue, and Nuxt packages are optional translators for their respective surfaces.
- How should I test and deploy CMS pages in a Laravel application?
- Test CMS pages through your Laravel application's test suite by exercising the module's public contracts for page creation, slugs, publishing, and rendering. Avoid testing private implementation details so optional surface packages remain swappable. For production, review migrations, version constraints, and how publishing controls expose routable content.
- What are alternatives to this Laravel CMS pages package?
- Alternatives include general Laravel CMS packages or building custom page models, controllers, and admin screens for static content. This package is specifically the provider-neutral Pages implementation for Liberu CMS with admin CRUD, slugs, publishing controls, and Blade rendering. Choose it when you want those Pages capabilities as reusable domain contracts rather than a one-off CMS feature.