Technical Documentation Page - Build a Technical Documentation Page

Tell us what’s happening:
I’m done the certification project on Technical Document, but result says " Your #navbar should always be on the left edge of the window." For me, navbar looks showing left of the window all the time. I’m wondering if my understanding is not correct or coding is not correct… Please help me.

Your code so far

<!--HTML-->
<!DOCTYPE html>
<html lang="en">
<head>
  <title>JS Documentation</title>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <link rel="stylesheet" href="styles.css">
</head>

<body>
  <div id="content">
    <nav id="navbar">
      <header>JS Documentation</header>
       <a href="#Introduction" class="nav-link">Introduction</a>
    <a href="#What_you_should_already_know" class="nav-link">What you should already know</a>
    <a href="#JavaScript_and_Java" class="nav-link">JavaScript and Java</a>
    <a href="#Hello_world" class="nav-link">Hello world</a>
    <a href="#Variables" class="nav-link">Variables</a>
  </nav>


  <main id="main-doc">

    <section class="main-section" id="Introduction">
      <header>
        Introduction
      </header>
      
      <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><i>Server-side JavaScript</i> 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>

    </section>

    <section class="main-section" id="What_you_should_already_know">
      <header>
        What you should already know
      </header>
      
      <p>This guide assumes you have the following basic background:</p>
      <ul>
        <li>A general understanding of the Internet and <code>the World Wide Web (WWW)</code>.</li>
        <li>Good working knowledge of HyperText Markup Language (HTML).</li>
      </ul>
    </section>

    <section class="main-section" id="JavaScript_and_Java">
      
      <header>
        JavaScript and Java
      </header>
      <p>JavaScript and Java are similar in some ways but fundamentally different in some others. The <code>JavaScript language</code> 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>
      <ul>
        <li>Client-side JavaScript extends the core language by supplying objects to control a browser and its Document Object Model (DOM).</li>
      </ul>
    
    </section>

    <section class="main-section" id="Hello_world">
      <header>
        Hello world
      </header>
      
      <p>To get started with writing JavaScript, open the Scratchpad and write your first <code>"Hello world"</code> JavaScript code:</p>
      <p>Select the code in the pad and hit Ctrl+R to watch it unfold in your browser!</p>

      <ol>
        <li>avaScript 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. </li>
        <li>Core JavaScript can be extended for a variety of purposes by supplementing it with additional objects; for example</li>
      </ol>
      
    </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, <code>conform</code> 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>
      pYou 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>
      <ul>
        <li>Six data types that are primitives:
          <ul>
            <li>Boolean. true and false.</li>
            <li>null. A special <code>keyword</code> denoting a null value. Because JavaScript is case-sensitive, null is not the same as Null, NULL, or any other variant.</li>
          </ul>
        </li>
        <li>and Object</li>
      </ul>
    </section>
  </main>

  </div>
 </body>
</html>

/*CSS*/
body{
  font-family: sans-serif;
}
header{
  padding: 3px;
  font-weight: bold;
  font-size: 30px;
}
@media (max-width: 500px) {
  #navbar{
    background-color: #999999;
  }
}

#navbar{
  width:20%;
  margin:10px;
  height: 100%;
  overflow-y: scroll;
  overflow-x: hidden;
  float: left;
  border-right: solid 3px  #999999;
  position: fixed;
}
a{
  text-decoration: none;
  color: #000000;
}

.nav-link{
  font-size: 20px;
  display: block;
  border-top: solid 1px;
  padding: 30px 20px;
  
}

#main-doc{
  margin: 20px 0 0 20px;
  float: right;
  width:75%;
}

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:

The tests expect the nav to be touching the left side of the browser window. Margins will prevent it from doing that.

Thank you soooooo much!!! It worked!!! I apreciate for your help!!

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