Weave Code
Cms Laravel Laravel Package
liberu-cms/cms-laravel
Liberu CMS for Laravel is a modular content management package for building editable websites and applications. It offers pages, posts, media, menus, SEO tooling, custom content types, and role-based admin features, with clean Laravel integration that helps teams ship CMS-driven sites faster.
CMS application written in Laravel 13 / PHP 8.5 using Filament 5 - WordPress or Drupal or OctoberCMS alternative.
Frequently asked questions about Cms Laravel
- What is Liberu CMS for Laravel, and how does it compare to WordPress, Drupal, or OctoberCMS?
- Liberu CMS is a modular content management package for Laravel applications, described as a WordPress, Drupal, or OctoberCMS alternative. It provides pages, posts, media, menus, SEO tooling, custom content types, role-based admin features, and Filament-based administration. It is aimed at teams that want CMS conventions inside a Laravel codebase rather than a separate platform. Unlike WordPress or Drupal, it is adopted as a Composer package and integrated into your Laravel application.
- How do I install and configure liberu-cms/cms-laravel?
- Install the package with Composer using liberu-cms/cms-laravel, then follow the repository README to publish configuration and migrations. Run migrations against a safe database copy and configure Filament admin access and permissions. Validate environment variables, media storage, and route registration before exposing the CMS publicly. Because CMS packages often publish config and assets, review what is published and commit only what your deployment process needs.
- Which Laravel, PHP, Filament, and Livewire versions does Liberu CMS support?
- The repository description targets Laravel 13, PHP 8.5, and Filament 5. Companion API and Livewire packages are mentioned, but you should confirm the exact supported Livewire and database versions in the package metadata or release notes. If your application runs older Laravel, PHP, or Filament versions, treat compatibility as unconfirmed until tested in a sandbox. Check dependency constraints in composer.json before upgrading.
- Is v32.0.0 a breaking change, and what is the upgrade path?
- v32.0.0 is a major version, so treat it as potentially breaking even if described as a feature release. Pin your current version, create a sandbox branch, install v32.0.0, run migrations against a copy of production data, and review changes to content models, routes, permissions, templates, and public APIs. Confirm upgrade notes and rollback procedures before migrating real content. Only promote to production after validating existing editorial workflows.
- What does the CMS Events Content module add?
- The CMS Events Content module adds event-domain content covering events, sessions, speakers, venues, calendars, registration references, archives, and structured data. This reduces the need to custom-build event content modeling in a Laravel CMS. The module appears intended for modular content architecture and can support event-focused sites or hybrid applications. Validate how these models relate to your existing content types before enabling it broadly.
- Can I extend event, session, speaker, and venue models without forking package code?
- The package structure is modular, but extensibility must be verified against the actual event, session, speaker, and venue models. Check whether you can add fields, override templates, adjust routes, and extend Filament resources through supported configuration or extension points. Avoid patching vendor code because it complicates upgrades. Test customizations in staging and document which package contracts you rely on.
- Can I use Liberu CMS as a headless CMS with an API?
- Liberu CMS appears to support a headless or hybrid approach through companion API, Filament, and Livewire packages. The API package can serve content to separate frontends, while Filament provides administration. Before committing, validate API versioning, authentication, filtering, pagination, and response contracts with representative consumers. Confirm the API package version matches your core CMS version.
- Does Liberu CMS handle event registration, ticketing, or payment workflows?
- The Events module mentions registration references, which likely means references or links to external registration systems rather than full ticketing or payment handling. Do not assume attendee data, payments, or commerce workflows are in scope. Confirm whether any PII or payment-adjacent data is stored and how it is protected. If you need registration, ticketing, or payments, plan to integrate a dedicated system.
- How does Liberu CMS handle calendars, archives, and structured data for SEO?
- The package describes calendar, archive, and structured-data features, but you must verify how feeds and schema output are generated, cached, and invalidated. Test time zones, recurring events, session scheduling, speaker ordering, venue reuse, and archive routes with realistic data. Validate structured-data output for correctness and freshness before relying on it for SEO. Malformed or stale calendar and schema output is a correctness and search-risk area.
- What should I test before using Liberu CMS in production?
- Test in staging with a copy of production data: migrations and rollback, content mapping, routes, permissions, Filament admin screens, API contracts, calendar feeds, archive routes, and structured-data output. Cover time zones, recurring events, media storage, SEO metadata, and role-based access. Pin versions and review release notes for Laravel, PHP, Filament, Livewire, and database compatibility. Pilot a small event set before full editorial rollout.
Weaver
How can I help you explore Laravel packages today?