CMS Module Collection

The module collection supplies reusable definitions, edit forms, templates, translations, and browser behavior for CMS modules. It gives a project a starting vocabulary while allowing its own collection to override the design.

Load the collection

composer require softspring/cms-module-collection:6.1.*@dev

Register the package root, which contains modules/ directly:

# config/packages/sfs_cms.yaml
sfs_cms:
    collections:
        - vendor/softspring/cms-module-collection

<?php

// config/packages/sfs_cms.php
namespace Symfony\Component\DependencyInjection\Loader\Configurator;

return static function (ContainerConfigurator $container): void {
    $container->extension('sfs_cms', ['collections' => ['vendor/softspring/cms-module-collection']]);
};

Do not append /cms to this package's path. Merge the entry with existing collections and keep the application's overrides later in the collection order.

Choose modules for a layout

The collection includes headings, buttons, hero/content elements, and more specialized modules. Inspect the installed modules/ directory and each module's config.yaml for its actual identifier, fields, revision, and group.

Expose the intended modules through the layout/content container's allowed_modules; installing a collection does not mean every module suits every container. Start with a heading and button, preview them in the application's theme, then add more complex elements.

Load browser behavior

For Encore:

// assets/app.js
import '../vendor/softspring/cms-module-collection/assets/modules.js';

The published AssetMapper entry is @softspring/cms-module-collection/modules.js. The application must also load styles appropriate to the selected modules. A Bootstrap-oriented template does not install Bootstrap into the application automatically.

Override a module

Create the same identifier under the application's cms/modules/ directory and override the required files. For example, replace a button's render template while keeping its field structure.

If the data format changes, increment the revision and provide a migration. If only the public template changes, recompile affected published content. See CMS collections and module migrations.