Beginners almost always fall into the same trap. They decide to learn HTML, open a page listing all 142 existing tags in alphabetical order, and start memorizing. <abbr>, <bdi>, <wbr>... An hour later they've forgotten the first ten, haven't built a single page, and conclude they're "not cut out for this".
HTML isn't learned like a dictionary. It's a language you learn by building real pages, one element at a time, in an order where every brick immediately does something visible. Here's the method I recommend, after years of writing HTML and watching beginners either stick with it or quit.
Why memorizing tags is pointless
There are roughly 110 HTML tags still useful today. Nobody knows them all by heart, not even the devs who make a living from it. And that's fine: you only use about twenty of them day to day. The rest you look up in three seconds when the need shows up, because you know what to search for.
Memorizing a list of tags out of context is like learning vocabulary without ever forming a sentence. You can recite <figcaption>, but if you've never displayed an image with a caption, the word means nothing. The right approach is the reverse: you build a page, you hit a real need ("I need a link", "I want a list"), and you learn the tag right then. It sticks because it's tied to a problem you just had.
HTML describes the meaning of content: this is a heading, this a paragraph, this a link. You're not memorizing tags, you're learning to name the parts of a page correctly. And that only happens by doing.
The right learning order
HTML has a natural progression, from the skeleton of a page down to the details that make the difference. Each step reuses the previous one: you lay the structure first, then fill it, then make it clean and accessible.
1. The structure of a page. First, the skeleton: <!DOCTYPE html>, then <html> containing a <head> (the invisible metadata: tab title, encoding) and a <body> (everything that shows up). Until that mold is clear, the rest floats in a vacuum. Once it's in place, you have a valid page that opens in the browser.
2. Text. Content first: headings from <h1> to <h6> that establish hierarchy, paragraphs <p>, emphasis with <strong> and <em>. It's the part you'll write most often: a website is, above all, structured text.
3. Links and images. What makes the "web" a web: the link <a href="..."> that connects pages to each other, and the image <img src="..." alt="...">. Two tiny tags, but this is where your page stops being an isolated document and comes alive.
4. Lists and tables. To organize content: bulleted lists <ul>, numbered ones <ol>, and tables <table> for real tabular data (not for layout, that's the job of CSS). You start structuring information, not just aligning it.
5. Semantics. The step that separates tinkering from clean work: <header>, <nav>, <main>, <footer>, <section>, <article>. Instead of stacking anonymous <div> elements, you name the zones of your page. The browser, Google and screen readers finally understand what each block represents.
6. Forms. When the page needs to talk back: <form>, <input>, <label>, <button>. Text fields, checkboxes, submit buttons. It's also where you discover the many input types (email, date, number) that do half the validation work for free.
7. Attributes and best practices. Last, what separates correct HTML from polished HTML: attributes (id, class, title), accessibility (an alt that actually describes the image, labels tied to their fields), and the habit of validating your code. This is where "best practices" finally make sense, because they answer problems you've now run into.
Practice without installing anything
The classic blocker is believing you need a complicated editor, a server, a config. For HTML, that's false: a text file and a browser are enough. But the real spark is seeing the result change live as you edit a tag. Without that, you write blind and you give up.
That's exactly what I built in the free interactive HTML course on this site: every step above has its lesson, with examples you edit right in the page and whose output you see instantly, plus exercises and quizzes. You write real HTML from the very first lesson, in the order that works, without ever installing anything.
And once the page is structured, the logical next step is to style it: that's the job of the CSS course, which picks up exactly where HTML stops. HTML for meaning, CSS for appearance: that's the foundation of the whole craft.
Conclusion
The best way to learn HTML isn't to read about HTML, let alone to memorize its tags: it's to build pages, in the right order, seeing the result at every step. Tags aren't a vocabulary to recite, they're tools you grab the moment you need them.
Deep down, the beginner cramming the list wasn't having a memory problem. They'd just started from the end. Put practice first, and HTML stops being a list to remember and becomes what it always was: a simple way to tell the browser what your content means.