Hi all, I followed the cookbook Kirby meets Tailwind CSS | Kirby CMS . Installing Tailwind with npm install tailwindcss@latest leads to this error: mat@macbook kirbyproject % npm run watch > watch > npx tailwindcss -i ./src/css/tailwind.css -o ./assets/css/styles.css -w npm error coul…

Yes, the cookbook doesn’t work with Tailwind 4 anymore. You’d have to follow this guide: Tailwind CLI - Tailwind CSS Also, do not use the JS config for Tailwind 4, but only the tailwindcss, as specified in the guide on the linked Tailwind page.

// style.css // source can also be empty to scan "all" @import "tailwindcss" source("../site/**/*.{html,js,php}"); @plugin "daisyui"; // @plugin "@tailwindcss/typography"; Like @tobimori said, the building process is a bit different because there is no config.tailwind.js file anymore, but the buil…

Hello All, [Screenshot 2025-09-03 at 22.50.58] Sorry to jump into a thread not created by me, but I just jumped to Kirby (Starter pack) and tried to install Tailwind 4 and DaisyUi (same as the OP). Unfortunately, it didn’t work very well for me :slight_smile: I got an error message in the browse…

I did some changes and maybe it works now … I removed some parts from the original Kirby cookbook tutorial (Kirby meets Tailwind CSS): I removed tailwind.config.js and also src/css/tailwind.css In the /src folder, I left only input.css & output.css Changed assets/css/styles.css to this: /*! tai…

doesn’t look to work. Can’t apply any Tailwind or DaisyUI styles. Any other ideas?

You are no longer importing your output.css in your header. 2. You seem to be missing the first ( and must be first ) tailwind import. This is an abbreviated sample of my tailwind4 css @import "tailwindcss"; /* blueprints have TW selectors */ @source "../../../public/content/"; /* the php f…

Thank you @oyster :slight_smile: Hmm actually, it might work now. Fixed what you suggested, and it looks like I can apply Tailwind styling. Hopefully, DaisyUI will work too. Do you think I also need to add source to /assets/css/style.css like in my first post: @import "tailwindcss" source("./si…

Ok it was too early to get excited :slight_smile: now the previous 404 error message returned back: [Screenshot 2025-09-04 at 16.18.46]

Something looks wrong here. The files that contain your @import statements are the input files (-i) and should be in the src folder. Whatever you call the result of the build process css file (-o) should end up in the assets/css folder. Then the files in the assets folder should be loaded in your he…

Tailwind v4 and DaisyUI

Resources Plugins

dimejo October 1, 2025, 9:29am 17

I’ve updated the recipe for Tailwind CSS v4. I didn’t include information about adding DaisyUI specifically, but that should be pretty straight forward. Please take a look:

Topic		Replies	Views
Kirby + tailwind Questions v4	17	1870	January 14, 2024
Kirby + Tailwind @apply function doesn't work Questions v4	4	338	April 1, 2024
Using Tailwindcss in our plugin components? Questions v3	0	294	May 8, 2021
Is Kirby compatible with Tailwindcss 3? Questions v3	4	682	February 7, 2022
Local development using the command line Solutions v3	12	1568	February 1, 2021

Tailwind v4 and DaisyUI

Related topics