Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Feature suggestion for developemnt #238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rubydesign opened this issue Jan 8, 2023 · 1 comment
Closed

Feature suggestion for developemnt #238

rubydesign opened this issue Jan 8, 2023 · 1 comment

Comments

@rubydesign
Copy link

As per title, no problem here, tailwind works great and the gem too. As it is designed.

But i find during development, it is a whole lot faster to prototype in the browser.
Using the development tool (inspector) i add/remove/modify classes in the browser until i am happy and then copy the result into the template. Have another look and move on.
This saves all the reloads and while that may not sound a lot, it adds up. The approach is in line with tailwind i find, and actually got the idea from a video Sam Selikoff, emberconf.

Off course for this to work, one needs the complete tailwind build (300k), so the classes are actually available.

I know i can (and do) achieve this quite easily with an if and the cdn. But i though it would be nice if it were integrated and documented as an at least alternative workflow. If it were integrated, tailwind configuration changes/additions would also be available.

@ifasoldt
Copy link

ifasoldt commented Aug 9, 2023

Ha, came here to leave the exact same comment

@rails rails locked and limited conversation to collaborators Jan 7, 2024
@flavorjones flavorjones converted this issue into discussion #312 Jan 7, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants