Pen Settings



CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URL's 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 it's URL and the proper URL extention.

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


Save Automatically?

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>


Hello Camper!

For now, the test suite only works in Chrome! Please read the README below in the JS Editor before beginning. Feel free to delete this message once you have read it. Good luck and Happy Coding! 

- The freeCodeCamp Team 


<meta name="viewport" content="width=device-width, initial-scale=1">
<nav id="navbar">
  <header id="header">.</header>
    <th><h3>Tutorial Website</h3></th>
    <th><a href="#"><img id="header-img" src=",f_auto,q_auto:eco/ikqra03zdnggljdu5vv0" alt="freecodecamp logo"></a></th>
  <p id="centered">Contents</p>
  <a href="#Introduction" class="nav-link">Introduction</a>
  <a href="#Prerequisties" class="nav-link">Prerequisties</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>
<main id="main-doc">
  <section class="main-section" id="Introduction">
        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

        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.
        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.
  <section class="main-section" id="Prerequisties">
          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.
          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.
         Desire to learn
         Ability To Handle This Thing Without Going Mad
         Desire To Induce An Existenstial Crisis
    <p>lorum iposum</p>
  <section class="main-section" id="JavaScript_and_Java">
    <header>JavaScript and Java</header>
    <p>lorum iposum </p>
  <section class="main-section" id="Hello_world">
    <header>Hello world</header>
      To get started with writing JavaScript, open the Scratchpad and write your
      first "Hello world" JavaScript code:
        >function greetMe(yourName) { alert("Hello " + yourName); }

      Select the code in the pad and hit Ctrl+R to watch it unfold in your
    <code>potatoes potatoes</code>
  <section class="main-section" id="Variables">
    <p>lorus iposum</p>
      You use variables as symbolic names for values in your application. The
      names of variables, called identifiers, conform to certain rules.
      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).
      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
      You can declare a variable in three ways:
        With the keyword var. For example, <code>var x = 42.</code> This syntax
        can be used to declare both local and global variables.
        By simply assigning it a value. For example, <code>x = 42.</code> This
        always declares a global variable. It generates a strict JavaScript
        warning. You shouldn't use this variant.
        With the keyword let. For example,<code> let y = 13.</code> This syntax
        can be used to declare a block scope local variable. See Variable scope



                html {
	scroll-behavior: smooth;
body {
  font-family: "Lato", sans-serif;

/**Navigation Bar Stuff**/
#navbar {
  height: 100%;
  width: 20vw;
  position: fixed;
  top: 0;
  left: 0;
  background-color: #111;
  text-align: center;
  padding-top: 20px;
  overflow-x: hidden

th {

#navbar h3 {
  font-size: 20px;
#navbar img {
  height: auto;
  border-style: solid;

#navbar a {
  padding: 6px 8px 6px 16px;
  text-decoration: none;
  font-size: 25px;
  color: #818181;
  display: block;

#navbar a:hover {
  color: #f1f1f1;
#centered {
  font-size: 25px;
  /** Adjust If You Want Later
  color: #818181;

/**Main Documentation Shenanigans**/
#main-doc {
  margin-left: 21vw;; /* Same as the width of the sidenav with some extra margin*/
  padding: 0px 10px;

#main-doc header {
  font-size: 2em;
code {
    background: #f4f4f4;
    border: 1px solid #ddd;
    border-left: 3px solid #f36d33;
    color: #666;
    page-break-inside: avoid;
    font-family: monospace;
    font-size: 15px;
    line-height: 1.6;
    margin-bottom: 1.6em;
    max-width: 100%;
    overflow: auto;
    padding: 1em 1.5em;
    display: block;
    word-wrap: break-word;

li {
  margin: 15px 0px 0px 20px;

/**Responsiveness & Media Queries**/

@media screen and (max-height: 450px)
  #navbar {left:0; top:0;}
  #navbar {padding-top: 15px;}
  #navbar a {font-size: 18px;}
@media screen and (max-width: 1600px) {
  #navbar {
  #main-doc {
@media screen and (max-width: 450px) {
  /**Make The Nav-bar Vertical Table**/


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