PHPackages                             blackbit\_digital\_commerce/pimcore-cms-toolbox - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. blackbit\_digital\_commerce/pimcore-cms-toolbox

ActivePimcore-bundle[Utility & Helpers](/categories/utility)

blackbit\_digital\_commerce/pimcore-cms-toolbox
===============================================

Basic area bricks to create Pimcore documents for landing pages, Web2Print documents or complete websites

1.0.0(3y ago)1148GPL-3.0-or-later

Since Sep 8Pushed 3y ago4 watchersCompare

[ Source](https://github.com/BlackbitDigitalCommerce/pimcore-cms-toolbox)[ Packagist](https://packagist.org/packages/blackbit_digital_commerce/pimcore-cms-toolbox)[ Docs](https://shop.blackbit.com/pimcore-cms-toolbox/)[ RSS](/packages/blackbit-digital-commerce-pimcore-cms-toolbox/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependenciesVersions (2)Used By (0)

CMS Toolbox
===========

[](#cms-toolbox)

This bundle provides ready-to-be-used area bricks to create Pimcore documents without any programming effort. As many websites use the same basic components and only adjust their specific styling this bundle contains both: basic components with the ability to individually style and configure them. In the end you will have responsible documents which can be used for landing pages, Web2Print documents or complete websites.

Usage
-----

[](#usage)

After installation, you can immediately start to create documents:

[![Add new document](doc/add-document.png)](doc/add-document.png)

Directly after creation the document offers to add all different types of area blocks:

[![Add area brick](doc/add-area-brick.png)](doc/add-area-brick.png)

After adding a `Multi-column Layout` and inside this an `Image` field on the left and a `Headline` and a `Rich Text / WYSIWYG` field on the right, the document looks like this:

[![Finished document](doc/finished-document-editmode.png)](doc/finished-document-editmode.png)

On the frontend this document looks like this:

[![Finished document frontend](doc/finished-document-frontend.png)](doc/finished-document-frontend.png)

Every area brick has a configuration section, for instance in this example the grid has been adjusted to 3/12 and 9/12.

[![Area brick configuration](doc/area-brick-configuration.png)](doc/area-brick-configuration.png)

With those configurations it is possible to individually customize every component to your needs, be it sizes, colors or even adding completely individual CSS rules.

Available Areas
---------------

[](#available-areas)

The following areas come with the toolbox and can be used without any additional configuration (although configuration and modification is possible, if needed):

- **Multi-column layout**
    - This component allows you to define a layout with multiple columns. Within each column, you can place additional area bricks.
    - *Defining columns:*

        The setting window for this component shows a tab for every bootstrap breakpoint. The smallest, xs, determines which columns exist at all. For the other breakpoints, you can modify the size of each column.
    - *Inheritance:*

        Breakpoints inherit their settings from the breakpoints that come before them - `sm` inherits from `xs`, `md` inherits from `sm` etc. `xs` is the default setting and thus can not inherit settings. The other breakpoints have an `Inherit` checkbox, which is enabled by default, so all breakpoints initially inherit settings from xs. If you disable this checkbox, the column settings become modifiable. All larger breakpoints will now inherit the settings you specify here. For example, if you disable inheritance for the `md` breakpoint, the larger breakpoints `lg` and `xl` will then inherit the settings from `md`.
    - *Adding and removing columns and offsets:*

        The breakpoint `xs` determines which columns (and offsets) there are, so columns can only be added or removed there. Be careful when removing columns that had content before. If you save your document, that content is lost.

        There are two types. Actual columns, which can be filled with content, and offsets, which push the following columns to the right. Offsets can not be filled with content.
- **Headline**
    - Single line text with configurable h\*-Tag
- **Image**
    - Single image with options for positioning, sizing, and style
- **Plain Text**
    - Multiline textfield without any styling options
- **Rich Text (WYSIWYG)**
    - Text editor which supports styling / formatting the text. The available features are configurable to prevent too "wild" styling

Integration
-----------

[](#integration)

### Combine with own area bricks / controllers / templates

[](#combine-with-own-area-bricks--controllers--templates)

You can also combine the area bricks of this bundle with your own area bricks and use them together in one document. Please see [Pimcore documentation](https://pimcore.com/docs/pimcore/current/Development_Documentation/Documents/Editables/Areablock/index.html#page_Integrate-an-Areablock-in-a-Template).

Please ensure that your template also includes those JS files (or integrate them into your build workflow):

- /bundles/cmstoolbox/webpack/app.js
- /bundles/cmstoolbox/webpack/common.css
- /bundles/cmstoolbox/webpack/editmode.css (only for editmode)

### Overriding the default views

[](#overriding-the-default-views)

All areas come with default bootstrap markup. If you need to change the markup, you can override the view (template) of an area in your project. You can then make modifications to the area in the new file.

You'll find all default views in `vendor/blackbit/cms-toolbox/src/Resources/views/Areas`. Each area has its own folder. You can copy the whole folder with the included `view.html.twig` to `app/Resources/BlackbitToolboxBundle/views/Areas` and modify the view according to your needs.

###  Health Score

24

—

LowBetter than 31% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity12

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity47

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

1395d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/edf236af532784ace4b8fe1f8342c426bfcbe1ebfaa68b73fecb5a16a4e8f446?d=identicon)[BlackbitNeueMedien](/maintainers/BlackbitNeueMedien)

---

Top Contributors

[![Jan-Walther-Basilicom](https://avatars.githubusercontent.com/u/92913571?v=4)](https://github.com/Jan-Walther-Basilicom "Jan-Walther-Basilicom (1 commits)")

### Embed Badge

![Health badge](/badges/blackbit-digital-commerce-pimcore-cms-toolbox/health.svg)

```
[![Health](https://phpackages.com/badges/blackbit-digital-commerce-pimcore-cms-toolbox/health.svg)](https://phpackages.com/packages/blackbit-digital-commerce-pimcore-cms-toolbox)
```

###  Alternatives

[naoray/blueprint-nova-addon

7123.2k](/packages/naoray-blueprint-nova-addon)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)