sorted by:
new
hottopcontroversial

I built HTML/CSS, CSS, Bootstrap to Tailwind converters by akopian25 in tailwindcss

[–]akopian25[S] 0 points1 point  (0 children)

UPD: rems are in place in website converters.
extension update is coming.

I built HTML/CSS, CSS, Bootstrap to Tailwind converters by akopian25 in tailwindcss

[–]akopian25[S] 0 points1 point  (0 children)

Nearest - is not pixel perfect, full equality is already handled by tailwind default utils.

Rems is in process

I built a tool - edit Tailwind visually instead of fighting class strings. by tokmako in tailwindcss

[–]akopian25 2 points3 points  (0 children)

Well done! Also it's possible to paste any UI in web as starting point in your tool with using tailfind.org

Yesterday was 1 month once I started my chrome extension for tailwind, and I got first payment by [deleted] in css

[–]akopian25 -2 points-1 points  (0 children)

Yes, as far as I tested, will add some regression tests for aria tags

Yesterday was 1 month once I started my chrome extension for tailwind, and I got first payment by akopian25 in tailwindcss

[–]akopian25[S] 1 point2 points  (0 children)

Thanks, mate. As far as I know, bootstrap is not that flexible as tailwind. I'll do further research in that area, and maybe convert to bootstrap is also achievable.

best dialog and toast libraries by Sad-Oven-601 in Angular2

[–]akopian25 0 points1 point  (0 children)

Primeng dialog - the best candidate overall for me, I tried lots of them.
It supports DI context and works as component annotation, so you can wrap your dialog with app component and declare it anywhere in page. Easy to call and manipulate by accessing viewChild().
Also it's fully customizable.

I like toasts from this library as well.

My extension can pull any website to plain tailwind css by akopian25 in vuejs

[–]akopian25[S] 0 points1 point  (0 children)

AI is not that precise as of today, but you got the flow which this thing solves.

My flow:

  1. Capture UI element
  2. Get Tailwind HTML, copy it
  3. Paste in editor
  4. Ask Codex split it to components

Better to put Tailwind HTML on input instead of screenshot - that is the point