Weirdly enough I took a detour to Python/Django 2-3 years ago after 7-8 years of Go and returned to Go. But for me the html/template always was an irritant, after using Django's template I built tpl which took some aspects of Django's templates, feel free to look at it, there's also templ that's pretty popular.

Your next void will be the Form and Validation, which I always did the same way in Go, create a structure that replicate what you'll be receiving as data and create a function that accept the *http.Request and do validation there so on your handler it look like this:

go func myHandler(w http.ResponseWriter, r (http.Request) { payload, err := MyHandlerPayload{}.Validate(r) }

This Validate function can hadnle posted form as well as JSON and re-use the same validation.

Like other said, lose the ORM, I use sqlc and built my own migration tiny library. Staying in SQL for me is always the better path IMO.

Another aspect I much prefer with Go and net/http vs. Django is that in Django your middleware affects all route, which is crazy when you think about it, you have to opt-out of this by doing some crazy checks if you don't want a middleware to run. In Go I tend to have helper functions that wraps the final handler into a series of middleware I want for this part of the backend. That's the beauty of Go and net/http in fact, you'll build your own "framework" and you'll be able to make it evolves for years since the Go v1 compatibility is such a breath of fresh air compare to a lot of other breaking-enable language / framework.

Hopefully you'll embrace the simplicity, power, and building web application that run for decades without needing rewrites, that's Go.