Cms Laravel Package

Getting Started

Install the package with Composer and review its README/service provider before touching application code. A typical first pass is:

1. composer require panelis-php/cms:^1.2
2. Publish any package config, migrations, and assets if the package exposes publish tags.
3. Run migrations and create/seed an admin user through the package’s documented flow.
4. Open the CMS/admin entry point and confirm navigation renders with only the packages you actually have installed.
5. Build one small admin-managed content area first—for example, a simple page or settings resource—rather than migrating a large domain model immediately.

Look first at the package service provider, published config, routes, and navigation registration code. The v1.2.1 patch is a low-risk maintenance release focused on navigation registration, not a new feature release, so the first use case remains standard CMS/admin integration.

Implementation Patterns

• Keep package configuration in the published config file and environment variables, not in hard-coded service provider values.
• Let the package register its own navigation groups. Add application-specific navigation in your own service provider or CMS extension point rather than duplicating package entries.
• Use Laravel authorization policies/gates around CMS-managed models so admin access and content permissions stay in the app layer.
• Seed baseline CMS data and admin users through idempotent seeders so local, staging, and production environments behave consistently.
• Separate CMS content models from domain models where possible; use the CMS for editorial/admin workflows and keep business logic in application services.
• In multi-package setups, verify navigation only appears for packages that are actually installed. v1.2.1 specifically improves this behavior, so avoid adding workarounds that manually hide missing-package navigation.
• For deployment, run composer install --no-dev, package migrations, and Laravel cache warming in the normal release pipeline. Treat CMS assets and published files as part of deployment artifacts.

Gotchas and Tips

• v1.2.1 is a patch release with no indicated breaking changes. Upgrade with composer update panelis-php/cms and verify the admin navigation after deployment.
• If navigation groups appear or disappear unexpectedly after upgrading, clear caches first: php artisan optimize:clear, then rebuild production caches with php artisan optimize.
• The v1.2.1 fix means navigation registration now depends on installed packages. If a group is missing, confirm the related package is actually installed and autoloaded rather than assuming the CMS failed to register it.
• Check Composer autoload state after adding/removing optional packages: composer dump-autoload and, if needed, php artisan package:discover.
• Be careful with cached config/routes in production. A config or service-provider change can appear to “break” navigation until caches are rebuilt.
• Avoid hard-coding assumptions about navigation group names or ordering. Treat them as package-owned metadata and customize only through documented extension points.
• When debugging registration issues, inspect the package service provider boot order and any app providers that also register CMS navigation. Duplicate or premature registration is a common source of confusing admin menus.