- Visual manipulation (draggable handles for padding/margin) - Direct class editing on element click - AI-assisted styling through prompts - Component-based drag and drop system
The goal is to make Tailwind development more visual while maintaining code quality.
Questions for the HN community: - What's broken about current Tailwind workflows? - Would visual editing help or hinder development? - How would you use AI in this context?
Looking for critical feedback before starting development.
+ what people will say when imagining a tool is different from what the will do when considering an actual tool.
+ research is safer than building.
+ research is easier than building.
+ no amount of research is building.
+ research is trying to solve problems you don't have.
It's ok to have an idea and not want to do the hard work to make it happen and hard work without driving enthusiasm is often not worth doing.
Good luck.