Technical Documentation Page - Build a Technical Documentation Page

**Tell us what’s happening: Please help, I am not sure how to pass this error. I have linked the href.
" 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)." **

   border: 1px;
  border-color: #000;

#navbar a
  display: block;
  padding: 10px;
  color: #000;


  position: right;

  font-size: 28px;
  font-weight: bold;
  font-family: arial, san-serif;

header h1
  font-size: 20px;


@media only screen and (max-width: 1800px) {
  body {
    background-color: lightblue;


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.

<!DOCTYPE html>
<title>Techinical Documentation Page</title>
<link rel="stylesheet" href="styles.css">
<main id="main-doc">
    <section class="main-section" id="introduction">
        <p>JavaScript is a cross-platform, object-oriented scripting language. It is a small and lightweight language. Inside a host environment (for example, a web browser), JavaScript can be connected to the objects of its environment to provide programmatic control over them.</p>

        <p>JavaScript contains a standard library of objects, such as Array, Date, and Math, and a core set of language elements such as operators, control structures, and statements. Core JavaScript can be extended for a variety of purposes by supplementing it with additional objects; for example:</p>

          <li>lient-side JavaScript extends the core language by supplying objects to control a browser and its Document Object Model (DOM). For example, client-side extensions allow an application to place elements on an HTML form and respond to user events such as mouse clicks, form input, and page navigation.</li>
          <li>Server-side JavaScript extends the core language by supplying objects relevant to running JavaScript on a server. For example, server-side extensions allow an application to communicate with a database, provide continuity of information from one invocation to another of the application, or perform file manipulations on a server.</li>
       <section class="main-section" id="What_you_should_already_know">
            <h1>What you should already know</h1>
        <p>This guide assumes you have the following basic background:</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>

       <section class="main-section" id="JavaScript_and_Java">
        <h1>JavaScript and Java</h1>
      <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>

       <section class="main-section" id="Hello_world">
        <h1>Hello world</h1>
      <p>To get started with writing JavaScript, open the Scratchpad and write your first "Hello world" JavaScript code:</p>

      <code>function greetMe(yourName) { alert("Hello " + yourName); }

      <p>Select the code in the pad and hit Ctrl+R to watch it unfold in your browser!</p>

       <section class="main-section" id="if_else_statement">
        <h1>if else statement</h1>
      <p>Use the if statement to execute a statement if a logical condition is true. Use the optional else clause to execute a statement if the condition is false. An if statement looks as follows:</p>
      <code>if (condition) { statement_1; } else { statement_2; } </code>
      <p>condition can be any expression that evaluates to true or false. See Boolean for an explanation of what evaluates to true and false. If condition evaluates to true, statement_1 is executed; otherwise, statement_2 is executed. statement_1 and statement_2 can be any statement, including further nested if statements.
You may also compound the statements using else if to have multiple conditions tested in sequence, as follows:</p>

<code>if (condition_1) { statement_1; } else if (condition_2) {
statement_2; } else if (condition_n) { statement_n; } else {
statement_last; } </code>

<p>In the case of multiple conditions only the first logical condition which evaluates to true will be executed. To execute multiple statements, group them within a block statement ({ ... }) . In general, it's good practice to always use block statements, especially when nesting if statements:</p>
<code>if (condition) { statement_1_runs_if_condition_is_true;
statement_2_runs_if_condition_is_true; } else {
statement_4_runs_if_condition_is_false; }

<code>if (x = y) { /* statements here */ }</code>

      <nav id="navbar">
        <header>JS Documentation </header>
        <a class="nav-link" href="Introduction" id="Introduction">Introduction</a>
        <a class="nav-link" href="What you should already know" id="What_you_should_already_know">What you should already know</a>
        <a class="nav-link" href="JavaScript and Java" id="JavaScript_and_Java">JavaScript and Java</a>
        <a class="nav-link" href="Hello world" id="Hellow_world">Hello world</a>
         <a class="nav-link" href="if else statement" id="if_else_statement">if else statement</a>

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/ Safari/537.36

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:

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 (').

There are a few issues here

The first issue has to deal with the href values here

each of these href values needs to have the # symbol in front because the link is going to a section on the page with that respective id

The second issue is to remove these duplicate ids here in the navbar

The logic should be when you click on any of the nav links, it should navigate to the section on the page with that id name.
That is why you can remove those ids there because you already identical id names in the section elements

The third issue is that you need to make sure href values with multiple words are separated by underscores like mentioned in the directions


Lastly, you will need to double check and make sure each id name for the section matches identically with the href values

For example, this is incorrect here

because you use all lower letters there but then used an uppercase I here

everything needs to match exactly for the tests to pass

hope that helps


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