How do I nest an input element within a form element

Tell us what’s happening:
Describe your issue in detail here.

  **Your code so far**

<h2>CatPhotoApp</h2>
<main>
<p>Click here to view more <a href="#">cat photos</a>.</p>

<a href="#"><img src="https://www.bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back."></a>

<p>Things cats love:</p>
<ul>
  <li>cat nip</li>
  <li>laser pointers</li>
  <li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
  <li>flea treatment</li>
  <li>thunder</li>
  <li>other cats</li>
</ol>
<input type="text" placeholder="cat photo URL"><form action="https://www.freecatphotoapp.com/submit-cat-photo"></form>
</main>
  **Your browser information:**

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

Challenge: Create a Form Element

Link to the challenge:

Hello there.

Do you have a question?

If so, please edit your post to include it in the Tell us what’s happening section.

Learning to describe problems is an important part of learning how to code.

Also, the more information you give us, the more likely we are to be able to help.

Hi @gazelle ,

you have to create a <form> tag as shown in the example from this challenge along with the action attribute.

Place the <input> tag between the <form> tag (opening tag ) and </form> tag (closing tag).

I hope it helps

I think @JeremyLT is trying to push people to properly describe the issue they are having rather than us having to work it out ourselves. I can see both points of view on this.
At times it can seem a little harsh but also I do absolutely get the logic behind it and that maybe it’s in thier best interests long term to be able to analyse and describe issues in the world of web dev because if you can’t describe it you can’t google it.
I think there’s probably no right or wrong answer, just different interpretations

Right. Talking about code is a critical skill. My thinking on this is twofold:

  1. Software is typically developed in teams. Learning about how to talk to other developers is a skill that takes practice, so its important to start early.

  2. Not all problems are obvious. You get better help and faster help when you can describe what you need help with.

When someone doesn’t include a description of their issue, I always include the message above, but if its obvious at a quick scan, I’ll also include my assessment of what the problem is.

@JeremyLT I think I have an issue with describing my challenge .
I will continue to work on myself though

Hello @nivethakrishnan72
thanks for the help I really appreciate that I have solved the problem though before seeing this.

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.