Metronic Crud Generator Bundle Laravel Package

Getting Started

Framework reality check first: despite the prompt framing, this is a Symfony bundle, not Laravel. It extends SensioGeneratorBundle's CRUD generator, so it targets Symfony 2.x/3.x projects with the Sensio generator installed. There is nothing to leverage in a Laravel app without a rewrite.

Assuming a Symfony project:

1. Require both generators (this bundle does not pull in Metronic itself — you source that theme separately from KeenThemes):

   composer require sensio/generator-bundle
   composer require ruudy/metronic-crud-generator-bundle
   

2. Register Ruudy\MetronicCrudGeneratorBundle (and SensioGeneratorBundle) in AppKernel.php under dev.
3. Run php bin/console and look for the metronic:generate:crud command (or whatever the bundle aliases — the generator command is the entry point; confirm with list).
4. First use case: point it at a simple Doctrine entity you already have, generate the CRUD scaffold, then swap the Metronic layout/asset includes in the generated base template. Treat the output as a starting point you'll hand-edit, not final code.

Where to look first in the repo: the Command/, Generator/, and Resources/skeleton/ directories. The skeleton Twig templates are what actually differ from stock Sensio output — that's the entire value of the bundle.

Implementation Patterns

• Scaffold-then-refine workflow. The realistic pattern is: generate a CRUD for a single entity, review the controller/form/templates, then port the Metronic markup patterns into your own hand-written CRUDs. Nobody at 2 stars is running this in production on many entities; use it as a template library.
• Template override is the integration point. Symfony's generator resolves skeletons from app/Resources/SensioGeneratorBundle/skeleton/crud/. Copy the bundle's Metronic skeletons there and tweak them for your project — that's how you adapt styling, menu items, breadcrumbs, and the layout wrapper without forking the bundle.
• Pair with your own base layout. Generated templates will reference a Metronic layout block. Wire your app's base.html.twig (with Metronic CSS/JS assets in web/) to that block so generated pages inherit your navigation and theme.
• Batch generation. For simple CRUD-heavy back-office entities, generating all of them in one pass and then normalizing the templates is faster than building each form by hand. Good fit for admin-panel-style apps where 80% of screens are list/show/new/edit.
• Use it as a reference, not a dependency. Read the generated output as a Metronic-styled Twig reference for form layouts, tables, and modals. Even if you drop the generator, the skeleton patterns are reusable.

Gotchas and Tips

• Framework mismatch is the biggest gotcha. Laravel's artisan make:* generators won't touch this. If you're on Laravel, this package is essentially irrelevant — build your own stub-based generator or use laravel-generator-style packages with a Metronic-inspired admin template.
• Deprecated upstream. SensioGeneratorBundle was abandoned after Symfony 3; Symfony 4+ uses MakerBundle instead. This bundle inherits that dead-end. On modern Symfony it either won't install or won't run.
• Metronic licensing. The theme is commercial. The bundle only generates markup referencing Metronic assets — you still need a valid Metronic license, and you're responsible for not redistributing theme files inside the generated output.
• Very low adoption (2 stars, 0 dependents). No community, unlikely to be maintained, no issue-tracker backup. Budget for forking it if you rely on it.
• Debugging generator issues: run commands with -vvv, and if a skeleton isn't found, verify the path resolution order (app/Resources overrides bundle Resources/skeleton). A missing Metronic layout block usually surfaces as a Twig Block ... does not exist at render, not at generation time.
• Extension points: the cleanest way to customize is overriding Twig skeletons and form-type classes under app/Resources, not editing the bundle's PHP. Fork only the generator command if you need different prompts (e.g., adding a "which Metronic page" option).
• Don't commit to it as infrastructure. Given the state of the repo, treat it as a one-time scaffold source; copying the skeleton templates into your own project removes the fragile dependency while keeping the Metronic markup benefit.