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 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.
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.
<div>Hover me to see the magic happen</div>
/*
General styling. Ignore this.
*/
body{
font-family:Ubuntu, sans-serif;
padding:20px;
}
*{box-sizing:border-box}
/*
DISCLAIMER:
I'm chaining a hefty chunk of properties, so I
decided to format them for readability. I haven't tested
this in anything other than Chrome so other browsers may
have trouble parsing the property this way. You have been
warned.
This is the initial state of our element. Compare all
of the properties here with the properties on the :hover
state but skip the transition property for now. Read the
comment above the :hover state, then come back here.
* Did you read the comment over the :hover state? I'll bet
* you're lying. Oh well, you're the one that will fail
* miserably and ultimately throw yourself into a volcano
* because you can't stand to face your own shame.
* Carry on:
The only major difference between the :hover state and the
initial state in a transition chain is that you'll reverse
the delays. Unfortunately, it's not as simple as flipping the
delay column. Start from the bottom and add up the delays the
same way you did with the :hover state. You'll likely have
different numbers. This is normal.
Now check out the transition chain documentation template at
the bottom for your freebie. ;-)
*/
div{
background-color:transparent;
border:0 solid #000;
border-left-width:0;
border-radius:2px;
border-right-width:0;
cursor:pointer;
display:block;
margin:0 auto;
max-height:200px;
padding-bottom:20px;
padding-top:20px;
text-align:center;
transform:rotate(0);
transition:
/* property duration delay */
border-left 1.0s 2.0s,
border-right 1.0s 2.0s,
-webkit-transform 0.5s 1.5s,
padding-bottom 1.0s 0.5s,
padding-top 1.0s 0.5s,
background-color 0.5s 0.0s;
}
/*
When chaining a bunch of transitions, I always start with
the secondary state (:hover, :focus, :active, etc) since
the transition property here actually controls the first
half of our full transition.
Wait, what? Shouldn't it control the second half? Let me
explain. The transition property on a selector sets the
INCOMING animation for that selector. For example, setting
a delay on the :hover state means that the delay will happen
when you move your cursor OVER the element. Setting the delay
on the initial state will cause the delay to occur when you
move your cursor AWAY from the element.
Now that's out of the way, let's look at the transition
property. I always sort my transition properties in the
order that they'll be activated. Transitions that will be
activated simultaneously are sorted alphabetically, making
it a lot easier to read.
Once I've typed in my properties, I'll start setting the
duration and the delay for each of them. Make sure you
always set delay values on chained properties, even if the
delay is zero. Otherwise the browser may have trouble parsing
the transition between the delay and non-delay versions.
The easiest way to chain transitions is to have them happen
in immediate sequence, or one right after the other. To do
this, set each delay to the sum of the previous property's
duration and delay. Here's the maths:
* Previous Property: padding-bottom/-top
duration + delay = newDelay
1.0s + 1.5s = 2.5s
You can get a lot fancier, adding transitions in the middle
of each other or overlapping transitions but that's all
beyond the scope of this pen.
Something else to take notice of is that I'm using
border-left/-right and padding-bottom/-top. This is because if
I want to, I can now transition the vertical/horizontal
versions of these properties individually. Also, some shorthand
properties will give you grief with transitions, like background.
You'll want to use the longhand properties if you plan on
transitioning these.
One final thing to note is that when chaining transitions,
prefixed properties can break your entire chain. This chain uses
-webkit-transform because I do most of my work in Chrome.
However, if I change the prefix to -moz- and open it in Chrome,
it will break the ENTIRE TRANSITION. I'm sure this is a bug but
I'll be investigating a bit further and filing a bug report later
if necessary.
* NOW you should go back to the first comment.
*/
div:hover{
background-color:#ccc;
border-left-width:20px;
border-right-width:20px;
padding-bottom:100px;
padding-top:100px;
text-align:center;
transform:rotate(360deg);
transition:
/* property duration delay */
border-left 1.0s 0.0s,
border-right 1.0s 0.0s,
-webkit-transform 0.5s 1.0s,
padding-bottom 1.0s 1.5s,
padding-top 1.0s 1.5s,
background-color 0.5s 2.5s;
}
/*
This is just a little transition chain documentation I came up
with to help keep track of your properties. Set the number on
the timeline, then list the properties to which it corresponds
in the list below.
*/
/* Timeline
****************************************************************************************************
01------------------02--------------------------------------03------------------04------------------
0.0s 0.5s 1.0s 1.5s 2.0s
****************************************************************************************************
01 border-left
border-right
----------------------------------------------------------------------------------------------------
02 transform
----------------------------------------------------------------------------------------------------
03 padding-bottom
padding-top
----------------------------------------------------------------------------------------------------
04 background-color
----------------------------------------------------------------------------------------------------
*/
Also see: Tab Triggers