Building Full Stack Golang + HTMX + Templ APP

Рет қаралды 12,273

Күн бұрын

In this video I teach you guys from a high overview the basics of HTMX, creating components with Templ and how to integrate it with Golang.
By the end we build a complete full stack web app.
📚 Resources:
Project Source code: github.com/sikozonpc/fullstac...
HTMX Docs: htmx.org/
Templ Docs: templ.guide/
👉 Join the private community to level up as software engineer: selfmadeengineer.com
📢 We're building a Discord community, come and join
/ discord
Hope you liked and thanks for watching!
#golang #htmx #webdevelopment
Time Stamps 👇
00:00:00 Intro
00:03:00 How the Car List works
00:05:26 Implementing the Add Car functionality
00:09:17 Project Start
Video titles ideas (for the algo):
HTMX + Golang Stack
HTMX + Golang + Templ stack

Пікірлер: 32

@ahmedschhaider4762 2 күн бұрын

thanks for the tutorial,

@nurayatbeltaev9072 4 ай бұрын

Let's go, need more of that, don't stop

@klaudiuszbiegacz3519 4 ай бұрын

Great content. Keep up the good work man! I would love to dive deeper into this stack. I hope You will create more stuff like this. Best regards

@kotlinjava5228 23 күн бұрын

thanks for the content!I really appreciate that

@ltardioli 2 ай бұрын

Very nice video!

@amarboro 4 ай бұрын

great content, do more crazy things with htmx, I will definitely watch

@QriousKoder Ай бұрын

Looking forward to the production app you talked about

@gregorydaggett7444 3 ай бұрын

This is almost the exact setup that I've been trying to teach myself. Most examples are either rudimentary or way over my head. For a project about showing search results for a niche, this is going to be so useful. Thank you!

@TiagoTaquelim 3 ай бұрын

Awesome! 💪

@robimgabriel8063 4 ай бұрын

Mano, o teu canal é uma mina de ouro!

@TiagoTaquelim 4 ай бұрын

Muito obrigado 💪

@naranyala_dev 4 ай бұрын

come here because of GO + HTMX

@pratyushrao7979 4 ай бұрын

Let's gooo VIM + HTMX + Go + Tmpl, cultured Backend dev

@samarnagar9699 4 ай бұрын

Ima pretty sure I saw vscode there not vim

@monciego 4 ай бұрын

thank you

@Septumsempra8818 4 ай бұрын

How do we handle caching and also how to we handle client side state? Suppose you add to cart and update cart total badge in top nav. When a user navigates back, the old cart total will be visible. What's the best design pattern to ensure that when a user navigates back, the top nav cart total is the latest?

@TiagoTaquelim 4 ай бұрын

HTMX communicates with the server. So for that, we either make a request to the server for UI state (which is bad imo). Better yet, this is where we need to add some JavaScript into the mix. I've seen people enjoying AlpineJS with HTMX which sits well with it's philosophy. Further reading: htmx.org/docs/#scripting

@Septumsempra8818 4 ай бұрын

@TiagoTaquelim I use HTMX and Alpine.js. The logic of overriding cached HTML with the latest state is important. Most people tell me to use the server, but that answer fails to address the simple cart total problem. There has to be an easy scalable way

@nanonkay5669 2 ай бұрын

From the looks of it, templ is really just the go version of jsx and heavily borrows from component architecture of frontend frameworks. So it'll seem like going from react to go with templ is a pretty small learning curve

@TiagoTaquelim 2 ай бұрын

Yes I had a bit of that feeling as well

@helloworld7796 4 ай бұрын

Hey what do you think about the latest release 1.22 and it's routing? Do you think frameworks or packages around routing are not longer needed for new projects?

@TiagoTaquelim 4 ай бұрын

I think it's pretty cool and for me it has certainly replaced. However, because most of my audience is not using 1.22 I'm using gorilla/mux just for teaching purposes.

@gregorydaggett7444 3 ай бұрын

@@TiagoTaquelim Would it be possible to do a teaching video about the differences? I'm trying to teach myself, and I really don't quite understand how the update might affect the project I want to build. Thanks

@TiagoTaquelim 3 ай бұрын

@@gregorydaggett7444 Hey there isn't much differences tho. As long as your "transport" layer is seperate from your business logic it's easily swaped. Check my video on golang 1.22 (I would recommend starting without any package and only install if needed)