Weave Code
Module Cms Core Laravel Package
liberusoftware/module-cms-core
Core CMS module for Liberu's modular Laravel platform, providing foundational content models, routing, and admin integration for building and extending sites through pluggable modules. It offers a stable base for pages, content types, and backend workflows.
The Liberu CMS kernel: module registry, lifecycle manager, event bus, base module classes, and the module generator.
Frequently asked questions about Module Cms Core
- What is liberusoftware/module-cms-core and what does it provide?
- liberusoftware/module-cms-core is the kernel for Liberu's modular Laravel CMS. It provides the module registry, lifecycle manager, event bus, base module classes, and module generator that other CMS modules build on. Use it when you need a stable foundation for pages, content types, routing, and admin workflows in a pluggable Laravel application.
- How do I install the Liberu CMS Core module in a Laravel application?
- Install it with Composer using composer require liberusoftware/module-cms-core in your Laravel project. Then register the package service provider as required by your Laravel version and publish any configuration or assets the package exposes. Because this is a CMS core package, it is usually installed as part of a Liberu modular platform rather than as a standalone content system.
- How do I configure the module registry and lifecycle manager?
- Configuration usually involves publishing the CMS core config and defining which modules are enabled in the registry. The lifecycle manager then handles install, enable, disable, and related module state transitions according to your application setup. Check the package README for exact config keys and environment-specific options before changing defaults.
- Which Laravel versions are supported by liberusoftware/module-cms-core?
- The package is designed for Laravel applications, but the supported Laravel versions should be confirmed in the package composer.json and README. Match the package constraint to your application Laravel and PHP versions before installing. If you are upgrading Laravel, test the CMS kernel and custom modules in a staging branch first.
- How do I generate a new module with the built-in module generator?
- Use the built-in module generator to scaffold a new CMS module with the expected directory structure and base classes. The generator is part of the kernel, so generated modules can register with the module registry and participate in lifecycle and event handling. Review the generated files and adjust namespaces, routes, and admin integration for your site.
- What are the base module classes and when should I extend them?
- Base module classes give your custom modules a consistent contract for registration, bootstrapping, and lifecycle behavior. Extend them when you are building a pluggable CMS module that needs to integrate with routing, content models, or admin workflows. Keeping to the base classes helps the module registry and event bus treat your module consistently.
- How does the event bus work for CMS module events?
- The event bus lets CMS modules publish and subscribe to application events without tight coupling. You can use it to react to module lifecycle changes, content workflow steps, or other extension points exposed by the kernel. Register listeners through Laravel's event system or the package documented hooks, and test event ordering in your modules.
- Does this package include page models, content types, routing, and admin integration?
- The package is described as providing foundational content models, routing, and admin integration for Liberu's modular Laravel platform. It gives you a stable base for pages, content types, and backend workflows rather than a complete turnkey site. You will still build or install modules that define the actual content structures and admin screens.
- How can I test custom modules built on Liberu CMS Core?
- Test custom modules with Laravel's testing tools, focusing on module registration, lifecycle transitions, routes, and event bus listeners. Use a test database and a fresh application boot to catch service provider or config issues. If the package ships testing helpers, use them, but also cover your module's admin and content model behavior.
- Is this package suitable for production, and what should I know about maintenance or alternatives?
- Treat it as production-oriented infrastructure for a modular Laravel CMS, but review the package release history, issue tracker, and compatibility with your Laravel version before relying on it. For alternatives, compare other modular Laravel CMS packages or building a custom module system, weighing lock-in and admin features. Maintenance should include Composer updates, regression tests for modules, and monitoring of lifecycle and event behavior after upgrades.
Weaver
How can I help you explore Laravel packages today?