Pen Settings



CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

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.

+ add another resource


Babel includes JSX processing.

Add External Scripts/Pens

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.

+ add another resource


Add Packages

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.


Save Automatically?

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.


                <!--Pattern HTML-->
  <div id="pattern" class="pattern">
  	<!--Begin Pattern HTML-->
		<ul class="navigation" role="navigation">
			<li><a href="#">Home</a></li>
			<li><a href="#">About</a></li>
			<li><a href="#">Products</a></li>
			<li><a href="#">Services</a></li>
			<li><a href="#">Contact</a></li>
	<!--End Pattern HTML-->
	<div class="container">	
		<section class="pattern-description">
			<h1>Top Links</h1>
      <p>From <a href="">Responsive Navigation Patterns</a>:</p>
			<p>One of the easiest-to-implement solutions for navigation is to simply keep it at the top. Because of its ease of implementation, it's found on many (maybe even most) responsive sites right now.</p>
			<li><strong>Easy to implement</strong>- you can implement your large-screen site almost as-is.</li>
			<li><strong>No Javascript dependencies</strong> &mdash; ensuring maximum compatibility</li>
			<li><strong>No back-breaking CSS maneuvers required</strong></li>
			<li><strong>No tripping over your source order</strong> &mdash; no need to jump through hoops to shift nav lists around in the source. It flows au naturel.</li>
			<li><strong>Height issues</strong>- <a href="">Height matters in mobile</a>. As <a href="">Luke's book</a> explains, content-first, nav-second is preferred for mobile web experiences. You want to get the users to the meat-and-potatoes content as quickly as possible. That means getting the navigation out of user's way so they can focus on the core information on the page. It can also be confusing when all the core content is cut off</li>
			<li><strong>Not scalable</strong> &mdash; What happens when you want to add a new section to your site? Where the nav fits neatly on one line now, what happens when your client says you need to add "products and services" to the nav? Or when you need to translate the menu to German?</li>
			<li><strong>Fat Fingers</strong> &mdash; Cramming links too closely together can easily result in unwanted proximity clicks</li>
			<li><strong>Cross-device issues</strong> &mdash; While text might look great on an iPhone, devices have different ways of rendering fonts. Sites can look great on an iPhone but break when viewed on other platforms:</li>
		<footer role="contentinfo">   
				<nav id="menu">
					<a href="">&larr;More Responsive Patterns</a>


                .navigation li {
  		display: inline-block;
			margin: 0 0.5em;
		.navigation li a {
			display: block;
			padding: 1em 0.5em;