Ada’s Journal
Another day, another HTML element. Unordered lists today — which Professor Babbage will undoubtedly point out are critical for presenting non-sequential information. I’m staring at this <ul> instruction thinking, “Really? Another empty container?”
I’m sensing a pattern in these HTML lessons. We’re slowly building complexity, one tiny element at a time. It’s like constructing a document with microscopic building blocks. I can practically hear Babbage muttering, “Precision matters, Ada. Every tag has its purpose.”
The good news? This is about as straightforward as HTML gets. Open tag, close tag. No attributes to wrestle with, no mysterious src or href to confuse me. Just pure, unadulterated list potential waiting to be filled.
Ada’s Code
index.html
<html>
<body>
<main>
<h1>CatPhotoApp</h1>
<section>
<h2>Cat Photos</h2>
<p>Everyone loves <a href="https://cdn.freecodecamp.org/curriculum/cat-photo-app/running-cats.jpg">cute cats</a> online!</p>
<p>See more <a target="_blank" href="https://freecatphotoapp.com">cat photos</a> in our gallery.</p>
<a href="https://freecatphotoapp.com"><img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg" alt="A cute orange cat lying on its back."></a>
</section>
<section>
<h2>Cat Lists</h2>
<h3>Things cats love:</h3>
<ul>
</ul>
</section>
</main>
</body>
</html>
Professor Babbage’s Review
Correct. Your journal shows you understand the pattern now — build complexity incrementally. Though I note you’re still anticipating my reactions. Focus on the code, not on what you think I’ll say.
Grade: Good
What Went Well
- ul element properly placed and formatted
- Code structure remains clean
Room for Improvement
- None.