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.
<h1>CSS only priority navigation</h1>
<p>Resize this window and watch the navigation adapt to available space. <strong>No JS</strong>. <strong>Only CSS</strong>. A pen by <a href="https://codepen.io/olach">Ola</a>.</p>
<nav id="menu">
<ul id="menu-closed">
<li><a href="#">Start</a></li>
<li><a href="#">Events</a></li>
<li><a href="#">Calendar</a></li>
<li><a href="#">Portfolio</a></li>
<li><a href="#">Blog</a></li>
<li><a href="#">Products</a></li>
<li><a href="#">Things</a></li>
<li><a href="#">About</a></li>
<li><a href="#">Contact</a></li>
<li><a href="#">Login</a></li>
<li><a href="#menu-closed">× Close menu</a></li>
<li><a href="#menu">☰ Menu</a></li>
</ul>
</nav>
<p>A quick note on how this works. Nothing special is used, only inline-blocks, absolute positioning, max-height and overflow hidden. Therefore, this technique should work in all browsers.</p>
<p>The menu button is the last menu item. This item is placed above the navigation, and is hidden because the nav has overflow hidden applied. The rest of the menu items is styled with inline-block and placed in a row. If the window is so small that not all menu items can fit, they wrap into a second row, but is not shown, because of overflow hidden on the nav.</p>
<p>But how is the menu button now magically shown? Remember that the last menu item, the menu button, is positioned with position absolute? It is positioned from the bottom of the ul tag, and moved upwards with the same height as the nav. The menu button is in other words moved when the height of the ul tag is changed. Since the items now are in two rows, the height of the ul tag is now twice of the original height. The menu button will therefore automatically move down one step (the height of the nav) into view.</p>
<p>But, if the menu items occupy three or more rows, we need to prevent the menu button to move another step down out of view below the nav. This is solved by setting a max-height to the ul tag, with a value of double the height of the nav.</p>
<p>The opening and closing of the menu is done with simple anchor links, and the use of the :target selector in css.</p>
<p>So, a simple but effective technique using only CSS. Only downside is that you have to set an explicit height size on the nav, and this fixed height value has to be applied several times in the CSS.</p>
body {
font-family: Helvetica, Arial, sans-serif;
background-color: rgb(236, 236, 236);
margin: 1em;
color: rgb(19, 51, 61);
}
p {
font-size: 18px;
line-height: 1.5;
font-weight: bold;
color: rgb(51, 51, 51);
max-width: 55em;
}
p a {
color: rgb(41, 183, 206);
text-decoration: none;
}
strong {
color: rgb(41, 183, 206);
}
nav {
font-size: 12px;
background-color: rgb(19, 51, 61);
box-shadow: 0 1px 2px rgba(19, 51, 61, 0.5);
margin: 3em 0 6em;
padding: 0 1em;
height: 44px; /* Menu height */
overflow: hidden; /* Don't show anything outside the nav */
}
nav ul {
margin: 0;
padding: 0;
list-style-type: none;
max-height: 88px; /* Menu height x 2 */
position: relative; /* Position the menu button relative to this item */
}
nav li {
display: inline-block;
}
nav a {
display: inline-block;
padding: 0 1em;
color: rgb(236, 236, 236);
font-weight: 700;
letter-spacing: 0.1em;
text-decoration: none;
text-transform: uppercase;
white-space: nowrap;
line-height: 44px; /* Menu height */
height: 44px; /* Menu height */
}
nav a:hover {
background-color: rgba(255, 255, 255, 0.08);
}
nav li:last-child { /* The menu button */
position: absolute; /* Move the menu button out of flow */
right: 0;
bottom: 44px; /* Move upwards, the same distance as the menu height */
background-image: linear-gradient(to right, rgba(19, 51, 61, 0) 0, rgba(19, 51, 61, 1) 2em);
padding-left: 3em;
}
nav li:nth-last-child(2) { /* The close button */
display: none;
}
nav#menu:target {
height: auto;
padding: 0;
}
nav#menu:target ul {
max-height: none;
}
nav#menu:target li {
display: block;
}
nav#menu:target a {
display: block;
padding: 0 2em;
background-color: rgba(255, 255, 255, 0.05);
}
nav#menu:target a:hover {
background-color: rgba(255, 255, 255, 0.08);
}
nav#menu:target li:not(:first-child) {
margin-top: 2px;
}
nav#menu:target li:last-child {
display: none;
}
nav#menu:target li:nth-last-child(2) {
display: inline-block;
position: absolute;
top: 0;
right: 0;
margin: 0;
border-left: 2px solid rgb(19, 51, 61);
}
/* No JS needed :) */
Also see: Tab Triggers