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

You're using npm packages, so we've auto-selected Babel for you here, which we require to process imports and make it all work. If you need to use a different JavaScript preprocessor, remove the packages in the npm tab.

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

Use npm Packages

We can make npm packages available for you to use in your JavaScript. We use webpack to prepare them and make them available to import. We'll also process your JavaScript with Babel.

⚠️ This feature can only be used by logged in users.

Code Indentation

     

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.

HTML Settings

Here you can Sed posuere consectetur est at lobortis. Donec ullamcorper nulla non metus auctor fringilla. Maecenas sed diam eget risus varius blandit sit amet non magna. Donec id elit non mi porta gravida at eget metus. Praesent commodo cursus magna, vel scelerisque nisl consectetur et.

            
              <ot-site>
  <ot-head>
    I render in head.
  </ot-head>
  <ot-menu>
    I render in menu.
  </ot-menu>
  <ot-body>
    I render in body.
  </ot-body>
</ot-site>

<!-- not registering custom elements in this demo -->
            
          
!
            
              // this red text color shows an example of content projection
ot-head, ot-menu, ot-body { color: red; }

// this red text color shows an example of style scoping
footer, #site footer { color: red; }

// this could set the footer to red if you un-comment it
// ot-site::shadow footer { color: red; }

            
          
!
            
              otSite.shadowRoot.innerHTML += `
  <style>
		/* due to content projection behavior
		   text color still red even if you try all of this: */

		ot-site,
		ot-head,
		ot-menu,
		ot-body,
		ot-site ot-head,
		ot-site ot-menu,
		ot-site ot-body,
		#site,
		#site header,
		#site header ot-head,
		#site menu,
		#site menu ot-menu,
		#site main,
		#site main ot-body { 
			color: #FFF !important; 
		}

		/* because the DOMs aren't "combined" */

		/* but this rule below can override it: */

		/*
		header ::content ot-head,
		nav ::content ot-menu,
		main ::content ot-body { color: #FFF; }
		*/

		/* because ::content allows us
		   to style the distributed nodes
		   but notice the footer rule from the light dom
		   doesn't affect the copyright from the shadow dom */
	</style>
`;
            
          
!
999px
🕑 One or more of the npm packages you are using needs to be built. You're the first person to ever need it! We're building it right now and your preview will start updating again when it's ready.

Console