gimliapp

https://gimli.app/

I'm working on my Tailwind CSS and Bootstrap DevTools browser extensions.

Yes, later this year. I like Firefox but not many people have asked for a Firefox version, so I have not prioritized it.

Sure, the way I phrased it. I just think it's a bit weird to chose this "direction" for a button. No matter if you are creating something new och using something already made, like this.

As much as I like Tailwind, I too does not understand the Tailwind-in-js thing for basic components likes buttons or checkboxes. Why not just create a button component in whatever framework you are using with scoped styles. This just seems like unnecessary coupling to me.

Looks cool! Shameless plug: I've created a Tailwind extension for chrome: https://gimli.app/tailwinddx.html

For anyone using Tailwind CSS, I would recommend Gimli Tailwind. It's a Chrome DevTools extension enabling smart tools for Tailwind CSS developers.

https://chrome.google.com/webstore/detail/gimli-tailwind/foj...

The author may have a point. Some people will be: "well, just don't use those features then". But you are often not the only dev on a project. And some devs just love using the shiny new stuff even if it does not make any sense.

Shameless plug: https://gimli.app/tailwinddx.html - A Chrome DevTools extension enabling smart Tools for Tailwind CSS :)

For anyone struggling with Tailwind, I would recommend Tailwind DX[0]

[0] https://gimli.app/tailwinddx.html

That's web development, things move in circles :)

I personally find it hard to maintain "normal" CSS. Especially when things change a lot. That first version of a site might be great. But I honestly never seen an old site with good maintainable CSS, it seems developers just give up after a while.

That said, I don't think Tailwind is the solution for everything. Tailwind DX/Gimli is created with styling in the Shadow DOM, which works great. For more regular websites I would use Tailwind. But for more App like solutions I would preferably put the styling scoped within components.

Good suggestion! I will look into it.

I don't think learning something necessarily mean knowing lots of names/properties by heart. You should however have a good idea of what grid and flexbox can do for you and when to use them I think.

I personally have a hard time differentiating between properties such as justify-content / align-content / align-items / justify-items / justify-self and so on. To me those are just random words. Perhaps because English is not my first language, I don't know.

I really think it makes a huge difference to see a small icon describing what properties have been set and to see the difference by hover instead of just reading/editing raw CSS.

I've visited https://css-tricks.com/snippets/css/complete-guide-grid/ and https://css-tricks.com/snippets/css/a-guide-to-flexbox/ countless of times. Some of the stuff just does not seem to stick tbh, especially if you have been working on something not-CSS related for some time.

I'm sure some people just remembers everything, but i'm not one of them :)

How about FlowWeb? is that something I could get away with?

Completely agree with this. It would be very hard to build good tools around float, tables and inline-block which we used to work with. Also, I do find a bit surprising that browser vendors haven't looked more at what tools like webflow are doing.

The current pricing is available at: https://www.kickstarter.com/projects/182057119/gimli

Its basically:

29$ for a 2 year license. 35$ for a 2 year license + beta access

Aw, well i'm glad you wanted to try it :)

Too answer your question though. I've been working on Gimli for the last 18 months now. Using up my own savings, and the reality is that I can't afford to keep working on it for much longer.

I would have loved to be able to present a finished and polished product but i'm just not there yet.

Hi!, creator of Gimli here. i'll be happy to answer any questions you may have