PgHero VS Tailwind CSS

I am using https://github.com/ankane/pghero/ and this is one of its features with GUI

I use either PgHero or Rails PG Extras on every project

There are tools available which can look at your Postgres logs and tell you if you need to add indexes, I've used https://github.com/ankane/pghero before and it seems decent.

https://github.com/ankane/pghero (open source equivalent to pganalyze)

- [pghero](https://github.com/ankane/pghero)

pghero

If you are using PostgreSQL you can enable logging of slow queries and connect to the server with pghero (https://github.com/ankane/pghero) and check top queries by the number of requests and total usage time. Also, you can just enable logging of queries in Django, and on each request, you will have a list of queries on development, sometimes it's just a missing select_related of prefetch_related to increase performance, or you need to create a complex index.

If you are using rails, pghero is a great gem to get better visibility on your Postgres performance

https://github.com/ankane/pghero

I know others can answer this better but we use a combination of PgHero and logging of slow queries trough jOOQ.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository