Love it. Just the other day I have been looking for something like this.
What preconditions must be met to use this with an existing app? What tech stack is supported (e.g. only Typescript and React and ...)?
The docs say it's framework-agnostic. I assume then that the editor would only be used for editing css, not html, but I'm sure the founder can correct me if I'm wrong.
I'm also curious how they determine where in source the code needs to change, because you could have (a) external stylesheets, (b) a stylesheet in the html head, (c) tailwind classes, (d) some css-in-js variant, or even (e) direct style application of dom elements in your javascript.
> I assume then that the editor would only be used for editing css, not html
It does edit html. Inserting html elements in this case.
> I'm also curious how they determine where in source the code needs to change
Right now we're editing inline-tailwind because it's the easiest option. It only edits the existing tailwind styles so there could be some interaction with existing styles that have higher-priotity.
The plan later is to have users configure how they want their styles written. We have full code access to be able to edit css stylesheets or inject our own.
I'm also curious how they determine where in source the code needs to change, because you could have (a) external stylesheets, (b) a stylesheet in the html head, (c) tailwind classes, (d) some css-in-js variant, or even (e) direct style application of dom elements in your javascript.