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.
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.
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.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
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.
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).
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.
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.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
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.
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.
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.
Using packages here is powered by Skypack, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ES6 import
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.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
Visit your global Editor Settings.
<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>
<div id="main">
<div id="title">Amerigo Vespucci</div>
<div id="title2">"I resolved to abandon trade and to fix my aim on something more praiseworthy and stable; whence it was that I made preparation for going to see part of the world and its wonders."</div>
<div id="img-div">
<img id="image" class="thick-black-border" src="https://upload.wikimedia.org/wikipedia/commons/6/6f/Portrait_of_Amerigo_Vespucci.jpg" alt="Original portrait of Amerigo Vespucci holding a map. This portait is believed to be painted by Cristofano dell'Altissimo.">
<div id="img-caption">Original portrait of Amerigo Vespucci holding a map. This portait is believed to be painted by Cristofano dell'Altissimo.</div>
<div id="tribute-info">
<h1>Timeline of Amerigo Vespucci's Life:</h1>
<ul>
<li><strong class="strong">1454</strong> - Amerigo Vespucci is born in Firenze, Italy.</li>
<li><strong class="strong">1478</strong> - Amerigo travels to France with his uncle who educated and trained him in preparation for a career in business.</li>
<li><strong class="strong">1492</strong> - Amerigo travels to Spain to assist in preparing ships to set sail. He helped prepare Christopher Colombus' ships to sail to the New World.</li>
<li><strong class="strong">1499</strong> - After years of working with the ships, Amerigo departed with four ships on a voyage to the New World. They believed that their voyage would take them to the West Indies off the coast of Asia.</li>
<li><strong class="strong">1501</strong> - After returning to Spain and working for Portugal, Amerigo returns on a voyage to South America in order to explore Brazil and Argentina. This is also the time that Amerigo began to doubt that he was in the West Indes and began to suggest that the world may be much bigger than what they believed it to be.</li>
<li><strong class="strong">1502</strong> - On the return voyage from the New World, Amerigo studied the constellations and named a few. The <a target="_blank" href="https://www.space.com/29445-southern-cross-constellation-skywatching.html">Southern Cross</a> was named by him. Upon returning to Portugal, he presented his new beliefs and findings, saying that they had discovered a new continent between Europe and Asia. Thus this new land was named after him—America.</li>
<li><strong class="strong">1503</strong> - Amerigo's travels, detailing his exploration of Brazil, were published in a pamphlet.</li>
<li><strong class="strong">1508</strong> - Unlike Colombus, who is a controversial figure, Amerigo was a brave and intelligent explorer who earned his great reputation. Spain had to create a new position specifically for Amerigo, naming him the first 'chief navigator' for all subsequent voyages.</li>
<li><strong class="strong">1512</strong> - Sadly, four years after achieving the prestigious position of chief navigator, Amerigo died of malaria. Though his body has long turned to dust, his name has been immortalized. </li>
<li><strong class="strong">1538</strong> - Decades after his passing, a German mapmaker named <a target="_blank" href="https://en.wikipedia.org/wiki/Martin_Waldseem%C3%BCller">Martin Waldseemüller</a>, who had heard of Amerigo's travels, drew up a world map that included North and South America. It was called the <a target="_blank" href="https://en.wikipedia.org/wiki/Waldseem%C3%BCller_map"><em>"Universalis Cosmographia"</em></a></li>
</ul>
<div>
<p>Read more about the life of<a id="tribute-link" target="_blank" href="https://en.wikipedia.org/wiki/Amerigo_Vespucci"> Amerigo Vespucci</a>.</p>
</div>
<footer>
The information presented in this tribute can be found on the <cite><a href="https://www.softschools.com/">SoftSchools</a></cite> website, along with other interesting historical figures that may interest you.
</footer>
#main {
display: grid;
background-color: #353333;
border-color: black;
border-width: 15px;
border-style: solid;
}
#title {
margin: 10px 5px 5px 5px;
font-size: 30px;
font-weight: bold;
text-align: center;
color: #d1a111;
}
#title2 {
padding: 5px 100px 10px 100px;
margin: 10px 20px 10px 20px;
font-size: 15px;
font-style: italic;
color: #ffffff;
text-align: center;
}
#img-div {
display: flex;
flex-direction: column;
}
#image {
display: block;
max-width: 100%;
margin-left: auto;
margin-right: auto;
}
#img-caption {
margin: 5px 10px 10px 10px;
padding: 5px 5px 5px 20px;
color: #fff;
font-size: 12px;
text-align: center;
}
#tribute-info {
display: block;
color: #fff;
font-size: 18px;
text-align: justify;
padding: 0 15px 0 15px;
margin: 0 15px 0 15px;
}
.thick-black-border {
border-color: #d1a111;
border-width: 10px;
border-style: inset;
}
a {
color: #fff
}
a:hover {
color: blue;
}
h1 {
color: #d1a111;
font-size: 36px;
font-weight: bold;
text-align: center;
margin: 10px 15px 15px 15px;
padding: 20px 10px 20px 10px;
}
ul {
list-style-type: none;
padding: 10px 10px 10px 10px;
margin: 10px 10px 10px 10px;
border: 1px solid #d1a111
}
li {
padding-bottom: 20px;
}
.strong {
color: #d1a111
}
p {
display: block;
color: #d1a111;
font-size: 24px;
margin: 10px 10px 10px 10px;
padding: 10px 5px 10px 5px;
text-align: center;
}
footer {
display: block;
color: #fff;
font-size: 14px;
font-style: italic;
text-align: center;
margin: 15px 15px 15px 15px;
padding: 10px 10px 10px 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.
/***********
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.
Also see: Tab Triggers