Weave Code
Cms Kernel Laravel Package
lin3s/cms-kernel
Core kernel for the Lin3s CMS ecosystem, providing foundational abstractions and services to integrate content management into PHP applications. It helps bootstrap CMS features and structure content-driven sites with reusable components.
Base package to make CMS in an easy way
Frequently asked questions about Cms Kernel
- Is lin3s/cms-kernel a Laravel package or a Symfony package?
- It is not a Laravel package. It is a Symfony Kernel/Bundle-style composition layer for PHP CMS applications, with Tactician command bus integration and a bundled frontend/admin surface. It does not follow Laravel package conventions or use Laravel's service container as its architectural backbone.
- Can I use lin3s/cms-kernel in a Laravel application?
- Integration feasibility is low. It behaves more like a foreign application skeleton than a package you composer require into Laravel, because it brings Symfony kernel abstractions plus JS/React and asset build concerns. A Laravel app would need substantial wrapping and would still inherit legacy runtime constraints.
- What Laravel versions does lin3s/cms-kernel support?
- None are declared because it is not built for Laravel. Its lineage is Symfony, with Tactician and frontend dependencies tied to older ecosystem eras. You should inspect composer.json for PHP and Symfony constraints rather than looking for Laravel version support.
- How do I install lin3s/cms-kernel with Composer?
- You can require it with Composer if its constraints align with your project, but it is not a drop-in Laravel dependency. Installation involves a shared kernel abstraction plus transitive LIN3S frontend packages and asset tooling. Verify PHP, Symfony, Node, and webpack expectations before adopting it.
- What is lin3s/cms-kernel used for?
- It provides a CMS-oriented application kernel for bootstrapping content-driven PHP applications. It centralizes configuration and core services for modular CMS features with Symfony-based integration. It also ships admin UI and frontend asset concerns, so it is broader than a headless CMS kernel.
- Does lin3s/cms-kernel work with PHP 8?
- The v0.4.0 release notes do not mention PHP 8.x support or Symfony component bumps. Tactician and react-dates are legacy dependencies, so PHP 8 compatibility is not evidenced. Inspect the current composer.json constraints before assuming it runs on maintained PHP versions.
- Is lin3s/cms-kernel maintained and production-ready?
- Technical risk is high. It is pre-1.0 at version 0.4.0, semver permits breaking changes without deprecation cycles, and there is no visible security or version maintenance signal. Adoption is effectively zero and the bus factor is one, practically zero.
- What are the alternatives to lin3s/cms-kernel for Laravel CMS projects?
- For Laravel-native admin and content modeling, evaluate Filament with a headless CMS or a maintained Laravel CMS package. Those avoid adopting Symfony kernel abstractions and a React/asset pipeline inside Laravel. Compare them against the CMS domain value you actually need, such as content modeling, publishing workflow, or admin UI.
- What dependencies does lin3s/cms-kernel bring?
- It brings a Symfony-style kernel, a Tactician command bus, and the LIN3S front foundation package. It also involves React-related frontend dependencies such as react-dates plus CSS and asset build concerns. That expands the integration footprint beyond PHP and introduces vendor concentration risk.
- How should I evaluate lin3s/cms-kernel before using it?
- Start by checking composer.json for PHP and Symfony constraints, then verify transitive dependencies and their maintenance status. Confirm whether Tactician and lin3s-front-foundation force older PHP or Node toolchains. Prototype outside Laravel first; inside Laravel, expect significant wrapping and legacy runtime risk.
Weaver
How can I help you explore Laravel packages today?