Technical Documentation Page - Step #14 (Confusion)

Tell us what’s happening:
Hi everyone,

First of all, I am new to learning HTML/CSS. In fact, this is my first question that I have asked on this forum. I am having a hard time with step #14 of the technical documentation page project. I was wondering if someone could explain why my div containers are not separating the navigation pane from the content. My idea is to basically split the the nav bar & main content into two separate div containers and then make them appear side-by side. I watch how other people are solving it, but in the end, I just end up copying and not understanding anything. So any guidance is appreciated as I am very confused at this point. Thanks!

Your code so far

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

    <div class = "body-left">
      <nav id="navbar">
          <header>JS Documentation</header>
          <ul id="navigationpane">
            <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="#Javasript_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>

  <div class="body-right">
<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>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>

      <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>
          <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="Javasript_and_Java">
        <header>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>

      <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 "Hello world" JavaScript code:
       <code class="syntax">function greetMe(yourName) { alert("Hello " + yourName); }</code>

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

      <section class="main-section" id="Variables">
        <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>

        <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 class="main-section" id="Declaring_Variables">
        <header>Declaring Variables</header>
        <p>You can declare a variable in three ways:</p>
        <p>With the keyword var. For example,</p>
          var x = 42.
        <p>This syntax can be used to declare both local and global variables.</p>

        <p>By simply assigning it a value. For example,</p>
          x = 42.

        <p>This always declares a global variable. It generates a strict JavaScript warning. You shouldn't use this variant.</p>
          With the keyword let. For example,
        <code>let y = 13.</code>
        <p>This syntax can be used to declare a block scope local variable. See variable scope below.</p>

      <section class="main-section" id="Variable_scope">
        <header>Variable scope</header>
          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.

          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.

          if (true)
 { var x = 5;} console.log(x); //5

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


body {
  font-family: roboto arial;
  line-height: 1.5;
  font-size: 16px;
  display: flex;
  flex-direction: column;
  width: 100%;
  max-height: 35%;
  overflow: scroll;

.body-left {
  display: flex;
  flex-direction: column;
  width: 100vw;
  max-height: 100%;
  background-color: lightgreen;
  overflow: scroll;

#main-doc {
  display: flex;
  flex-direction: row;
  flex-wrap: wrap;
  text-align: justify;
  margin-left: 30%;
  width: 73%;

  overflow: scroll;
  overflow-x: hidden;
  border-bottom: 2px solid grey;
  display: flex;
  flex-direction: column;
  width: 100%;
  height: 35%;
  background-color: light-gray
header {
  padding: 10px;
  font-weight: 600;
  font-size: 1.5rem;

#navbar {
  vertical-align: top;
  display: flex;
  flex-wrap: wrap;
  border-right: 2px solid black;
  width: 25%; 
  height: 100%;
  top: 0px;

#nav-link {
  display: block;
  text-decoration: none;
  padding: 12px 16px;
  border-top: 1px solid black;

.main-section p {
  padding: 16px 20px;


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

Challenge: Technical Documentation Page - Build a Technical Documentation Page

Link to the challenge:

You have syntax errors that make what is rendered not what you meant to be. I suggest you go through your code with a validator and fix all unclosed elements and things like that with a tool like this Ready to check - Nu Html Checker

Once you fix that I would suggest you had flex-direction: row; here instead

Thanks for your help! I’ll go through the code wit the validator and try again. I’ll come back with the update.

It finally looks better than it did before. There is still improvements to be made in terms of styling still. If you have time, do you mind critiquing my page and telling me how I can improve it? Thanks!

That’s not something I a, able to do - you can try the #project-feedback subforum

Ok Awesome. Thanks so much!

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