Order of listing typography and daisyui plugins in README install should be reversed

Created on 17 February 2025, about 2 months ago

Problem/Motivation

On DaisyUI https://daisyui.com/docs/layout-and-typography/ - it is mentions
`You should use official TailwindCSS Typography plugin. It handles everything and it's fully customizable. daisyUI adds some style to @tailwindcss/typography so it will use the same theme as other elements.`

`Make sure you require daisyui AFTER @tailwindcss/typography in tailwind.config.js`

Steps to reproduce

Proposed resolution

Remaining tasks

Replace

  plugins: [
    require("daisyui"),
    require('@tailwindcss/typography'),
  ],

with

  plugins: [
    require('@tailwindcss/typography'),
    require("daisyui"),
  ],

in the README.md file

User interface changes

none

API changes

none

Data model changes

none

🐛 Bug report
Status

Active

Version

4.0

Component

Documentation

Created by

🇱🇺Luxembourg paddy_deburca

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @paddy_deburca
  • 🇫🇷France G4MBINI Bègles

    @paddy_deburca ! I'm really happy to see new users using this theme.

    You seem to know Tailwind very well.

    I struggled for so much time deciding the right way to use Typography plugin with DaisyUI. At the end I decided to use it very minimally on text field with a small preprocess, in order to avoid side effects.

    I would be very interested to discuss it with you. In a Google meet could it be possible for you ?

    For information, as I told you on the other issue, I'm porting the theme to DaisyUI 5. My plan at the end is to not maintain anymore branch 4.0.x, but as Typography plugin is recommended for DaisyUI 5, this discussion is still important to me.

  • 🇱🇺Luxembourg paddy_deburca

    @g4mbini, glad to make contact - even with Google Meet (I am that person that has never used it - but willing to give it a try).

    I created the issue on 4.0.x as it originally existed on this branch - I could have easily created the issue on 5.0.x - but I did not want any of those retro TailwindCss V3 users to be left out.

    I too am most interested in working with DaisyUI v5 going forward.

    I have experience with implementing DaisyUI themes and implementing workflows to help move them from DEV to TEST to PROD environments. Previously I used webpack - but as things can sometimes be too complicated, a more simple PostCSS solution also works quite nicely.

    Glad to talk whenever you wish.

    À bientôt.

  • 🇫🇷France G4MBINI Bègles

    Fixed in readme file ! Thanks for pointing it out ;)

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024