Technical Documentation Page - Build a Technical Documentation Page

Tell us what’s happening: Each .nav-link should have text that corresponds to the header text of its related section (e.g. if you have a “Hello world” section/header, your #navbar should have a .nav-link which has the text “Hello world” How to get about this

Your code so far

WARNING

The challenge seed code and/or your solution exceeded the maximum length we can port over from the challenge.

You will need to take an additional step here so the code you wrote presents in an easy to read format.

Please copy/paste all the editor code showing in the challenge from where you just linked.

Replace these two sentences with your copied code.
Please leave the ``` line above and the ``` line below,
because they allow your code to properly format in the post.

Your browser information:

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

Challenge Information:

Technical Documentation Page - Build a Technical Documentation Page

Hello!
Welcome back to the fCC forum
So you have not attached your code here, but I will try explaining.

So in your a element that links your text, you should add a ‘#’ before your heading and for any spaces you add a '_' . So example if your heading is ‘Hello World’ your a element will look like this <a href="#Hello_World>
And then when you link it to your heading, you should have an id with tyour heading, but it doesn’t need a ‘#’, it only needs a '_' for any spaces.
Example: <section id="Hello_World>

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