Download the PHP package tobimori/kirby-tailwind-merge without Composer
On this page you can find all versions of the php package tobimori/kirby-tailwind-merge. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download tobimori/kirby-tailwind-merge
More information about tobimori/kirby-tailwind-merge
Files in tobimori/kirby-tailwind-merge
Package kirby-tailwind-merge
Short Description Tailwind Merge for Kirby CMS
License MIT
Informations about the package kirby-tailwind-merge
Kirby Tailwind Merge
Intelligently merge Tailwind CSS v4 classes without style conflicts in your Kirby templates.
This plugin relies on tailwind-merge-php by Tales from a Dev for merging classes and only adapts it to work in the "Kirby ecosystem". Any issues related to merging classes should probably reported over there.
Installation
Usage
This plugin provides helper functions to use in your templates.
attr()
This helper function works similar to the Kirby built-in attr() function and overwrites it to support Tailwind Merge behaviour for the class attribute.
You'll need to disable the built-in attr() helper at the top-most location in your index.php file - before Kirby is loaded.
Example
merge()
merge() applies Tailwind Merge behaviour and outputs a class attribute.
Example
cls()
cls() applies Tailwind Merge behaviour and outputs the contents of class attribute. This can be used to work better with the conditional merge syntax this plugin provides, and also for nesting.
Example
Conditional merging
This conditional merge syntax using arrays can be used with the merge() and attr() functions as well.
Options
| Option | Default | Description |
|---|---|---|
config |
[] |
Additional tailwind-merge configuration (array or closure) |
cache |
true |
Disable caching using Kirbys Cache |
Options can be set in your config.php file:
The config option also accepts a closure for dynamic configuration. It supports all keys from the underlying library — the most useful ones being prefix, theme, classGroups, and conflictingClassGroups.
Custom theme values
If you're using Tailwind CSS v4 without custom @theme values, the plugin works out of the box: standard class names, numeric values, and arbitrary values are all handled automatically.
However, if you've defined custom @theme variables in your CSS, you need to register those names so tailwind-merge can recognize them as conflicting. For example, given a config like this:
You'd extend the theme config with the custom value names (the part after the last - in the CSS variable):
These values are merged with the built-in defaults, so you don't need to re-declare standard names. Without this config, merge('text-h1', 'text-h2') would keep both classes — with it, the plugin correctly resolves to text-h2.
Support
This plugin is provided free of charge & published under the permissive MIT License. If you use it in a commercial project, please consider to sponsor me on GitHub to support further development and continued maintenance of my plugins.
License
MIT License Copyright © 2023-2026 Tobias Möritz
All versions of kirby-tailwind-merge with dependencies
getkirby/composer-installer Version ^1.2
tales-from-a-dev/tailwind-merge-php Version ^0.1