Weave Code
Cmf Laravel Package
goldbroker/cmf
goldbroker/cmf is a Laravel content management framework package that provides reusable building blocks for defining content types, managing pages, and structuring admin backends, aimed at speeding up CMF-style application development with a clean, modular PHP architecture.
goldbroker/cmf is a lightweight content management framework for Laravel that gives you the building blocks for structured, editable content without locking you into a monolithic CMS. It integrates directly with Laravel's Eloquent models, routing, and Blade views, so content types and admin screens stay close to the code you already write.
- Modular content types defined through configuration and Eloquent models
- Admin scaffolding for creating and editing content records
- Blade-ready rendering with helpers for front-end output
- Media and field handling for common content structures
- Laravel-native integration — migrations, policies, and service provider setup
Frequently asked questions about Cmf
- Is goldbroker/cmf a Laravel package?
- No. It is a maintenance fork that merges Symfony CMF bundles such as RoutingBundle, CoreBundle, ContentBundle, MenuBundle, BlockBundle, MediaBundle, and SearchBundle into one repository. It relies on Symfony bundle registration, dependency injection compiler passes, and PHPCR-ODM, so there is no Laravel service provider or Eloquent integration. Treat it as Symfony-only.
- Can I use goldbroker/cmf in a Laravel application?
- Not feasibly. Laravel has no equivalent bundle registration surface, and the persistence layer is PHPCR-ODM with Jackalope rather than Eloquent or Doctrine ORM. The only coherent option is running it as a separate Symfony service behind an API, which means operating a second framework and persistence stack. For most Laravel apps, Statamic, Twill, Filament, or Blade plus Eloquent is a better trade.
- How do I install goldbroker/cmf?
- You would install it with Composer only in a Symfony application, typically by swapping symfony-cmf constraints to this fork. Before doing so, confirm whether bundle namespaces were preserved or renamed, because that decides whether it is a two-line composer swap or a code-wide refactor. Also confirm which PHPCR transport is expected, such as jackalope-doctrine-dbal or jackalope-jackrabbit. There is no Laravel install path.
- What Laravel versions does goldbroker/cmf support?
- None. The package is built on Symfony kernel concepts and PHPCR-ODM and does not target Laravel release lines. It cannot be composer required into a Laravel app and registered like a normal package. If you need a Laravel CMS, evaluate Laravel-native options instead.
- What are the best Laravel alternatives to goldbroker/cmf?
- Statamic, Twill, and Filament cover most CMS-style backend needs in Laravel, and hand-rolled Blade plus Eloquent remains a valid option for simpler content models. These use relational migrations and Laravel conventions rather than a JCR-style document tree. The CMF value proposition of routes as content, editable menus, block composition, and media management has mainstream Laravel equivalents. Choosing CMF means adopting the JCR tree, not just a feature set.
- Is goldbroker/cmf actively maintained?
- It is best described as a maintenance fork, not a product. The context reports zero stars, zero dependents, zero external contributors, and a bus factor of one, with the only consumer likely the maintainer's own site. The upstream symfony-cmf packages were abandoned, and the fork exists to keep a GoldBroker Symfony site running. Treat it as a reference implementation or last-resort continuity option.
- Does goldbroker/cmf work with Eloquent or Doctrine ORM?
- No. Content is stored through PHPCR-ODM using Doctrine PHPCR and Jackalope, in a JCR-style document tree under /cms/content, and routes are themselves content documents. That data model is fundamentally different from Laravel relational migrations and is not something you bolt onto an existing app. You would need to adopt the JCR tree and its persistence stack.
- What PHP and Symfony versions does goldbroker/cmf support?
- The provided context does not give a verified compatibility matrix. Before any spike, ask the maintainer which PHP and Symfony versions are actually supported and whether CI proves it, since a green build matrix is the strongest health signal available here. Also verify the listed last release date, which is in the future and may be a registry quirk or mistagged commit.
- Is goldbroker/cmf safe for production?
- Technical risk is high. Dependency chain risk dominates: PHPCR, Jackalope, and PHPCR-ODM are effectively unmaintained, and a fork does not fix compatibility with modern PHP and Doctrine DBAL. There is no visible security advisory or disclosure process, so SCA tooling will flag the transitive tree with no upstream to escalate to. Production use is only defensible for keeping an inherited Symfony CMF install running.
- How do I migrate from symfony-cmf to goldbroker/cmf?
- For an existing symfony-cmf application, changing Composer constraints to this fork is the intended keep-the-lights-on move. First check that bundle namespaces were preserved, confirm the PHPCR transport expectation, and verify the license is compatible with the upstream symfony-cmf licenses it absorbed. Look for a reference application or fixture set that boots the stack end to end before committing to the swap.
Weaver
How can I help you explore Laravel packages today?