Technical Documentation Page - Build a Technical Documentation Page

Tell us what’s happening:
Going on 2 days here with these two errors. Html is passing. All the examples I have researched have the same format. I need another pair of eyes, please.
Not passing -

  • 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).

  • You should have the same number of .nav-link and .main-section elements.

My code pen link (CSS is not fully styled. I am working through these two fails first)

https://codepen.io/shayd3555/pen/qBoyvVp

  **Your code so far**
/* file: index.html */
<!DOCTYPE html>
<html lang="en">

<head>
<meta charset="utf-8">
<link rel="stylesheet" href="styles.css">

<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Build a Technical Documentation Page</title>
<style>

</style>
</head>

<body class="body">

<div id="sideNav">
<nav id="navbar">
<header id="head" align="left"> JavaScript Documentation</header>

<ul>
<a class="nav-link" href="#Introduction"><li>Introduction</li>
      </a>
<a class="nav-link" href="#What_you_should_already_know"><li>What you should already know</li>
      </a>
<a class="nav-link" href="#JavaScript_and_Java"><li>JavaScript and Java</li>
      </a>
<a class="nav-link" href="#Hello_world"><li>Hello world</li>
      </a>
<a class="nav-link" href="#Variables"><li>Variables</li>
      </a>
<a class="nav-link" href="#Declaring_variables"><li>Declaring Variables</li>
      </a>
<a class="nav-link" href="#Variable_scope"><li>Variable scope</li>
      </a>
<a class="nav-link" href="#Global_variables"><li>Global variables</li>
      </a>
<a class="nav-link" href="#Constants"><li>Constants</li>
      </a>
<a class="nav-link" href="#Data_types"><li>Data types</li>
      </a>
<a class="nav-link" href="#if...else_statement"><li>if else...statement</li>
      </a>
<a class="nav-link" href="#while_statement"><li>while statement</li>
      </a>
<a class="nav-link" href="#Function_declarations">
        <li>Function declarations</li>
      </a>
<a class="nav-link" href="#Reference"><li>Reference</li>
      </a>
      </ul>
</nav>

<main id="main-doc">

<section class="main section" id="Introduction">
    <header> Introduction</header>
    <p><code></code></p>
    <p><code></code></p>
  </section>

  <section class="main-section" id="What_you_should_already_know">
    <header> What you should already know</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main section" id="JavaScript_and_Java">
    <header> JavaScript and Java</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Hello_world">
    <header> Hello world</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Variables">
    <header> Variables</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Declaring_variables">
    <header> Declaring variables</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Variable_scope">
    <header> Variable scope</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Global_variables">
    <header> Global variables</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Constants">
    <header> Constants</header>
    <p></p>
     <p><code></code></p>
  </section>

  <section class="main-section" id="Data_types">
    <header> Data types</header>
     <p><code></code></p>
     <p></p>
    <ol>
      <li></li>
      <li></li>
      <li></li>
      <li></li>
      <li></li>
      <li></li>
      <li></li>
      </ol>
  </section>

  <section class="main-section" id="if_else...statement">
    <header> if else...statement</header>
    <p></p>
  </section>

  <section class="main-section" id="while_statement">
    <header> while statement</header>
    <p></p>
  </section>

  <section class="main-section" id="Function_declarations">
    <header> Function declarations</header>
    <p></p>
  </section>

  <section class="main-section" id="Reference">
    <header> Reference</header>
  </section>

</main>
</body>

</html>
/* file: styles.css */
@media print {
body {
  font-size: 12pt;
}
}
body { 
margin: 6px;
font-family: Arial;
color: black;
background-color: powderblue;
}

main { 
padding-top: 20px;
margin-left: 280px;
margin-right: 20px;

}

li {
padding: 5px;
}

  **Your browser information:**

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

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:

The section class name is main-section it is one class. Check your class names.

Try changing if else...statment to just if else statment

The nav should be fixed to the left side. But the editor test doesn’t actually check that, the test script does (the tests you can add to your Codepen).

hi - thanks for the reply.
confused - I am using “main-section”

tried changing if else- created an error - changed back and it passed again

confused - if the Codepen passed and my test has a check mark that the nav is on the left side - what does your comment ask me to do/look at?

<section class="main section" id="Introduction">

Are you?

You Codepen does not pass the last layout test. Add the test script.

<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>

