Weave Code
Platform Laravel Package
asgardcms/platform
AsgardCMS Platform provides the core foundation for a modular, multilingual CMS built on Laravel, with extensible modules for managing pages, menus, media, users, and permissions.
AsgardCMS Platform is the core package of a modular, multilingual CMS built on Laravel. It provides the foundation for building and managing content-driven applications with a clean modular architecture, letting you extend functionality through independent modules and themes.
- Modular architecture for pluggable features and themes
- Multilingual content management with per-locale translations
- User, role, and permission management
- Settings and configuration management
- Laravel-based foundation with familiar tooling
Frequently asked questions about Platform
- What is asgardcms/platform?
- asgardcms/platform is a modular, multilingual CMS application built on Laravel 5. It provides an admin interface plus modules for content, pages, media, settings, users, permissions, and translations. It is best treated as a forkable application baseline or reference architecture, not as a library you add to an existing Laravel service.
- Can I install asgardcms/platform in an existing Laravel app with Composer?
- No, not realistically. asgardcms/platform is application-oriented and not designed as a composable package for an existing Laravel app; adding it as a dependency would pull in the whole CMS stack. For existing apps, extract selected module patterns or run the CMS behind a boundary instead.
- Which Laravel and PHP versions does AsgardCMS Platform support?
- It targets Laravel 5-era applications, and its 2018 release implies old PHP and Symfony constraints. It should not be assumed compatible with Laravel 10, Laravel 11, or PHP 8.2+ without a full upgrade audit. Check Composer constraints, PHP extensions, database versions, and admin asset tooling before planning production use.
- Is AsgardCMS Platform still maintained?
- The repository's last release is 2018-09-05, which makes it effectively stale for production dependency purposes. There is no indication in the provided context of active maintenance for modern Laravel or PHP versions. Treat security patching, dependency upgrades, and module compatibility as work you must own.
- How do I install AsgardCMS Platform?
- Install it as a standalone Laravel CMS application baseline, typically by cloning or forking the platform repository or using a create-project-style setup rather than requiring it into another app. Run it in an isolated container first with the target database, cache, queue, and storage drivers to confirm runtime viability. Then decide whether to fork-and-upgrade, isolate it as a legacy CMS, or extract patterns into maintained internal packages.
- Can AsgardCMS modules be reused in a modern Laravel application?
- You can reuse module boundaries, admin patterns, permissions, settings, media, pages, and localization ideas as reference architecture. Direct reuse is harder because the modules are coupled to the AsgardCMS core and old Laravel/Symfony constraints. Plan to extract and refactor selected patterns into maintained internal packages rather than copying modules wholesale.
- How does AsgardCMS Platform handle multilingual content?
- It is built as a multilingual CMS with localization as a core capability. That makes it a useful reference for translation workflows, localized content storage, and admin patterns. In a modernization, validate how existing translated content, URL routing, and locale settings will migrate.
- Can I run AsgardCMS as a headless or API-only CMS?
- It is primarily a full CMS application with an admin interface, not an API-first composable package. You can limit blast radius by isolating it behind an API or subdomain boundary, but expect custom work to expose and secure content endpoints. Assess whether the admin experience and frontend integration are acceptable before committing.
- How should I upgrade or migrate an existing AsgardCMS site?
- Start with a version audit covering Laravel, PHP, Symfony, modules, database, storage, queues, and asset build tooling, including known CVEs. Run a containerized proof of concept, then choose fork-and-upgrade, isolate as a legacy CMS, or extract needed modules and patterns. For content, plan a one-way migration with export scripts, validation, and a rollback rehearsal rather than long-term dual-running.
- What are the production risks of using AsgardCMS Platform?
- The main risks are EOL framework versions, security patch exposure, stale asset and build tooling, module coupling, and high maintenance ownership. The platform can run, but sustaining it on modern Laravel and PHP requires funded upgrade work. Isolate it behind a boundary and assign explicit ownership for patching, dependencies, and module compatibility.
Weaver
How can I help you explore Laravel packages today?