Skip to content

Guides & examples

These guides teach a way of thinking as much as a set of recipes. Start with a page that works in HTML and HTTP, shape it with modern CSS, and introduce optional behavior only when the task requires it. Canonical catalog routes remain the source of truth for API details and copyable examples.

A useful rule of thumb

If the browser already knows how to do something, keep that behavior in the browser. Use an <a> for navigation, a <form> for submission, CSS for layout, and a small enhancement only when the interaction truly needs it.