I am enjoying this workflow so far, with a few bumps along the way. I realize
@tailwindcss/typography was created for situations like this, where we have content written in a CMS, and we do not expect content writers to do
h1.font-xl however, when I am making PHP templates, I need to add the
prose class or else I do not get any styling in those sections for fonts.
@tailwindcss/typography and instead made a custom
fonts.scss where I bring my custom typefaces, and set defaults like what
prose offers. That gives me the flexibility of having those classes through the entire app. No matter if I write an
h1 in a PHP template, or in the CMS I have those defaults.
Another reason I removed
@tailwindcss/typography is because when I am creating a custom PHP template or blade partial and want to change the defaults I need to use the
important class to overwrite the
prose class defaults. That, was a nail in the coffin for me. Curious to hear other’s experiences. Maybe I am doing it wrong?