HTML
Absolute beginners, web learners and designers moving to code.
This page needs a newer browser to run its tools. You can still read everything here.
Building for the browser, starting from the web platform itself: how pages are structured, laid out, styled and made usable by everyone.
Absolute beginners, web learners and designers moving to code.
Web learners, designers and front-end developers who struggle with layout.
Python developers building database-backed web apps. Assumes the Python track's basics (functions, classes, exceptions, virtual environments) and basic HTML; SQL knowledge helps from the ORM-in-depth module onwards.
Front-end developers, designers and QA engineers.
TypeScript developers building back-end services, including Express and Fastify developers moving to a structured framework and teams moving Nest 10 or 11 apps to Nest 12.
Developers who maintain or inherit jQuery code (WordPress, Drupal, Magento, PHP and ASP.NET MVC sites), teams upgrading from jQuery 1.x-3.x to 4.0, and teams removing jQuery gradually.
PHP developers building web applications. Assumes the php track's essentials (types, functions, classes, namespaces and Composer, exceptions, PDO and HTTP basics); basic HTML and SQL help from the first module, and JavaScript only for the Inertia lessons.
Ruby developers who know objects, blocks, modules, gems and Bundler, and some HTML and SQL, and want to ship a real Rails 8.1 app; also developers coming from Django, Laravel or Node.js who want the Rails way explained.
Frameworks change every few years; the browser’s own rules change slowly. Layout, the cascade, forms, links and accessibility work the same under every framework, and many bugs in a framework project turn out to be questions about the platform underneath. Time spent on them pays off whichever tools your team chooses.
Keep a blank page open beside each lesson and rebuild its examples. The browser’s developer tools show which style rule won, how big each box is and why an element sits where it does: open them whenever something surprises you.
Check every page you build at a narrow phone width and with the keyboard alone. A page that works in both usually works everywhere.
Build small pages often: a form, a card layout, a navigation bar. Each one teaches a handful of rules you will use on every project.
Accessibility costs far less while you build than after. Use the element that means what you need, a button for an action and a link for a destination, give every form control a label, and keep enough contrast between text and its background.