Contao Component Style Manager Laravel Package

Support

If you like this extension, we'd love your support in keeping the open-source spirit alive.

If you think this plugin is useful, please consider sponsoring us to help contribute to our time invested and to further development of this and other open source projects.

Your contributions, whether through coding, testing, providing feedback, or even a donation, help ensure that we can continue offering free open source software. Join us in making a difference, and thank you for your support! - Oveleon.

Description

Allows you to easily manage your own CSS classes as groups provided in layouts, pages, articles, modules, news, events, forms, form elements and content elements.

This plugin is designed to simplify theme customizations without the need of manually adding classes or creating new layouts.

• Overview
• Installation
• Documentation
  • Configuration
  • Use template variables
  • Support own extensions
  • Import / Export
  • Bundle-Configurations
  • Migration
• Bugs and feature requests

Overview

• Many possibilities of use (e.g. grids, animations, content properties, ...)
• Clear representation in the backend
• Categories and Groups
  • Combine and output as tabs
• Passing variables to the template
  • Formatting output using predefined methods or your own
• Import / Export (Deprecated)
  • Automatic import of configurations from third-party bundles (Bundle configurations)
  • Partial import
• Available for
  • Layouts
  • Pages
  • Articles
  • Modules
  • Content-Elements
  • Forms
  • Form-Fields
  • News
  • Events
  • Third-Party DCA
• Third-Party plugin support
  • RockSolid Custom Elements

Installation

Via composer

composer require oveleon/contao-component-style-manager

Via contao-manager

Search for StyleManager and add it to your extensions.

Documentation

• Configuration
• Use template variables
• Support own extensions
• Import / Export
• Bundle-Configurations
• Migration

Bugs and feature requests

We appreciate your contributions when opening issues or requesting features. To help keep our issue list tidy, we may need to close issues if questions go unanswered.

Bugs

If you think you have found a bug please follow these guidelines

1. Search for existing issues and check if your problem has already been reported
2. Check if you are using the latest version and if the issue has been fixed already
3. Provide a step-by-step tutorial on how to reproduce the issue in an isolated environment using only this bundle

Feature requests

Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.