Laraslice Laravel Package

Product Decisions This Supports

• Build vs. buy for internal admin/CRUD tooling: LaraSlice generates and ports Laravel admin applications from YAML manifests. v1.8.0’s Default UI program reduces hand-tuning for listings, detail pages, forms, FK labels, option selects, dates, booleans, long text, and wide tables—shifting roadmap effort from custom admin UI work to manifest configuration.
• Legacy port strategy: ONE Studio unifies Port, Design, Create, and Manage into a single shell with a “What are you starting from?” entry point (BRD/AI brief, legacy port, from-zero design). The production ERP port validation strengthens the case for using LaraSlice on complex legacy schemas.
• Manifest governance and change control: YAML-only manifests, Studio preview-first diffs with version history, and slice:diff in the CLI support auditable, reviewable changes. PMs can treat the manifest as the source of truth and enforce review workflows.
• Upgrade planning: JSON manifest reads are removed—a breaking change. Teams with slice.json must run slice:migrate-json-to-yaml (use --dry-run first) and refresh published UI components with slice:repair --publish-ui. This is a planned migration, not a drop-in upgrade.

When to Consider This Package

• You need rapid Laravel-based admin panels, CRUD apps, internal tools, or data management screens driven by structured manifests.
• You are porting legacy databases/applications and want generated UI with FK labels, enum/option handling, human-readable dates, Yes/No booleans, and curated navigation by default.
• You want a visual studio plus CLI parity, with diff previews and version history for manifest changes.
• You can adopt YAML as the only manifest format and have capacity to migrate existing JSON-only slices.
• Look elsewhere if you need a general-purpose CMS, public-facing site builder, non-Laravel stack, fully no-code platform, or cannot tolerate a breaking manifest migration and UI republish step.

How to Pitch It (Stakeholders)

Executives: LaraSlice v1.8.0 reduces time-to-value for internal admin/CRUD delivery and legacy porting by generating production-ready Laravel UIs from YAML manifests with strong defaults. The unified studio and diff/version-history workflow lower delivery and change-control risk. The main caveat is a breaking manifest migration that should be planned, not treated as a routine patch.

Engineering: Adopt YAML-only manifests; migrate JSON slices with slice:migrate-json-to-yaml --dry-run, then migrate, and republish UI with slice:repair --publish-ui. ONE Studio unifies the four studios while keeping POST endpoints unchanged and redirecting legacy URLs. Use slice:validate and slice:diff in CI/review. The Default UI improvements remove common hand-tuning across tables, forms, detail pages, FK labels, options, and formatting.