These tutorials focus on evergreen front-of-site skills: semantic HTML, resilient forms, and layout patterns that survive redesigns, framework swaps, and theme rewrites.
Each guide is built as a working example you can copy, inspect, and adapt - with a focus on accessibility, maintainability, and how it feels to use on real devices, not just in a design tool.
These tutorials are free to read, use, and share. They're my way of giving back to the web community that helped me learn.
This is a growing library of front-of-site tutorials. If there's a specific pattern, layout problem, or accessibility question you'd like to see covered, let me know as I keep a running list that I use to shape the next tutorials.
Learn how to turn :root and CSS custom properties into a reusable design token system. We build light/dark themes step by step, wire tokens into real components, and keep everything accessible, and easy to refactor.
When pages are long and dense, structure matters. This tutorial covers headings, landmarks, and layout patterns that keep content-heavy pages scannable, accessible, and maintainable.
Go to the Semantic HTML for Content-Heavy Layouts tutorial ⇒
Practical, repeatable HTML patterns for small business sites: hero sections, service lists, testimonials, and contact panels that stay understandable even when the theme changes around them.
Go to the Semantic HTML Patterns for Small Business Sites tutorial ⇒
Take messy, div-heavy markup and refactor it into clear, semantic structure. We walk through realistic examples so you can see what changes, what stays, and how it affects screen readers and CSS.
Build a complete, accessible form from scratch while learning how to structure your HTML so it stays robust through visual redesigns, CSS rewrites, and design system changes.
Go to the Semantic HTML & Form Inputs - Step-by-Step Tutorial tutorial ⇒
Learn how to structure pages with semantic landmarks, headings, and component-friendly markup so your HTML survives brand refreshes, framework swaps, and CSS rewrites without turning into div soup.
