Pen Settings

HTML

About HTML Preprocessors

HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.

Learn more · Versions

Adding Classes

In CodePen, whatever you write in the HTML editor is what goes within the <body> tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html> tag. If you want to add classes there that can affect the whole document, this is the place to do it.

About the <head>

In CodePen, whatever you write in the HTML editor is what goes within the <body> tags in a basic HTML5 template. If you need things in the <head> of the document, put that code here.

!
Insecure Resource

The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.

CSS

About CSS Preprocessors

CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.

Learn more · Versions

CSS Base

About CSS Base

It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.

Vendor Prefixing

About Vendor Prefixing

To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit- or -moz-.

We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).

Add External Stylesheets/Pens

Any URLs added here will be added as <link>s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.

Powered by Algolia
About External Resources

You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.

You can also link to another Pen here (use the .css URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.

Learn more

+ add another resource

JavaScript

About JavaScript Preprocessors

JavaScript preprocessors can help make authoring JavaScript easier and more convenient.

Learn more · Versions

Babel includes JSX processing.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

Powered by Algolia
About External Resources

You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.

If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.

You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.

Learn more

+ add another resource

Packages

Add Packages

Search for and use JavaScript packages from npm here. By selecting a package, an import statement will be added to the top of the JavaScript editor for this package.

Powered by Algolia
About Packages

Using packages here is powered by esm.sh, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ESM usage.

All packages are different, so refer to their docs for how they work.

If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.

Behavior

Auto Save

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.

HTML 

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

<head>
  <title>Markdown Technical Documentation</title>
</head>
<body>
  <nav id="navbar">
    <header id="navheader"><h1>Markdown Language</h1></header>
      <a class="nav-link" href='#introduction'>Introduction</a>
      <a class="nav-link" href='#bold_and_italic'>Bold and Italic</a>
      <a class="nav-link" href='#headings'>Headings</a>
      <a class="nav-link" href='#links'>Links</a>
      <a class="nav-link" href='#unordered_lists'>Unordered Lists</a>
  </nav>
  <main id="main-doc">
    <section class="main-section" id="introduction">
      <header><h2>Introduction</h2></header>
        <p>Markdown is a lightweight markup language with plain-text-formatting syntax. Its design allows it to be converted to many output formats, but the original tool by the same name only supports HTML.
        <p>Markdown is often used to format readme files, for writing messages in online discussion forums, and to create rich text using a plain text editor.</p>

        <p>Since the initial description of Markdown contained ambiguities and unanswered questions, the implementations that appeared over the years have subtle differences and many come with syntax extensions. </p>
      
      <p>There are various advantages of using Markdown, which includes</p>
      <ul>
        <li>Markdown provides semantic meaning</li>
        <li>You can write rich formatted content</li>
        <li>You can read markdown easily</li>
        <li>It doesn't interrupt</li>
        <li>It's Platform agnostic</li>
        
      </ul>
      
    </section>
    <section class="main-section" id="bold_and_italic">
      <header><h2>Bold and Italic</h2></header>
        <p>Probably the most basic components. Wrapping your text in * or ** or _ or _ _ will make it bold or italic. Observe: <p>

        <code><pre>
          Markdown is **cool** /*for bold

          Markdown is _really_ cool!! /*for italic

          Strike through is a ~~double tilda~~ 
      </pre></code>
    </section>
    <section class="main-section" id="headings">
      <header><h2>Headings</h2></header>
      <code><pre>
      # Is an H1 Heading

      ## Is an H2 Heading

      ### Is an H3.
      </pre></code>
      <p>Headings are automatically indexed in Github</p>
    </section>
    <section class="main-section" id="links">
      <header><h2>Links</h2></header>
        <p>Angle brackets makes it a clickable link;</p>
        <code><pre>
            &lt http://google.com &gt
        </pre></code>

        <p>Link text is inserted in square brackets and actual link following in parentheses.</p>

        <code><pre>
          [My Github](http://github.com/britsnj) 
         </pre></code>

        <p>Link text in square brackets and actual link following in parentheses. Hover text in double quotes inside the parentheses.</p>

        <code><pre>
          [FreeCodeCamp](http://freecodecamp.org "Great coding resource")
         </pre></code>
      

        <p>You can also use keys. For instance to link to [Nico's Blog][1] you can specify the key later in the document, and it will still link back. </p>

        <code><pre>
          [Nico's Blog][1]

          [1]: https://nicobrits.hashnode.dev
        </pre></code>

        <p>You also only need to specify the key once and wherever you use `[it][1]`,  [it][1] it will still link back to the key.</p>

        <p>Keys can be text or numbers.</p>
    </section>
    <section class="main-section" id="unordered_lists">
      <header><h2>Unordered Lists</h2></header>
        <p>Add * or - or + in front of list. </P

        <code><pre>
        * milk
        * egg
        * bread

        + milk
        + egg
        + bread

        - milk
        - egg
        - bread
        </pre></code>      
      </section>    
  </main>   
</body>
!

CSS 

              
                body{
    font-family: "Open Sans", Arial, sans-serif;
    color: #4d4e53;
    display: grid;
    grid-template-columns: 250px 10fr; 
  }

.nav-link{
  text-decoration: none;
  color: #4d4e53;
  font-size: 120%;
  border-top: #4d4e53 1px solid;
  padding: 20px 10px;
  
}

#navbar{
    position: fixed;
    border-right: #4d4e53 3px solid;
    display: flex;
    flex-direction: column;
    
  }

main{
  padding: 20px;
  grid-column-start: 2;
}

code{
  display: block;
  border-radius: 10px;
  background-color: lightgrey;
  margin: 10px;
  padding-top: 7px;
}

@media all and (max-width:815px){

  body{
    display: flex;
    flex-direction: column;
  }
  #navbar{
    position: relative;
    border-bottom: #4d4e53 3px solid;
  }
  .nav-link{
    font-size: 100%;
    padding: 10px;
  }

}
!

JS 

              
                // !! IMPORTANT README:

// You may add additional external JS and CSS as needed to complete the project, however the current external resource MUST remain in place for the tests to work. BABEL must also be left in place. 

/***********
INSTRUCTIONS:
  - Select the project you would 
    like to complete from the dropdown 
    menu.
  - Click the "RUN TESTS" button to
    run the tests against the blank 
    pen.
  - Click the "TESTS" button to see 
    the individual test cases. 
    (should all be failing at first)
  - Start coding! As you fulfill each
    test case, you will see them go   
    from red to green.
  - As you start to build out your 
    project, when tests are failing, 
    you should get helpful errors 
    along the way!
    ************/

// PLEASE NOTE: Adding global style rules using the * selector, or by adding rules to body {..} or html {..}, or to all elements within body or html, i.e. h1 {..}, has the potential to pollute the test suite's CSS. Try adding: * { color: red }, for a quick example!

// Once you have read the above messages, you can delete all comments.
!
999px

Console