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.
// use the default "full" mode - not the "fit" mode many of the codepens use
// full mode makes a full window stage without any automatic scaling
// the objects then must be manually scaled in the Frame's resize event
const frame = new Frame({color:darker, outerColor:darker});
frame.on("ready", ()=>{ // ES6 Arrow Function - similar to function(){}
zog("ready from ZIM Frame"); // logs in console (F12 - choose console)
// often need below - so consider it part of the template
let stage = frame.stage;
let stageW = frame.width;
let stageH = frame.height;
// REFERENCES for ZIM at https://zimjs.com
// see https://zimjs.com/intro.html for an intro example
// see https://zimjs.com/learn.html for video and code tutorials
// see https://zimjs.com/docs.html for documentation
// CODE HERE
// this is basic responsive using percentages of the stageW and stageH
// these can be used with scaleTo(), sca(), pos()
// or properties (but without chaining) scale, scaleX, scaleY, x, y
// There will be more advanced examples using the ZIM Layout() class as well
// use a grid to help visualize percentages - see docs for more options
const grid = new Grid({color:dark}); // or put last to go on top
// make some assets to position or scale in the resize event later
const a = new Rectangle(100,100,green).centerReg();
const b = new Rectangle(100,100,blue).centerReg();
const c = new Rectangle(100,100,orange).centerReg();
const d = new Rectangle(100,100,pink).centerReg();
const circle = new Circle(100, red);
const title = new Label({
text:"ZIM - Responsive Canvas: position and scale - press to toggle",
color:white
}).alp(.7).addTo();
// mousedown on the stage:
// here we have provided a way to toggle the the grid and outline
// normally, as you build you would put them in to see what is happening
// and then comment them out or remove them when done
// so all this code is really just for this demonstration
// note we use "stagemousedown" to capture a mousedown anywhere on the stage
// there is just "mousedown" which only captures events on any object on the stage
stage.on("stagemousedown", ()=>{
if (stage.contains(grid)) {
grid.removeFrom();
outlineSize=0
} else {
grid.addTo(stage, 0);
outlineSize=2;
}
resize();
stage.update();
});
let outlineSize = 2;
// here is the frame resize event (same as window.addEventListener("resize", ()=>{}))
frame.on("resize", resize);
function resize() {
// grab the new stage width and height
stageW = frame.width;
stageH = frame.height;
// scaleTo defaults to scale to the "smallest" of 30% height or 30% width
// can also scale to the "largest" or "both" - this last one would stretch the object
circle.scaleTo(stage, 30, 30).center().outline(purple, outlineSize);
// keep center rectangles at 20% horizontal and 30% vertical margin
// note the rectangles are center registration so this is to their centers
// the outline shows the registration point as a circle
// once again, the outline is only for helping see what is happening
// you would remove the outline and the grid for the final app
// normally, outline can be done just obj.outline();
// we just wanted purple and the ability to toggle the outline with its size parameter
a.loc(stageW*.2, stageH*.3).outline(purple, outlineSize);
b.loc(stageW*.8, stageH*.3).outline(purple, outlineSize);
c.loc(stageW*.8, stageH*.7).outline(purple, outlineSize);
d.loc(stageW*.2, stageH*.7).outline(purple, outlineSize);
// scale the title to 50% the width
// position title at 5% margin left and top
title.scaleTo(stage, 50);
title.pos(stageW*.05, stageH*.05);
grid.resize();
}
stage.update(); // this is needed to show any changes
// DOCS FOR ITEMS USED
// http://zimjs.com/docs.html?item=grid
// http://zimjs.com/docs.html?item=rectangle
// http://zimjs.com/docs.html?item=circle
// http://zimjs.com/docs.html?item=centerReg
// http://zimjs.com/docs.html?item=center
// http://zimjs.com/docs.html?item=scaleTo
// http://zimjs.com/docs.html?item=outline
// http://zimjs.com/docs.html?item=pos
// http://zimjs.com/docs.html?item=addTo
// http://zimjs.com/docs.html?item=frame
}); // end of ready
Also see: Tab Triggers