oveleon / contao-component-style-manager
Style and CSS-Class Manager for Contao Open Source CMS
Fund package maintenance!
oveleon
Installs: 25 273
Dependents: 4
Suggesters: 2
Security: 0
Stars: 23
Watchers: 7
Forks: 6
Open Issues: 1
Type:contao-bundle
Requires
- php: ^8.1
- ext-dom: *
- ext-json: *
- contao/core-bundle: ^4.13 || ^5.1
- doctrine/dbal: ^3.3
- psr/log: ^1.0 || 2.0 || ^3.0
- symfony/config: ^5.4 || ^6.4 || ^7.0
- symfony/console: ^5.4 || ^6.4 || ^7.0
- symfony/dependency-injection: ^5.4 || ^6.4 || ^7.0
- symfony/event-dispatcher: ^5.4 || ^6.4 || ^7.0
- symfony/http-foundation: ^5.4 || ^6.4 || ^7.0
- symfony/http-kernel: ^5.4 || ^6.4 || ^7.0
- symfony/routing: ^5.4 || ^6.4 || ^7.0
- symfony/translation-contracts: ^2.3 || ^3.0
- twig/twig: ^3.8
Requires (Dev)
- contao/manager-plugin: ^2.3.1
Suggests
- contao-thememanager/core: A lightweight forward-thinking CSS component-first-framework leveraging flexbox and custom properties
Conflicts
- contao/core: *
- contao/manager-plugin: <2.0 || >=3.0
- dev-main / 3.6.x-dev
- 3.6.2
- 3.6.1
- 3.6.0
- 3.5.3
- 3.5.2
- 3.5.1
- 3.5.0
- 3.4.3
- 3.4.2
- 3.4.1
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.2
- 3.1.1
- 3.1.0
- 3.0.3
- 3.0.2
- 3.0.1
- 3.0.0
- 2.x-dev
- 2.6.5
- 2.6.4
- 2.6.3
- 2.6.2
- 2.6.1
- 2.6.0
- 2.5.0
- 2.4.4
- 2.4.3
- 2.4.2
- 2.4.1
- 2.4.0
- 2.3.4
- 2.3.3
- 2.3.2
- 2.3.1
- 2.3.0
- 2.2.0
- 2.1.3
- 2.1.2
- 2.1.1
- 2.1.0
- 2.0.1
- 2.0.0
- 1.2.1
- 1.2.0
- 1.1.2
- 1.1.1
- 1.1.0
- 1.0.2
- 1.0.1
- 1.0.0
- dev-fix/strict-type-errors
- dev-develop
This package is auto-updated.
Last update: 2024-10-29 08:19:16 UTC
README
Allows you to easily manage your own CSS classes as groups
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.
Working with Contao 4.13 and Contao ^5.1 (PHP ^8.1)
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
- 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
- Automatic import of configurations from third-party bundles (Bundle configurations)
- Partial import
- Automatic import of configurations from third-party bundles (Bundle configurations)
- 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
- Search for existing issues and check if your problem has already been reported
- Check if you are using the latest version and if the issue has been fixed already
- 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.