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.
<!--
excerpt from an article by Sam Mularczyk
found on medium.com
https://medium.com/coding-design/54e4688e4ee5
-->
<h1>Designing<br />in<br />Photoshop<br />sucks</h1>
<p><em>I’m not saying you can’t design in Photoshop. I certainly used to, and plenty of designers much more talented than myself do. But I’d argue that in 90% of cases, it’s not the best tool for the job. I’ll explain why.</em></p>
<hr>
<p>It’s incredibly common for web designers to use Photoshop as a tool to mock up sites. I get it. It’s quick, simple and visual… but also totally inaccurate.</p>
<p>By designing a web page in Photoshop, you’re creating a fixed-size image for a responsive, “retina-display” world. It’s not a true representation of what you’d actually see on the web. Animation, transitions, accurate/readable fonts and responsive design are all becoming essential in a mobile-focused landscape.</p>
<p>Sure, you can make a couple comps, mock up different breakpoints and so on — but that’s just making things super complicated.</p>
<p>Personally, I think it’s really important for web designers to <i>design in the browser</i>. Start with a sketch, flesh out all your ideas on paper then jump straight into code.</p>
<hr>
<p>I’ve been taking this approach for the last three or four years, and it really gives you an idea of what can actually be achieved with HTML & CSS. Clients also find a static web page much more impressive than an image, even if it’s super simple.</p>
<p>Sometimes you’ll see mockups and they’ll be impossible (or at least, very complicated) to implement. Web designers now, more than ever, need an in-depth understanding of their medium — otherwise you won’t be able to design effective, functional sites.</p>
<p class="etc">Read the full article on <a href="https://medium.com/coding-design/54e4688e4ee5">medium.com</a></p>
@import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700);
*, *:before, *:after {
margin:0;
padding:0;
-webkit-box-sizing:border-box;
-moz-box-sizing:border-box;
box-sizing:border-box;
}
body {
padding:3em 1em;
font-family: 'Ubuntu Mono', sans-serif;
line-height:1.6em;
color:white;
background:#00005a;
}
em {font-style:normal;font-size:1.2em;}
i {font-style:normal;color:#00ff77;}
h1, p, hr, .etc {
width:100%;
max-width:40rem;
margin:0 auto;
}
p {padding-bottom:1em;}
h1 {
position:relative;
padding:3rem 0 6rem 0;
font-size:3em;
line-height:1em;
font-weight:700;
text-transform:uppercase;
letter-spacing:5px;
}
h1:before {
content:'\3C\21\2013\2013';
position:absolute;
top:0;
left:0;
color:#00ff77;
}
h1:after {
content:'\2013\2013\3E';
position:absolute;
bottom:3rem;
left:0;
color:#fe0002;
}
hr {
position:relative;
padding:3rem 0;
border:none;
}
hr:before {
content:'\2044\2217\2013\2013\2013\2013\2013\2217\2044';
position:absolute;
top:1.2rem;
right:0;
left:0;
font-size:1.5em;
color:#0200fb;
text-align:center;
}
.etc {
position:relative;
padding:6rem 0 1rem 0;
text-align:center;
color:#fe0002;
}
.etc a {color:#fe0002;}
.etc:before {
content:'\2022';
position:absolute;
top:1rem;
left:50%;
color:white;
text-shadow:0 1rem 0 white,
0 2rem 0 white;
}
Also see: Tab Triggers