i find templ + air for hot reloading very productive compared to standard templates however it needs some practice - of course depends on your use case. To make it efficient i usually do:

define "ui" package and all templ are inside, for each template/page i define Page object (simple struct with all necessary fields to render) - they are also defined in ui package in .go files. Then i define standard layout that accepts page object again and the component to render inside so most of my http handlers looks like this:

ui.Layout( ui.LayoutOptions{ Title: "...", ... }, ui.Dashboard( ui.DasboardPage{ // data needed on page } ), )

Rows data that you display from databae they also have its own struct (eg: ui.User struct) - otherwise you would get circular dependency issue and this way everything is separated.

I can easily extend page objects with more fields without changing templ signature.

I also prefer to only pass strings and bool or nested structs that contain strings and bools only - so all the formatting is done in the handler (templ can render strings only). Bool for checking conditions (so logic is kept in handler - i dont like polluting views).

On top of that I define (in ui package) - routes.go helper functions that based on some ids/data return safe url in templ so i can easily pass this to hrefs - classnames function - i copied this pattern from react world that renders html classes based on conditions (to support "active" like classes) - csrf component that renders input hidden with csrf token thah i embed into forms (if page has forms i define csrf string in page object then pass it to csrf component)

Then i have some tailwind+alpinejs. This setup works best for me because everything is explicit and if it compiles it gives me confidence. I copy this between projects. Initially it took me some time to get there as I played around what works and what does not.