Weave Code
Coastercms Laravel Package
web-feet/coastercms
Coaster CMS is a Laravel-based content management system with a flexible page builder, reusable blocks, media management, user permissions, and multi-language support, making it easy to build and manage custom websites.
Coaster CMS is a flexible, Laravel-native content management system for building and managing websites with familiar PHP tooling. It pairs a user-friendly admin interface with a modular content model, letting teams manage pages, reusable content blocks, media, and site settings without leaving Laravel.
- Block-based content for reusable, editable page sections
- Laravel integration with familiar routing, Blade, and Eloquent
- User permissions and role-based admin access
- Media and SEO tools for day-to-day site management
- Extensible architecture for custom templates and modules
Frequently asked questions about Coastercms
- Does CoasterCMS work with Laravel 9 or PHP 8.1?
- The last CoasterCMS release was 2020-11-27, so its tested matrix is Laravel 6/7 with PHP 7.2 to 7.4. On Laravel 9+ or PHP 8.1+ expect to fix removed helpers, dynamic-property deprecations, Flysystem v1 to v3 changes, and Symfony and Doctrine DBAL signature changes. Treat that as fork maintenance, not a normal integration, and budget several engineer-weeks.
- How do I install web-feet/coastercms in a Laravel app?
- Install with composer require web-feet/coastercms, then run php artisan coaster:install and publish its assets. After that you write a Blade theme and build pages with the block-based editor. Mechanically it is quick on a supported Laravel 6/7 stack, but the stack support is the real gate.
- Is CoasterCMS a good fit for adding a CMS to an existing Laravel application?
- Poorly. CoasterCMS is an opinionated full-stack CMS that assumes it owns the Laravel app, including a catch-all front-end route, its own /admin namespace and UI, its own users, roles, and permissions, and its own migrations. Expect collisions with host routing, auth, sessions, and admin surfaces if you drop it into an existing domain app. Prefer a greenfield site or an isolated satellite app.
- What license does CoasterCMS use and can I use it commercially?
- CoasterCMS is GPL-3.0, which is viral on distribution. Internal use and a hosted SaaS generally do not trigger source-disclosure obligations, but shipping a proprietary on-prem product that embeds Coaster does. Many corporate OSS policies reject GPL-3.0 in product dependencies, so get legal sign-off before engineering spend.
- Can CoasterCMS be used as a headless CMS with a JSON API?
- There is no meaningful headless or API-first story. Content is not exposed as a first-class JSON contract, so decoupled or multi-channel use requires custom work. If you need that, run Coaster as an isolated satellite app and expose a read-only cached JSON feed of published content yourself.
- What features does CoasterCMS include and how do themes work?
- It includes block-based page building, Blade theme support under resources/views/themes, multi-language content, a clean admin interface, and users, roles, and permissions. Themes are driven by the block-based content model and depend on internal View and Blade conventions, which are the first thing to break on framework upgrades.
- Is CoasterCMS actively maintained and safe for production?
- Treat it as high technical risk. The 2020 release leaves an end-of-life framework baseline, likely unpatched transitive CVEs in composer.lock, zero Packagist dependents, and a small vendor with no visible commercial support or SLA. It can be tolerable for an isolated public marketing site, but not for a customer-facing transactional surface.
- How hard is it to upgrade CoasterCMS to a newer Laravel version?
- Expect real work, not a composer update. You will need to address removed str_* and array_* global helpers, dynamic-property deprecations, Flysystem v1 to v3 storage APIs, Symfony major-version bumps, and Doctrine DBAL signature changes. Realistically plan three to six engineer-weeks plus indefinite ownership of the fork.
- How do I migrate away from CoasterCMS or export its content?
- Exit is a data-extraction project because content lives in a bespoke block table with serialized block settings. Plan the export path before you commit, and prefer an isolated deployment so the main app's data is not entangled. Document how published pages and block settings map to your next system.
- What alternatives to CoasterCMS should I consider for block-based Laravel content management?
- The source does not name specific alternatives, but it advises that each capability driving the decision, such as page builder, blocks, multi-language, or roles, has a maintained alternative. Choose a package that supports your current Laravel and PHP versions and has recent releases and dependents. Do not downgrade your host app to inherit a stale CMS.
Weaver
How can I help you explore Laravel packages today?