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. If you link to another Pen, it will include the CSS from that Pen. If the preprocessor matches, it will attempt to combine them before processing.
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.
If the stylesheet 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 CSS 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.
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.
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<title>Display Property Example</title>
</head>
<body>
<p id="p1">This is paragraph p1.</p>
<p class="p2">This is paragraph p2.</p>
<p class="p3">This is paragraph p3.</p>
<hr />
<div class="ex4">
<i class="i1">Go</i> <i class="i2">Badgers!</i> <i class="i3">go!</i>
</div>
</body>
</html>
body {
font-size: 200%; /* just making the type easier to see */
}
#p1 {
background-color: rgba(255, 0, 0, .3);
color:white;
}
.p2 {
background-color: rgba(0, 255, 0, .3);
}
.p3 {
background-color: rgba(0, 0, 255, .3);
}
.i1 {
background-color: rgba(255, 55, 0, .9);
}
.i2 {
background-color: rgba(0, 255, 0, .6);
}
.i3 {
background-color: rgba(0, 0, 255, .7);
}
//Complete this during class, recording your observations with your partner.
//Look over the HTML and CSS of the example. Describe what you see.
//Use the web inspector to change the display property of the first paragraph to inline. Describe what you see.
//Change the second paragraph to inline. Describe what you see.
//Now change the third. Describe what you see.
//Describe why the paragraphs changed.
//Reload your page!!
//Using the web inspector, add a rule using p as the selector. Set it to display: inline-block. Any change?
//Look at the second section, Go bear, go!. Why is this section displaying in a line?
//Use the web inspector to change the display property of the first i to block. What happened?
//For your assignment mark up in HTML, add a CSS stylesheet and a full head tag with the responsive viewport tag.
//style this example anyway you like - take notice how I used rgba - a is the alpha channel and controls opacity. play with it!
//Add navigation to three empty links.
//Notice the use of classes used in this example.
//Explain in a new <div> the reason to use IDs and classes.
//Upload to your Week 23 folder.
Also see: Tab Triggers