I’m just saying the test should fail but it will pass in the editor. The editor test has not been implemented correctly and if it gets fixed at some point (I might fix it) then your project would fail that test. It would be better to use the test script and make sure you are passing that test on Codepen before submitting the project.

Hi. Thank you for taking the time to explain that. I did the add. One question is why don’t we have that code in the user stories to be able to apply it? It would save a lot of time for students and contributors like yourself. Or, is there a source link to these codes I don’t know about?

I see that I missed two - in main-section codes. I corrected both. It is still giving me the error of - 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).

Hi. Been trying for 2 hours plus and still an error. Will someone review this and give me some feedback?

Your href value doesn’t match

<a class="nav-link" href="#if...else_statement">if else...statement</a>
<section class="main-section" id="if_else...statement">
  <header>if else...statement</header>

Tell us what’s happening: Hoping this is noticed. I posted 16 hours past hence. Concerned it wasn’t picked up and noticed - so I apologize for the 2nd help post.

codepen 15/16
[https://codepen.io/shayd3555/pen/qBoyvVp]

STILL getting the error - 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

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 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:

Hello @ShayD ,

Found your problem. Your if else statement section’s id is different than what’s written in the related nav-link 's href attribute.

Your nav-link code:

<li>
        <a class="nav-link" href="#if...else_statement">if else...statement</a>
</li>

Your related section’s id:

<section class="main-section" id="if_else...statement">

Keep it up!

1 Like

Hello! Thank you so much. I literally went through the code line for line. No idea how I missed that. Any tips? There must be a work-around to spot things like this. I used validator (wdg) and nothing showed up like that. I very much appreciate you taking the ball on this and helping me out :slight_smile:

My pleasure.

How did i figure it out?

1- I read the failing step carefully.
2- Examined your code in general to get familiar.
3- Clicked each nav-link on the navbar to check if the related section of the page comes on the focus when clicked.
4- I realized if else statement part was not coming on to focus when clicked on. Thought there might be a mistake in the code related to that part.
5- I realized you named the id and the section a bit confusing and open the mistakes with lots of dots and symbols.
6- I was right. You made some typos there.

When your code is not working as expected but all seems fine, always look for the mistakes in very basic things.

Good luck!

1 Like

An HTML validator won’t find these types of errors. It only finds errors in your HTML syntax. It doesn’t know what the values of your id’s should be and so it can’t possibly tell you that they are wrong :slight_smile: Running your project through a validator is a good idea, it will find errors in your HTML and you should fix those. But it can only tell you about syntax errors with the HTML itself. It can’t tell you if you followed the FCC tests correctly.

Please do not create duplicate topics for the same question. This was already asked and answered in your other thread.

I have merged the threads.

I had posted the second one before the answer, with a note that I apologized in advance. I had thought my reply wasn’t taking in the system as no answer came back for some time. Sorry about that, though.

No worries. But we do not allow duplicate threads for the same question.

You can make a new post in your thread and it will bump it up to the top of the forum for visibility.

thank you for understanding and for explaining how to do it in the future :slight_smile:

1 )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).

  1. Your Technical Documentation project should use at least one media query.

Can you help me I didn’t understand what to do !

good job JS Documentation introduction

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.

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:

  • Client-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.
  • 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.
What you should already know

This guide assumes you have the following basic background:

  • A general understanding of the Internet and the World Wide Web (WWW).
  • Good working knowledge of HyperText Markup Language (HTML).
  • Some programming experience. If you are new to programming, try one of the tutorials linked on the main page about JavaScript.
JavaScript and Java

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>
      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>
  </article>
</section>
<section class="main-section" id="Hello_world">
  <header>Hello world</header>
  <article>
    To get started with writing JavaScript, open the Scratchpad and write
    your first "Hello world" JavaScript code:
    <code>function greetMe(yourName) { alert("Hello " + yourName); }
        greetMe("World");
      </code>

    Select the code in the pad and hit Ctrl+R to watch it unfold in your
    browser!
  </article>
</section>
<section class="main-section" id="Variables">
  <header>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>
