Weave Code
Module Cms Content Types Laravel Package
liberusoftware/module-cms-content-types
A Laravel module for defining and managing CMS content types, giving your application structured, reusable content schemas for building flexible editorial workflows.
Liberusoftware Module CMS Content Types adds a flexible content type system to Laravel, letting you define and manage reusable content structures such as articles, pages, and custom post types. It plugs into the Liberusoftware CMS module ecosystem and follows standard Laravel conventions for service providers, configuration, and publishing.
- Define content types with configurable fields and taxonomies
- Register types through config files or service providers
- Publishable config and migrations for quick setup
- Extensible contracts for custom field types
- Seamless integration with other Liberusoftware CMS modules
Frequently asked questions about Module Cms Content Types
- How do I install liberusoftware/module-cms-content-types in a Laravel app?
- Install the module with Composer using composer require liberusoftware/module-cms-content-types, then follow the package README for any publishing steps. Laravel package auto-discovery should register the service provider where supported. Check the package composer.json for Laravel version constraints before installing.
- What Laravel versions does this Liberu CMS content types module support?
- The supported Laravel versions are defined by the package Composer constraints and may change between releases. Check the require section in composer.json and the README compatibility notes before upgrading. Test against the exact Laravel version used by your Liberu CMS installation.
- How do I define a custom content type with JSON field schemas?
- You define a content type and describe its fields in a JSON schema, which the module uses to structure and validate entries. The exact API or admin workflow depends on the Liberu CMS integration, so check the package documentation for the content type model or configuration format. Keep schemas versioned alongside your application code so changes are reviewable.
- How does validation work for content entries in this package?
- Content entries are validated against the field schema defined for their content type, helping keep structured content consistent. Validation should apply at create and update time so invalid field values are rejected before storage. Review the schema field rules and error handling in the README when building forms or imports.
- Does this module support content workflow and versioning?
- Yes, the package description covers validated content entries with workflow and versioning. That means entries can move through defined workflow states and retain versions for review or rollback. Check the package documentation for available states, transition rules, and version history APIs.
- Can I use this package outside Liberu CMS?
- It is built as a Liberu CMS module, so its models, schema handling, and workflow features may assume the CMS is present. You could potentially reuse parts in another Laravel app, but you would need to verify dependencies and integration points. For standalone apps, a simpler custom model or schema package may be more appropriate.
- How should I test content types and entries in my Laravel application?
- Use Laravel testing tools to create content types with known JSON schemas, then assert that valid entries save and invalid entries fail validation. Include tests for workflow transitions and version creation if your application relies on those features. Check whether the module provides factories or test helpers to reduce setup.
- What configuration or migrations do I need to publish?
- The module may include migrations for content types, fields, entries, workflow state, or version tables, plus configuration for CMS integration. Publish the assets according to the README, then run migrations in each environment. Review published configuration before production so table names and workflow defaults match your application.
- What are the production considerations for using JSON content schemas?
- JSON schemas give flexibility, but you should validate on write, plan for schema evolution, and avoid breaking existing entries when fields change. Back up content tables and test migrations before deploying workflow or versioning changes. Also confirm database JSON support and query performance for fields you filter or sort on.
- How is this package maintained and how do I handle Laravel upgrades?
- Maintenance details are best confirmed on Packagist and the repository release history, especially since the repository URL is not listed here. Pin a tested version in composer.json and review changelogs before Laravel upgrades. Run your content type, validation, and workflow tests after each upgrade.
Weaver
How can I help you explore Laravel packages today?