Technical Documentation Page - Build a Technical Documentation Page

[marrwon27]

Tell us what’s happening:
Each .nav-link should have an href attribute that links to its corresponding .main-section (e.g. If you click on a .nav-link element that contains the text “Hello world”, the page navigates to a section element with that id).
Your code so far

<nav id="navbar"><header class="navbar">Technical Documentation</header><a class="nav-link" href="Introduction">Introduction</a></nav>
   </section>
   <section id="What_you_should_already_know" class="main-section"> 
     <header id="What_you_should_already_know">What you should already know</header> 
     <p>This guide assumes you have the following basic background:</p>
   <p></p>
   <li>A general understanding of the Internet and the World Wide Web (WWW).</li>
   <li>Good working knowledge of HyperText Markup Language (HTML).</li>
   <li>Some programming experience. If you are new to programming, try one of the tutorials linked on the main page about JavaScript.</li>
   <code></code>
    <nav id="navbar"><a class="nav-link" href="What_you_should_already_know">What you should already know</a></nav>
   </section>
   <section id="JavaScript_and_Java" class="main-section">
     <header id="JavaScript_and_Java">JavaScript and Java</header> 
     <p>JavaScript and Java are similar in some ways but fundamentally different in some others. The JavaScript language resembles Java but does not have Java's static typing and strong type checking. JavaScript follows most Java expression syntax, naming conventions and basic control-flow constructs which was the reason why it was renamed from LiveScript to JavaScript.

</p>
     <p>In contrast to Java's compile-time system of classes built by declarations, JavaScript supports a runtime system based on a small number of data types representing numeric, Boolean, and string values. JavaScript has a prototype-based object model instead of the more common class-based object model. The prototype-based model provides dynamic inheritance; that is, what is inherited can vary for individual objects. JavaScript also supports functions without any special declarative requirements. Functions can be properties of objects, executing as loosely typed methods.</p>
     <p>JavaScript is a very free-form language compared to Java. You do not have to declare all variables, classes, and methods. You do not have to be concerned with whether methods are public, private, or protected, and you do not have to implement interfaces. Variables, parameters, and function return types are not explicitly typed.</p>
     <li></li>
     <code></code>
     <nav id="navbar"><a class="nav-link" href="JavaScript_and_Java">JavaScript and Java</a></nav>
      </section>
   <section id="Hello_World" class="main-section">
     <header id="Hello_world">Hello world</header>
     
     <p>To get started with writing JavaScript, open the Scratchpad and write your first "Hello world" JavaScript code:</p>
     <li></li>
     <code>function greetMe(yourName) { alert("Hello " + yourName); }
greetMe("World");</code>
      <p>Select the code in the pad and hit Ctrl+R to watch it unfold in your browser!</p>
     <nav id="navbar"><a class="nav-link" href="Hello_World">Hello World</a></nav>
      </section>
   <section id="Variables" class="main-section">
     <header id="Variables">Variables</header>
      <p>You use variables as symbolic names for values in your application. The names of variables, called identifiers, conform to certain rules.</p>
     <p>A JavaScript identifier must start with a letter, underscore (_), or dollar sign ($); subsequent characters can also be digits (0-9). Because JavaScript is case sensitive, letters include the characters "A" through "Z" (uppercase) and the characters "a" through "z" (lowercase).</p>
     <p>You can use ISO 8859-1 or Unicode letters such as å and ü in identifiers. You can also use the Unicode escape sequences as characters in identifiers. Some examples of legal names are Number_hits, temp99, and _name.</p>
     <li></li>
     <code></code>
     <nav id="navbar"><a class="nav-link" href="Variables">Variables</a></nav>

Your browser information:

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:

freeCodeCamp.org

[hbar1st]

I’ve edited your code for readability. When you enter a code block into a forum post, please precede it with a separate line of three backticks and follow it with a separate line of three backticks to make it easier to read.

You can also use the “preformatted text” tool in the editor (</>) to add backticks around text.

See this post to find the backtick on your keyboard.
Note: Backticks (`) are not single quotes (').

[hbar1st]

Hi, welcome to the forum!
We see you have posted some code but did you have a question?

[marrwon27]

all 5 of my nav-links hav the href attribute, but i still get error message

[hbar1st]

I am gonna guess that the test doesn’t like that you have multiple navigation bars.
You should have exactly one nav bar on this page and it should contain all the nav-links within it.

[lasjorg]

The point of the nav is to link to the sections. If each section just has a link above it you have to go to the section to get the link to it. Which doesn’t make much sense.

Also, an id attribute value should be unique. You shouldn’t have multiple elements with the same id. In this case, the tests also rely on that fact and will find the first element with a navbar id and use that for the tests.