</section>
<section class="main-section" id="Declaring_variables">
    <header>Declaring variables</header>
    <article>
      You can declare a variable in three ways:
      <p>
        With the keyword var. For example, <code>var x = 42.</code> This
        syntax can be used to declare both local and global variables.
      </p>
      <p>
        By simply assigning it a value. For example,
        <code>x = 42.</code> This always declares a global variable. It
        generates a strict JavaScript warning. You shouldn't use this
        variant.
      </p>
      <p>
        With the keyword let. For example,<code> let y = 13.</code> This
        syntax can be used to declare a block scope local variable. See
        Variable scope below.
      </p>
    </article>
  </section>
  <section class="main-section" id="Variable_scope">
    <header>Variable scope</header>
    <article>
      <p>
        When you declare a variable outside of any function, it is called a
        global variable, because it is available to any other code in the
        current document. When you declare a variable within a function, it
        is called a local variable, because it is available only within that
        function.
      </p>

      <p>
        JavaScript before ECMAScript 2015 does not have block statement
        scope; rather, a variable declared within a block is local to the
        function (or global scope) that the block resides within. For
        example the following code will log 5, because the scope of x is the
        function (or global context) within which x is declared, not the
        block, which in this case is an if statement.
      </p>
      <code>if (true) { var x = 5; } console.log(x); // 5</code>
      <p>
        This behavior changes, when using the let declaration introduced in
        ECMAScript 2015.
      </p>

      <code>if (true) { let y = 5; } console.log(y); // ReferenceError: y is
        not defined</code>
    </article>
  </section>
  <section class="main-section" id="Global_variables">
    <header>Global variables</header>
    <article>
      <p>
        Global variables are in fact properties of the global object. In web
        pages the global object is window, so you can set and access global
        variables using the window.variable syntax.
      </p>

      <p>
        Consequently, you can access global variables declared in one window
        or frame from another window or frame by specifying the window or
        frame name. For example, if a variable called phoneNumber is
        declared in a document, you can refer to this variable from an
        iframe as parent.phoneNumber.
      </p>
    </article>
  </section>
  <section class="main-section" id="Constants">
    <header>Constants</header>
    <article>
      <p>
        You can create a read-only, named constant with the const keyword.
        The syntax of a constant identifier is the same as for a variable
        identifier: it must start with a letter, underscore or dollar sign
        and can contain alphabetic, numeric, or underscore characters.
      </p>

      <code>const PI = 3.14;</code>
      <p>
        A constant cannot change value through assignment or be re-declared
        while the script is running. It has to be initialized to a value.
      </p>

      <p>
        The scope rules for constants are the same as those for let block
        scope variables. If the const keyword is omitted, the identifier is
        assumed to represent a variable.
      </p>

      <p>
        You cannot declare a constant with the same name as a function or
        variable in the same scope. For example:
      </p>

      <code>// THIS WILL CAUSE AN ERROR function f() {}; const f = 5; // THIS
        WILL CAUSE AN ERROR ALSO function f() { const g = 5; var g;
        //statements }</code>
      However, object attributes are not protected, so the following
      statement is executed without problems.
      <code>const MY_OBJECT = {"key": "value"}; MY_OBJECT.key =
        "otherValue";</code>
    </article>
  </section>
  <section class="main-section" id="Data_types">
    <header>Data types</header>
    <article>
      <p>The latest ECMAScript standard defines seven data types:</p>
      <ul>
        <li>
          <p>Six data types that are primitives:</p>
          <ul>
            <li>Boolean. true and false.</li>
            <li>
              null. A special keyword denoting a null value. Because
              JavaScript is case-sensitive, null is not the same as Null,
              NULL, or any other variant.
            </li>
            <li>
              undefined. A top-level property whose value is undefined.
            </li>
            <li>Number. 42 or 3.14159.</li>
            <li>String. "Howdy"</li>
            <li>
              Symbol (new in ECMAScript 2015). A data type whose instances
              are unique and immutable.
            </li>
          </ul>
        </li>

        <li>and Object</li>
      </ul>
      Although these data types are a relatively small amount, they enable
      you to perform useful functions with your applications. Objects and
      functions are the other fundamental elements in the language. You can
      think of objects as named containers for values, and functions as
      procedures that your application can perform.
    </article>
  </section>
  <section class="main-section" id="if...else_statement">
    <header>if...else statement</header>
    <article>
      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:

      <code>if (condition) { statement_1; } else { statement_2; }</code>
      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.
      <p>
        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>
      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:

      <code>if (condition) { statement_1_runs_if_condition_is_true;
        statement_2_runs_if_condition_is_true; } else {
        statement_3_runs_if_condition_is_false;
        statement_4_runs_if_condition_is_false; }</code>
      It is advisable to not use simple assignments in a conditional
      expression, because the assignment can be confused with equality when
      glancing over the code. For example, do not use the following code:
      <code>if (x = y) { /* statements here */ }</code> If you need to use
      an assignment in a conditional expression, a common practice is to put
      additional parentheses around the assignment. For example:

      <code>if ((x = y)) { /* statements here */ }</code>
    </article>
  </section>
  <section class="main-section" id="while_statement">
    <header>while statement</header>
    <article>
      A while statement executes its statements as long as a specified
      condition evaluates to true. A while statement looks as follows:

      <code>while (condition) statement</code> If the condition becomes
      false, statement within the loop stops executing and control passes to
      the statement following the loop.

      <p>
        The condition test occurs before statement in the loop is executed.
        If the condition returns true, statement is executed and the
        condition is tested again. If the condition returns false, execution
        stops and control is passed to the statement following while.
      </p>

      <p>
        To execute multiple statements, use a block statement ({ ... }) to
        group those statements.
      </p>

      Example:

      <p>
        The following while loop iterates as long as n is less than three:
      </p>

      <code>var n = 0; var x = 0; while (n &lt; 3) { n++; x += n; }</code>
      <p>
        With each iteration, the loop increments n and adds that value to x.
        Therefore, x and n take on the following values:
      </p>

      <ul>
        <li>After the first pass: n = 1 and x = 1</li>
        <li>After the second pass: n = 2 and x = 3</li>
        <li>After the third pass: n = 3 and x = 6</li>
      </ul>
      <p>
        After completing the third pass, the condition n &lt; 3 is no longer
        true, so the loop terminates.
      </p>
    </article>
  </section>
  <section class="main-section" id="Function_declarations">
    <header>Function declarations</header>
    <article>
      A function definition (also called a function declaration, or function
      statement) consists of the function keyword, followed by:

      <ul>
        <li>The name of the function.</li>
        <li>
          A list of arguments to the function, enclosed in parentheses and
          separated by commas.
        </li>
        <li>
          The JavaScript statements that define the function, enclosed in
          curly brackets, { }.
        </li>
      </ul>
      <p>
        For example, the following code defines a simple function named
        square:
      </p>

      <code>function square(number) { return number * number; }</code>
      <p>
        The function square takes one argument, called number. The function
        consists of one statement that says to return the argument of the
        function (that is, number) multiplied by itself. The return
        statement specifies the value returned by the function.
      </p>
      <code>return number * number;</code>
      <p>
        Primitive parameters (such as a number) are passed to functions by
        value; the value is passed to the function, but if the function
        changes the value of the parameter, this change is not reflected
        globally or in the calling function.
      </p>
    </article>
  </section>
  <section class="main-section" id="Reference">
    <header>Reference</header>
    <article>
      <ul>
        <li>
          All the documentation in this page is taken from
          <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide" target="_blank">MDN</a>
        </li>
      </ul>
    </article>
  </section>
type or paste code here

 <nav id="navbar">
    <header>JS Documentation</header>
    <ul>
        <li><a class="nav-link" href="#Introduction">Introduction</a></li>
        <li>
          <a class="nav-link" href="#What_you_should_already_know">What you should already know</a>
        </li>
        <li>
          <a class="nav-link" href="#JavaScript_and_Java">JavaScript and Java</a>
        </li>
        <li><a class="nav-link" href="#Hello_world">Hello world</a></li>
        <li><a class="nav-link" href="#Variables">Variables</a></li>
        <li>
          <a class="nav-link" href="#Declaring_variables">Declaring variables</a>
        </li>
        <li><a class="nav-link" href="#Variable_scope">Variable scope</a></li>
        <li>
          <a class="nav-link" href="#Global_variables">Global variables</a>
        </li>
        <li><a class="nav-link" href="#Constants">Constants</a></li>
        <li><a class="nav-link" href="#Data_types">Data types</a></li>
        <li>
          <a class="nav-link" href="#if...else_statement">if...else statement</a>
        </li>
        <li><a class="nav-link" href="#while_statement">while statement</a></li>
        <li>
          <a class="nav-link" href="#Function_declarations">Function declarations</a>
        </li>
        <li><a class="nav-link" href="#Reference">Reference</a></li>
      </ul>
  </nav>