Pen Settings



CSS Base

Vendor Prefixing

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.

+ add another resource


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.

+ add another resource


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.


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.


                <script src=""></script>

  <title>Markdown Technical Documentation</title>
  <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>
  <main id="main-doc">
    <section class="main-section" id="introduction">
        <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>
        <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>
    <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>

          Markdown is **cool** /*for bold

          Markdown is _really_ cool!! /*for italic

          Strike through is a ~~double tilda~~ 
    <section class="main-section" id="headings">
      # Is an H1 Heading

      ## Is an H2 Heading

      ### Is an H3.
      <p>Headings are automatically indexed in Github</p>
    <section class="main-section" id="links">
        <p>Angle brackets makes it a clickable link;</p>
            &lt &gt

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

          [My Github]( 

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

          [FreeCodeCamp]( "Great coding resource")

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

          [Nico's Blog][1]


        <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 class="main-section" id="unordered_lists">
      <header><h2>Unordered Lists</h2></header>
        <p>Add * or - or + in front of list. </P

        * milk
        * egg
        * bread

        + milk
        + egg
        + bread

        - milk
        - egg
        - bread


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

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

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

  padding: 20px;
  grid-column-start: 2;

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

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

    display: flex;
    flex-direction: column;
    position: relative;
    border-bottom: #4d4e53 3px solid;
    font-size: 100%;
    padding: 10px;




                // !! 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. 

  - Select the project you would 
    like to complete from the dropdown 
  - Click the "RUN TESTS" button to
    run the tests against the blank 
  - 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.