Weave Code
Cms Laravel Package
numberninecms/cms
NumberNine CMS is a Laravel-based content management system offering a modular admin interface, page and content management, and extensible building blocks for rapidly launching custom websites. It follows Laravel conventions and supports Blade templates for easy integration.
Core code of NumberNine CMS
Frequently asked questions about Cms
- How do I install numberninecms/cms in an existing Laravel application?
- Install it with Composer using composer require numberninecms/cms, then publish the package config and assets, run the package migrations, and wire up the admin route prefix. NumberNine is a Laravel package bootstrapped through a service provider rather than a standalone application, so it is designed to sit inside a Laravel codebase you already own. Check the repository README for the exact artisan vendor:publish tags and migration commands, since those details can change between 0.x releases.
- Which Laravel and PHP versions does NumberNine CMS support?
- The package does not yet publish clear constraints in the material reviewed here, so read composer.json for its illuminate/* and php requirements before committing. At 0.4.x those constraints may be narrow, and the safest target is a currently supported Laravel major such as Laravel 10 or 11. There is no confirmed CI matrix proving every version combination, so verify compatibility in a scratch branch first.
- Is NumberNine CMS a Laravel package or a standalone CMS application?
- It is a Composer-installed Laravel package, not a separate application you deploy and point a domain at. That means it integrates directly with Laravel's container, Eloquent models, middleware, and Blade templates. The trade-off is that it expects to own routing, migrations, and possibly an auth guard, so treat it as an in-front-of dependency rather than a small utility library.
- Can I run NumberNine CMS on a subdomain or route prefix next to my existing Laravel app?
- Running it as a sidecar on a subdomain or route prefix is the lowest-risk way to evaluate it, because your existing application surface stays untouched. You will still need to reconcile route registration order, middleware groups, and migration ordering where the two surfaces overlap. Whether the package lets you avoid claiming the web middleware group and default auth guard is not documented, so confirm that early.
- Why does the 0.4.5 release use Request::all() instead of Request::get()?
- The changelog describes a single change: retrieving the request array with all() rather than get(). That looks like a compatibility-hygiene fix aligned with newer Laravel and Symfony input handling, but the release note does not explain what broke. Because all() can surface a different input set, including file uploads and adjacent keys, test any code path that consumes that array after upgrading.
- Is it safe to use a pre-1.0 package like NumberNine CMS in production?
- At 0.4.x, semver conventions allow breaking changes in minor bumps, so every upgrade should be treated as a review-required event. A CMS touches auth, routing, storage, uploads, and migrations at once, so a defect in any of those is a production incident rather than a degraded feature. If you adopt it, pin the version, run a staging copy, and keep a rollback plan.
- How actively is NumberNine CMS maintained?
- The evidence points to a small or solo maintainer: a four-digit patch release with a one-line changelog and no visible release cadence. There is no published security policy or LTS commitment in the material reviewed. The 0.4.5 fix is mild positive evidence of forward-compatibility work, but it does not replace checking commit activity and issue responsiveness before you commit.
- Does NumberNine CMS work with Blade templates?
- Yes, the package follows Laravel conventions and supports Blade templates, which is how you integrate your own front-end views with its content and page management. The modular admin interface is also built on top of that Laravel view layer. Expect to customize views through standard Blade overrides rather than a separate templating engine.
- What are the alternatives to NumberNine CMS for adding content management to Laravel?
- The closest architectural comparison is Statamic's core package or a hand-rolled content layer built on Eloquent and Blade. Both occupy the same slot: they add pages, content types, and an admin surface to an app you already control. Choose based on documented version constraints, release cadence, and security process, which is where NumberNine currently provides the least public information.
- What should I check before adopting numberninecms/cms?
- Read composer.json for illuminate/* and PHP constraints, confirm whether CI runs against multiple Laravel majors, and ask whether a documented upgrade guide exists beyond the GitHub compare link. Establish the security disclosure process and any advisory history, and confirm the package can be mounted on a prefix or subdomain without hijacking the default auth guard. Finally, look at test coverage and whether the tests are feature-level rather than unit-only, since a CMS's risk lives in its integration surface.
Weaver
How can I help you explore Laravel packages today?