More frustration making Technical Documentation Page

HTML-CSS
1

Tell us what’s happening:
I can’t pass because of the following comments :neutral_face: :

-Each element with the class of “main-section” should also have an id that corresponds with the text of each contained within it. (I do have :thinking:)

-When I click on a navbar element, the page should navigate to the corresponding section of the “main-doc” element (done, works :bowing_man:‍♀)

-Each element with the class of “nav-link” should contain text that corresponds to the text within each (did that too :see_no_evil:)

-The navbar element should contain one element which contains text that describes the topic of the technical documentation. (That I don’t understand, a header inside a nav…? :no_mouth:)

Your code so far

Your browser information:

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0.

Link to the challenge:

Could anyone explain me what goes wrong? Thanks a lot!

2

Your id in here:

 <section class="main-section" id="css_snap_points">

must be be the same as your h1 in here:

<h1>css_snap_points</h1>

but you need to change your h1 tag into <header>css_snap_points</header>
Same for all other sections.

3

Oh thanks, so I should remove all the

and

tags, I tried that too, but I’ll try again!

4

:disappointed_relieved: No,1 point less even…:sob:

5

Here what i meant: forked project

6

I see…so not easy styling then…thanks,

but this then…?
The element in the navbar must come before any link () elements in the navbar.

Its really hard to set up a page like that, without tags, headers inside a nav ?? but I have to do it the way fcc wants…

7

Not too hard.take a look at my project to see how I’ve dealt with it.

8

Thanks, upgraded one point already!
So now the nav to the left fcc says…, okeeee :smirk:

Passed! Thanks a lot SorinR!
Only looks so ugly, never mind.

9

Glad I could help. Happy coding