Download the PHP package c975l/core-bundle without Composer

c975L CoreBundle

The base of the c975L ecosystem in a single package: ConfigBundle (database-backed configuration, EasyAdmin dashboard, user accounts, health check, sitemaps) and UiBundle (page blocks, media library, theme, legal models, forms, emails). Two bundles, one package, one release.

One package, two bundles

This is not a merged bundle. A Composer package is not a Symfony bundle: this package ships the two bundles unchanged, each with its own namespace, its own services.yaml, its own configs.json, its own translation domain and its own dashboard section.

There is no c975L\CoreBundle\ namespace. The name core-bundle exists on Packagist only.

Why they ship together

ConfigBundle and UiBundle referenced each other in their composer.json, in both directions:

• Ui → Config is deep and deliberate: ConfigServiceInterface is read everywhere, and every *ProviderInterface of the generic registry mechanism is declared in ConfigBundle.
• Config → Ui comes from the dashboard itself (FontRegistry, FormThemeRegistry, StylesheetManagementRegistry, ScriptAdminRegistry, WhatsNewRegistry) and from user accounts (Form/FormField + EmailService).

Two packages that require each other cannot be released independently, and neither can see the other's work-in-progress — only its last published version. They were never two layers; they were one layer billed as two. This package says so out loud.

Installation

Then register both bundles — they remain two entries:

What the blocks look like

One tile per kind of the 32 UiBundle ships, captured on the showcase at bundles.975l.com, where every one of them is rendered live. A page is composed out of them in the back-office, with no template written for it - see Built-in block kinds for what each one takes.

Documentation

Each bundle keeps its own README, unchanged:

• ConfigBundle
• UiBundle

Each also ships four skills under its own skills/ directory, written for the coding agent of the site installing the package rather than for someone modifying it — see UiBundle.

Its history, on the other hand, is the package's: UPGRADE.md carry both bundles from here on. Each bundle's own files stop at its last published release — v5.17.1 for ConfigBundle, v1.17.0 for UiBundle — and are kept as archives.

Quality checks

The nine checks the CI runs live in composer.json alone, as one list:

composer run -l names what each one covers, and each is callable on its own (composer audit-deps, cs, fixer, stan, stan-scaffold, rector, lizard, test). The workflow calls those same scripts, so a check is never declared twice.

audit-deps is composer audit: it matches the resolved dependencies against the Packagist security advisories, which is where a known CVE in a dependency gets caught — before the push, not once a site has deployed it. Abandoned packages are reported without failing the run.

rector runs --dry-run, so it reports rather than rewrites, over the same sets SymfonyMigrate.sh gives a site. It covers scaffold/ next to each bundle's own code: what is left unmodernised here gets rewritten in the application, where the rewritten file no longer matches the hash ScaffoldInstaller recorded, and the site is then told forever it customized a file it never touched.

A development machine's vendor/ symlinks the sibling repositories, which expose code no tag has published yet — code the CI never sees. bin/ci.sh replays composer qa on a copy of the repository whose dependencies are resolved from Packagist, uncommitted changes included:

The quality tools themselves are not dependencies of the bundle — PHPStan aside, which require-dev carries for its deprecation rules: the CI installs them with setup-php, which always takes the latest release, where a development machine keeps whatever it installed the day it installed it. bin/ci.sh installs them fresh too, and prints the six versions it ran with — Lizard excepted, pinned in both because its counting changed between releases and one release alone matches the thresholds Codacy reads — a rule removed upstream since is otherwise still enforced here, and a rule added since is missed.

Migrating from c975l/config-bundle / c975l/ui-bundle

See UPGRADE.md. In short: replace the two requirements with c975l/core-bundle. No PHP use, no @c975LUi/… template reference, no translation key and no bundles.php entry changes — the namespaces are the same ones.

License

MIT — see LICENSE.