Sébastien Lorber

Thanks for these infos. We'll look at this more in depth soon, as we'll work on our theme gallery (https://github.com/facebook/docusaurus/issues/3522) and Tailwind support is part of it

FYI the next release will have a `configurePostCss` lifecycle, can be useful for Tailwind until we have first-class support https://github.com/facebook/docusaurus/pull/4185

@Romstar no timeline to be defined, as it requires a significant amount of refactoring work to avoid duplicating everything between the themes. It's not a short term priority but more...

@jquense I think you'd better implement that theme yourself for now, and we may be able to benefit from this third-party implementation once Docusaurus has refactored its theme system. The...

Thanks for that @jquense , that already looks great! Deployed it so that community can see a preview: https://docusaurus-tailwind-theme-test.netlify.app/ (had trouble running `4c build` and there's a missing css module...

There's a question that we never asked about what you expect from this Tailwind theme, compared to the existing Classic/Infima theme: - 1: Exact same UX/UI - 2: Same UX,...

Thanks @jquense , that's what I expected Anyone has other good reasons to use Tailwind here?

Note the classic theme is under serious refactorings to create smaller fine-grained and encapsulated components, and move the technical code (non-coupled to Infima) to the `@docusaurus/theme-common` package. - https://github.com/facebook/docusaurus/pull/6844 -...

> it's done when it's done We are continuously extracting technical / non-ui code from the classic theme so that producing a new Tailwind does not lead to a ton...

As commented in the other issue, it looks like a plugin option such as: ```js breadcrumbPrefix: [ { to: "/", label: "🏠" }, { to: "/docs", label: "Docs home" }...