PHPackages nvl/laravel-suite - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. nvl/laravel-suite ActiveLibrary nvl/laravel-suite ================= A cohesive Laravel suite for authentication, content, media, pages, forms, taxonomy, translations, and application infrastructure. 00PHPCI passing Since Aug 8Pushed todayCompare [ Source](https://github.com/nicolasvlachos/nvl-laravel-suite)[ Packagist](https://packagist.org/packages/nvl/laravel-suite)[ RSS](/packages/nvl-laravel-suite/feed)WikiDiscussions main Synced today READMEChangelogDependenciesVersions (1)Used By (0) NVL Laravel Suite ================= [](#nvl-laravel-suite) The NVL Laravel Suite is one installable Composer package containing 20 focused Laravel modules and an integration workbench. The modules remain isolated under `packages/nvl`, retain their namespaces, providers, migrations, tests, documentation, and Laravel Boost skills, and ship together under one version. Packages and API documentation ------------------------------ [](#packages-and-api-documentation) Each module has one canonical API and usage page. These pages cover installation, configuration, primary PHP entry points, optional HTTP surfaces, commands, extension contracts, operational behavior, and verification where applicable. Module identifierResponsibilityAPI and usage`nvl/activity`Activity capture and merged model timelines[Documentation](packages/nvl/activity/README.md)`nvl/auth`Headless authentication, invitations, authenticators, recovery, sessions, RBAC, and security audit[Documentation](packages/nvl/auth/README.md)`nvl/comments`Polymorphic threads, replies, reactions, moderation, reports, and attachments[Documentation](packages/nvl/comments/README.md)`nvl/content`Schema-driven translatable content blocks, placements, Media/reference fields, and rendering[Documentation](packages/nvl/content/README.md)`nvl/csv`Typed CSV analysis, validation, transformation, import, export, streaming, and queued chunk processing[Documentation](packages/nvl/csv/README.md)`nvl/data`Shared Spatie Data and TypeScript transformation support[Documentation](packages/nvl/data/README.md)`nvl/filterable`Validated Eloquent filtering and sorting[Documentation](packages/nvl/filterable/README.md)`nvl/forms`Form CRUD, public rendering/submission, security, analytics, and localized content[Documentation](packages/nvl/forms/README.md)`nvl/mail-notifications`Provider-neutral mail tracking, optional scheduling, MailerSend integration, privacy, and safe interception[Documentation](packages/nvl/mail-notifications/README.md)`nvl/media`Uploads, storage, associations, variations, delivery, and localized metadata[Documentation](packages/nvl/media/README.md)`nvl/metafields`Typed polymorphic custom fields and localized definition/value data[Documentation](packages/nvl/metafields/README.md)`nvl/pages`Localized hierarchical pages, dynamic resources, Content composition, SEO, and sitemaps[Documentation](packages/nvl/pages/README.md)`nvl/primitives`Immutable value objects, exact money, validation, and ISO/reference catalogs[Documentation](packages/nvl/primitives/README.md)`nvl/seo`Localized metadata, canonical/social/structured output, robots, and sitemaps[Documentation](packages/nvl/seo/README.md)`nvl/settings`Typed database-backed application-wide settings[Documentation](packages/nvl/settings/README.md)`nvl/support`Transport-neutral business exceptions and stable response codes[Documentation](packages/nvl/support/README.md)`nvl/taxonomy`Hierarchical attachable vocabularies and localized terms[Documentation](packages/nvl/taxonomy/README.md)`nvl/templates`Versioned Content compositions, validated payloads, PDF/HTML rendering, assignments, and queues[Documentation](packages/nvl/templates/README.md)`nvl/translatable`Shared locale validation, request-scoped content locale, fallback, queries, and writes[Documentation](packages/nvl/translatable/README.md)`nvl/translations`File/database UI-string translation workflows[Documentation](packages/nvl/translations/README.md)See the [package capability catalog](packages.md) for a concise comparison of all modules. The linked module pages are the source of truth for callable APIs and integration guidance. The suite is auto-discoverable and supports Laravel 12 or 13 on PHP 8.3+. Module source and configuration must not reference a host `App\`/`Modules\` class or named host middleware. Internal dependency boundaries remain explicit and are validated in CI, but Composer installs and versions only `nvl/laravel-suite`. Composer installation --------------------- [](#composer-installation) Install the stable suite from Packagist: ``` composer require nvl/laravel-suite:^1.0 ``` Composer installs the clean distribution archive for the selected tag by default. A normal installation does not clone the development repository. For development before the first stable tag, a consumer may use the public GitHub repository directly: ``` composer config repositories.nvl vcs https://github.com/nicolasvlachos/nvl-laravel-suite.git composer require nvl/laravel-suite:dev-main ``` One `vX.Y.Z` tag versions every internal module and produces one release archive. Repository and distribution contents ------------------------------------ [](#repository-and-distribution-contents) The `main` branch is the maintainable source repository. It intentionally keeps the integration workbench, tests, fixtures, static-analysis configuration, lockfiles, and GitHub Actions needed to verify releases. Repository-local AI, MCP, and editor configuration is ignored and is not part of the tracked source. Stable version tags are built from the verified Composer archive. Packagist consumers receive only `composer.json`, the license and package documentation, `src`, `config`, and the runtime contents under `packages/nvl`; development workbench and repository tooling are not included. Translation architecture ------------------------ [](#translation-architecture) `nvl/translatable` is the single runtime for model-backed content: - Metafield definitions and eligible owner values use dedicated translation rows. - Media title, alternative text, and caption use dedicated translation rows. - Taxonomy name and description use `terms_i18n`. - Form name, description, submit/success copy, and arbitrary nested content use `forms_i18n`. - Schema-driven Content block fields use `content_blocks_i18n`. - Laravel language files remain responsible for interface strings and validation messages. The central `TranslationResourceRegistry` gathers Forms, Media, Metafields, SEO, Taxonomy, and application resources from one place. Use `php artisan nvl:translatable:gather --json` for catalog/coverage output. Read [the translation architecture and rollout guide](references/translation-architecture.md) before adding another translated model or adopting an existing localized schema. Local setup ----------- [](#local-setup) ``` composer install cp .env.example .env php artisan key:generate php artisan migrate ``` The root `composer.json` is both the published package manifest and the local workbench manifest. The `Nvl\Workbench` namespace keeps local application fixtures separate from consumer `App\` namespaces. Laravel Herd serves this workspace automatically; do not start a separate PHP development server. Development rules ----------------- [](#development-rules) - Keep changes within the owning module and follow its established architecture and naming conventions. - Keep Controllers as HTTP adapters, Actions as transaction owners, Services as focused collaborators, Models lean, and DTOs explicit. - Add a migration instead of editing a migration that may already be deployed. - Add or update Pest coverage for every behavior change. - CI holds each package at its measured coverage baseline, requires 90% line coverage for newly changed source lines on pull requests and branch pushes, and ratchets package baselines upward as tests improve. - Keep module boundaries and external dependencies declared directly and bounded. - Keep the v1 API free of pre-release aliases; document breaking upgrades explicitly. - Use package Actions and Services from consumers; do not reach into persistence internals. Tests and formatting -------------------- [](#tests-and-formatting) Run one focused package: ``` vendor/bin/pest \ --test-directory=packages/nvl/forms/tests \ --configuration=packages/nvl/forms/phpunit.xml.dist \ --bootstrap=vendor/autoload.php \ --compact \ packages/nvl/forms/tests ``` Run the full monorepo with enough memory for Media binary fixtures: ``` composer quality ``` The root quality gate checks formatting, Larastan/PHPStan at maximum strictness, declared module and extension dependencies, suite architecture/distribution rules, the frozen public contracts, and the complete Pest suite with a 1 GB memory limit. The root integration suite is an executable reference consumer: one application model composes Activity, Comments, Content, Media, Metafields, SEO, and Taxonomy and exercises the shared registries, strict doctors, and a constant eager-loading query budget. Module-specific test suites remain independently runnable through their `phpunit.xml.dist` files. Public and protected extension contracts, command signatures, provider discovery, publish tags, autoload files, configuration, routes, and migrations are recorded in `tools/package-contracts.json`. Compatibility checks fail when that surface moves unexpectedly: ``` composer contracts:check composer contracts:update ``` Only run `contracts:update` after reviewing the semantic-version impact of an intentional contract change. During development, format only changed PHP or validate one manifest with: ``` vendor/bin/pint --dirty --format agent composer validate --strict packages/nvl/forms/composer.json ``` Agent skills ------------ [](#agent-skills) Each module provider exposes its skill directory through a stable `*-skills` publish tag. Modules use the Laravel Boost layout: ``` resources/boost/skills// ├── SKILL.md └── agents/openai.yaml ``` Publish a module skill into a consumer application: ``` php artisan vendor:publish --tag=forms-skills ``` Available package skill tags are: - `activity-skills` - `auth-skills` - `comments-skills` - `content-skills` - `csv-skills` - `data-skills` - `filterable-skills` - `forms-skills` - `mail-notifications-skills` - `media-skills` - `metafields-skills` - `pages-skills` - `primitives-skills` - `seo-skills` - `settings-skills` - `support-skills` - `taxonomy-skills` - `templates-skills` - `translatable-skills` - `translations-skills` Skill sources must describe current package code, validate with the Codex skill validator, and avoid historical namespaces or proposed architectures. Every package uses this one layout. Historical top-level skill directories and future-proposal guidance are rejected by the family validator. Generated TypeScript contracts ------------------------------ [](#generated-typescript-contracts) Modules that expose DTO or enum contracts register their source paths with the Data module; infrastructure-only modules do not acquire a data dependency just for discovery. Applications may add their own paths in `config/nvl-data.php`. Generate declarations during build: ``` php artisan nvl:data:types:generate php artisan nvl:data:types:check php artisan nvl:data:types:manifest ``` The opt-in generated-type surface serves only manifest-listed, pre-generated artifacts and a bounded streamed archive. It is disabled by default, protected by configured middleware when enabled, and never generates during a request. Release workflow ---------------- [](#release-workflow) 1. Choose a semantic version and update the changelog/release notes. 2. Review `composer contracts:check`; acknowledge intentional compatible or breaking changes before updating the baseline. 3. Run migrations and backfills against a representative existing database. 4. Run `composer quality`. Routine CI keeps five gates: formatting/static analysis/manifests/contracts, the complete PHP 8.4 + Laravel 13 + SQLite suite, Laravel 12 on the lowest supported dependencies, PostgreSQL stateful tests, and coverage for packages changed by the event. 5. Run strict Composer validation and `composer audit`. 6. Build the single suite archive with the release version: ``` COMPOSER_ROOT_VERSION=1.0.0 composer archive \ --format=zip \ --dir=/tmp/nvl-suite-archive ``` 7. Do **not** create or push the version tag manually. Open **Actions → Package release → Run workflow** on the default branch and enter the version without a `v` prefix, such as `1.0.0`. 8. The workflow reruns the five quality gates, builds one ZIP, installs that exact artifact in a clean Laravel 13 consumer, and validates discovery, caches, migrations, doctors, and the lock audit. It then creates an annotated `v1.0.0` tag whose tree is the verified clean archive and publishes the GitHub Release. The full development tree remains on `main`; the stable tag contains only files intended for Composer consumers, so Packagist's GitHub distribution archive excludes the workbench, tests, tools, and other development files. 9. Register `nvl/laravel-suite` on Packagist using this GitHub repository and enable the GitHub integration. If the package was already registered, ask Packagist to update after the workflow publishes the tag. 10. Verify the Packagist release in a clean application before announcing it: ``` composer require nvl/laravel-suite:^1.0 ``` Do not publish `dev-main` as a stable dependency. Consumers should use the `^1.0` line. Published NVL migrations retain their package timestamps so they have the same identity as auto-loaded migrations and cannot execute twice. License ------- [](#license) The suite is released under the [MIT License](LICENSE). ### Health Score 20 — LowBetter than 12% of packages Maintenance65 Regular maintenance activity Popularity0 Limited adoption so far Community6 Small or concentrated contributor base Maturity11 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/207204a882e67e970f179df885b6d42fa490e1732eba8529d4182e8f99ca26c8?d=identicon)[nicolas\_vls](/maintainers/nicolas_vls) --- Top Contributors [![nicolasvlachos](https://avatars.githubusercontent.com/u/104830042?v=4)](https://github.com/nicolasvlachos "nicolasvlachos (37 commits)") ### Embed Badge ![Health badge](/badges/nvl-laravel-suite/health.svg) ``` [![Health](https://phpackages.com/badges/nvl-laravel-suite/health.svg)](https://phpackages.com/packages/nvl-laravel-suite) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)