Web
Web
- HTTP request lifecycle: What happens between a request arriving and a response leaving, and where your code can hook in.
- Server-rendered HTML: How pages are rendered, how a visitor’s state travels in an encrypted cookie, and how a failed form finds its way back to the page it came from.
- Validation: How rules in struct tags become a cached plan, what
web.Hdoes with the result, and why validation works the way it does. - Internationalization: How Anetos finds the words to show a user: where messages come from, how a request’s language is chosen, and how the language travels with work done for the user later.
- Frontends: Anetos serves a frontend three ways: pages rendered on the server with templ and htmx; pages written as React, Svelte or Vue components that Inertia renders, with the Go side unchanged; and a JSON API with a frontend of its own, a single-page app or a mobile app. This page is how each works, what each keeps in Go, and how to choose.