[Request] Tailwind CSS in CMS

[CanopusFalling]

It would be a big step up for this project if tailwind worked within the CMS, right now it works only for the styles that are compiled on build and not for any classes exclusively rendered from the database.

This would mean doing the same job that tailwind does at build using workers and I have no idea if that's even technically possible but if it is it would make the project a lot easier to modify in the CMS. Let me know if I've missed something here.

[wenbinf]

You can put tailwind cdn at /admin/settings/code-editor/?type=shared#webHeader
And customize tailwind.config there.

For example, this microfeed instance is using tailwind:
https://brand-assets.listennotes.com/

Does this work for you?

[CanopusFalling]

That does work, and is a good patch solution while there is nothing else but it's explicitly not a production solution.

The Play CDN is designed for development purposes only, and is not the best choice for production.

[wenbinf]

I agree that the current approach may not be well-suited for high-traffic production websites requiring fast rendering. However, it is important to consider the typical use-cases for microfeed at this stage:

• Simple websites with minimal traffic.
• Scenarios where the primary user interface is through RSS/JSON feeds rather than the web UI (akin to a headless CMS).

Looking ahead, we could make it easy to integrate custom themes into existing microfeed instances. This will enable proper implementation of pre-built themes, including those based on Tailwind CSS or other frameworks.

[CanopusFalling]

Incredibly valid if it's low on the priority list, are you happy to just leave the issue here and give it a low priority tag or similar? Or would you rather close it for now and open an issue with a more fleshed out idea of a styling system later on? I'd quite like the feature personally just as a quality of life improvement so when I have the time I might submit a pull request for it.

[wenbinf]

Right now, you have the option to build a Tailwind CSS bundle and place it in R2, thereby replacing the Tailwind CDN referenced in the screenshot below:

However, this doesn't offer an optimal developer experience :( Consider implementing a GitHub Action to automate this process for improved efficiency.

Re: this issue & future PR -

Let's keep this issue open to encourage further community input.
Contributions via PR are highly welcome :)