Technical Documentation Page - Build a Technical Documentation Page

Tell us what’s happening:
I don’t know why am not passing the text, i have double checked and not sure what code i putted wrongly?

Each .main-section should have an id that matches the text of its first child, having any spaces in the child’s text replaced with underscores (_ ) for the id’s.

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”)

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 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:
https://www.freecodecamp.org/learn/2022/responsive-web-design/build-a-technical-documentation-page-project/build-a-technical-documentation-pagePreformatted text

Because your code is too long to be ported over automatically, could you please share your code using the Preformatted text tool?
Click on the </> icon and paste your entire code in between the two sets of triple backticks.

<!DOCTYPE html>
<html lang="en">
 <head> 
    <meta charset="UTF-8"/>
    <meta name="viewport" content="width=device-width, initial-scale="1.0"/>
    <link rel="stylesheet" href="styles.css">
    <title>JS Documentation</title>
    </head>
    <body>
    <nav id="navbar">
      <header id="header">JS Documentation</header>
      <ul id="ul-navbar">
       <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="#function_declarations"/> Function declarations </a> </li>
       <li> <a class="nav-link" href="#variables"/> Variables </a> </li>
       <li> <a class="nav-link" href="#if...else_statement"/>If...else statement</a> </li>
       <li> <a class="nav-link" href="#reference"/> Reference </a> </li>
     </ul>
    </nav>
    <main id="main-doc">
      <section class="main-section" id="introduction">
        <header>Introduction</header>
        <article>
        <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>
<ul> <li>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.</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> 
</ul>
</p>
</article>
      </section>
      <section class="main-section" id="what_you_already_know">
        <header>What you already know</header>
        <article>
        <p>This guide assumes you have the following basic background:
<ul> <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> 
</ul>
</p>
</article>
      </section>
      <section class="main-section" id="JavaScript_and_java">
        <header>JavaScript and Java</header>
    <article>
        <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>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>
        <p>To get started with writing JavaScript, open the Scratchpad and write your first "Hello world" JavaScript code:
<p>function greetMe(yourName) { alert("Hello " + yourName); }
greetMe("World");</p>
Select the code in the pad and hit Ctrl+R to watch it unfold in your browser!
</p>
</article>
      </section>
      <section class="main-section" id="function_declarations">
        <header>Function declarations</header>
        <article>
        <p>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>
<p>For example, the following code defines a simple function named square:
function square(number)</p> <p>{ return number * number; }</p>
<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>
<p>return number * number;</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="variables">
        <header>Variables</header>
        <article>
        <p>You use variables as symbolic names for values in your application. The names of variables, called identifiers, conform to certain rules.
<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>
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>
</article>
      </section>
      <section class="main-section" id="if...else_statemnet">
        <header>If...else statement</header>
        <article>
        <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.
        <p>You may also compound the statements using else if to have multiple conditions tested in sequence, as follows:</p>

        <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_3_runs_if_condition_is_false;
        statement_4_runs_if_condition_is_false; } </code></p>
        
        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:
        
        <p><code> if (x = y) { /* statements here */ } </code></p>
        If you need to use an assignment in a conditional expression, a common practice is to put additional parentheses around the assignment. For example:
       <p><code> if ((x = y)) { /* statements here */ } </code></p>
       </article>
      </section>
      <section class="main-section" id="reference">
        <header>Reference</header>
        <article>
        <p> <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>
        </p>
        </article>
      </section>
    </main>

You have a typo in one of your .main-section id attributes.

The text and href of one of your nav-links does not match the id and header of the corresponding section (there’s an extra/missing word).

The casing of your href and corresponding section id attributes is not consistent in a few cases (e.g. ‘hello_World’ and ‘hello_world’).

When I fixed all of these issues, your code passes all of the above tests.

1 Like

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