Build a Cat Photo App - Step 14

HTML-CSS
1

Tell us what’s happening:

don’t know what to do .

Your code so far

<html>
  <body>
    <main>
      <h1>CatPhotoApp</h1>
      <h2>Cat Photos</h2>
      <!-- TODO: Add link to cat photos -->

<!-- User Editable Region -->

      <p>Everyone loves  <img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/running-cats.jpg"</p> online!</p>
     

<!-- User Editable Region -->

      <p>See more <a href="https://freecatphotoapp.com">cat photos</a> in our gallery.</p>
      <img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg" alt="A cute orange cat lying on its back.">
    </main>
  </body>
</html>

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36 Edg/136.0.0.0

Challenge Information:

Build a Cat Photo App - Step 14

2

Can you say in your own words what specifically you do not understand?

3

Like the other commenter said more context might be better for posting a question. But maybe to get you going over the hump you can search on YouTube there are step by step walkthroughs that will help get you unstuck.

4

I would not use step by step walkthroughs. That bypasses the purpose of doing the exercises.

5

Here’s a clearer and more polished version that gets your point across respectfully and effectively:

⸻

@jermeyLT

Just to clarify—I wasn’t suggesting a full step-by-step walkthrough for everything, just support for specific steps. There are a lot of comments from learners saying they were stuck on a particular step and a short video helped them finally get it.

If a dev never looks things up on Google or ChatGPT, doesn’t that also “bypass the purpose”? Asking questions and learning from examples—whether through a tutorial or docs—is part of how we grow as programmers.

Even the MDN docs include example code. Should we stop using those because they show us how in addition to the what?

People learn in different ways. If a quick example helps someone finally understand and feel confident enough to move forward, I’d say that’s a win.

1 Like
6

Looking up resources and looking up the answer are completely different. Looking up the answer robs you of the opportunity to learn.

7

I totally get what you’re saying—there’s definitely value in wrestling with a problem and not jumping straight to the solution.

But I think there’s a gray area between “looking up the answer” and “seeking out clarity.” A good tutorial or video that explains the why behind a step isn’t just handing over the answer—it’s guiding someone through the logic so they can actually understand it and apply that thinking later.

For many learners, especially those new to programming, seeing how someone thinks through a problem can be the key to unlocking their own problem-solving skills. It’s not all about shortcuts—it’s about building confidence through understanding.

At the end of the day, people learn differently. Some thrive on trial and error. Others benefit from seeing a step explained clearly and then trying it on their own. Both approaches aim for the same goal.

1 Like
8

The great thing is, instead of giving someone a video walkthrough with the answer, we can instead ask about how they are stuck and help them past it so they don’t copy the answer and miss out on the learning :wink:

Giving people solutions or links to solutions just isn’t what this forum is for.