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 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.
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.
<header>
<h1>The Minions</h1>
<p class="excerpt">Minions have been on this planet far longer than we have. They go by many names. Dave, Carl, Paul, Mike. Oh, that one is Norbert. He’s an idiot.</p>
</header>
<main>
<p class="intro">Just testing initial-letter demo with the Minions’ script. They’re all different, but they all share the same goal. To serve the most despicable master they could find. Boss! Making their master happy was the tribe’s very reason for existence. But that’s not to say that they didn’t have other passions. Huh?</p>
<p>Finding a boss was easy. But keeping a boss, therein lies the rub. Nope, it wasn’t easy for these guys. But they never gave up.</p>
<p>With the emergence of the Stone Age came the rise of a new species. Man was very different from the dinosaur. He was shorter, hairier, and way, way smarter.</p>
<p>The Minions took an instant liking to man, and helped him the best they could. Oh, no, no. Eh? Poor man. So trusting, so fragile. So, so delicious!</p>
<p>Their quest for a boss put the Minions front and center for some of civilization’s most historic moments. Anubis! Ancient Egypt held great promise. Okay! Pancake! But it didn’t last long. Hmm. Oh! Ow!</p>
<p>The Dark Ages were actually fun times. Their new master had a tendency to party all night and sleep all day. Ooh! Oh. But eventually, the party was over. They bounced from one evil boss to another, but they never seemed to find their perfect fit. One particular employer took their failure very, very badly. Huh? The Minions had no other choice but to keep moving. Oh.</p>
<p>And then, when all hope seemed lost, they found sanctuary. The Minions were safe! Years passed as the Minions forged their own civilization. They truly made a life for themselves. But something just wasn’t right. They felt empty inside. Without a master, they had no purpose. They became aimless and depressed. If this continued any longer, the Minions would perish.</p>
<p>But all was not lost for one Minion had a plan. His name was Kevin. He was excited to share
his idea with the tribe. He’d been preparing for days, weeks, months. But now he was ready.</p>
<p>Buddies! Kevin would leave the cave … go back to the outside world, and he would not return until he had found his tribe the biggest, baddest villain to serve. But he needed help.</p>
<p>Me! Bob was eager to go, but Kevin felt he was just not strong enough for the dangerous journey ahead.</p>
<p>Uh, no. Luckily, someone stepped up.</p>
<p>Stuart!</p>
<p>Huh? Me, me? Oh! Thank you.</p>
<p>Truth be told, Stuart had no idea what he was chosen for … but was thrilled it made people cheer for him. Thank you. Me!</p>
</main>
// Style to demo initial-letter
// ============================
$body-fontsize: calc(80% + 0.35vw);
$cap-fallback: calc(1100% + 0.35vw);
// fallback
.intro::first-letter {
// uncomment to have an easy way to check if it is working
//color: hsl(141, 68%, 51%);
// font-size: $cap-fallback;
// float: left;
// line-height: 1;
// nitpicky details to get unsupported first-letter to line up
// margin-top: .2rem;
// margin-left: -.5rem;
// if browser supports initial-letter
@supports (initial-letter: 7) or (-webkit-initial-letter: 7) {
-webkit-initial-letter: 7;
initial-letter: 7;
// only used to test if it is working. Color could be declared in the "fallback" or root of this selector instead
color: hsl(41, 68%, 51%);
// only webfonts work with initial-letter in Safari right now
font-family: 'Times New Roman', serif;
// unset fallbacks, not every property will need overrides.
margin-left: unset;
}
}
// Styles for fun
// ==============
main,
header {
margin: 0 auto;
max-width: 68vw;
}
main {
column-count: 2;
column-gap: 3vw;
}
.excerpt {
font-size: 1.3rem;
font-weight: 600;
line-height: 1.8;
margin: 0 0 1.5rem;
}
h1 {
font-size: 6.4rem;
font-weight: 200;
line-height: 1.1;
margin: 0 0 .4rem;
padding: 0;
}
p {
margin: 0 0 1.5rem;
padding: 0;
}
@import url('https://fonts.googleapis.com/css?family=Martel:200,600" rel="stylesheet');
body {
font-family: 'Martel', serif;
font-size: $body-fontsize;
font-weight: 200;
line-height: 2;
margin: 2rem auto;
padding: 2rem;
&:before {
background: linear-gradient(90deg, hsl(105, 0%, 100%) 0%, hsl(45, 100%, 70%) 35%, hsl(45, 100%, 70%) 65%, hsl(105, 0%, 100%) 100%);
text-transform: none;
}
}
Also see: Tab Triggers