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.
-# Using some Haml for less typing :)
%p
Click anywhere on the grid to start, but the top right corner is the best spot. Then click each pink X to update the state of each cell and execute the algorithm. You will see
%a{ :href => "http://mathworld.wolfram.com/Rule110.html" } Rule 110
appear!
%div.a-machine
-# Cells per row * 23 b/c that's a good place to stop
- (1..897).each do
%input{type: "checkbox"}
%button.js-unchecker.u-margin-top
Uncheck all
//
// Welcome to the CSS encoding of the Elementary Cellular Automaton Rule 110!
//
// Here is a blog post explaining most of the concepts at play here:
// https://notlaura.com/is-css-turing-complete/
// Rule 110 is known to be Turing complete, so, this CodePen shows
// that CSS + user input + HTML are Turing complete!
// The holy trifecta of UI development we love dearly.
// A challenge! Can you fork this pen and encode Rule 126?
// http://mathworld.wolfram.com/ElementaryCellularAutomaton.html
// A more complex challenge! Can you figure out how to update the
// state of the cell without user input?
// Could we use the animation API and play states, perhaps?
// Or some completely different solution using CSS Grid?
// Okay, on to the code itself.
// First, some setup / Sass shortcut stuff that made it
// easier to work on this:
// Store custom property definitions in mixins for easier updating.
// (we'll be able to do this in CSS soon enough!)
@mixin zero {
--cell-bg-color: white;
--cell-num-color: black;
--cell-content: "0";
}
@mixin one {
--cell-bg-color: hotpink;
--cell-num-color: white;
--cell-content: "X";
--cell-cursor: pointer;
}
// Number of *s should be: var( --cells-per-row ) - 1.
// This means go to one cell before the one right below the current target.
// Using a Sass loop so we can update the cells per row in one place.
$CELLS_PER_ROW: 23;
$selector: "* ";
@for $i from 1 through ($CELLS_PER_ROW - 2) {
$selector: $selector "+ *";
}
//
// Rule 110 Encoding:
// 111 110 101 100 011 010 001 000
// 0 1 1 0 1 1 1 0
//
// $selector = 17 *s to target the cell directly below the targeted one
// 111
input:checked + input:checked + input:checked + #{$selector} {
@include zero;
}
// 110
input:checked + input:checked + input:not(:checked) + #{$selector} {
@include one;
}
// 101
input:checked + input:not(:checked) + input:checked + #{$selector} {
@include one;
}
// 100
input:checked + input:not(:checked) + input:not(:checked) + #{$selector} {
@include zero;
}
// 011
input:not(:checked) + input:checked + input:checked + #{$selector} {
@include one;
}
// 010
input:not(:checked) + input:checked + input:not(:checked) + #{$selector} {
@include one;
}
// 001
input:not(:checked) + input:not(:checked) + input:checked + #{$selector} {
@include one;
}
// 000
input:not(:checked) + input:not(:checked) + input:not(:checked) + #{$selector} {
@include zero;
}
//
// UI setup - not relevant to the automaton logic.
//
body {
font-family: Helvetica;
}
// Set up the custom properties
:root {
--cell-content: "";
--cell-bg-color: white;
--cell-num-color: black;
--cell-cursor: initial;
--cell-size: 30px;
--cells-per-row: #{$CELLS_PER_ROW};
}
// Configuration previous row checked items.
input:checked::before {
--cell-bg-color: black;
--cell-cursor: initial;
--cell-num-color: white;
--cell-content: "1";
}
input:not(:checked) {
@include zero;
}
// Scaffold number indicator pattern
input::before {
width: 100%;
height: 100%;
position: absolute;
display: grid;
place-content: center;
background-color: var(--cell-bg-color);
color: var(--cell-num-color);
content: var(--cell-content);
cursor: var(--cell-cursor);
}
.a-machine {
display: flex;
flex-wrap: wrap;
width: calc(var(--cell-size) * var(--cells-per-row));
// Cutting this off so it looks nice :)
height: calc(var(--cell-size) * 21);
overflow: hidden;
}
input {
-webkit-appearance: none;
border: 1px solid black;
height: var(--cell-size);
width: var(--cell-size);
font-size: 1rem;
margin: 0;
position: relative;
}
// Utilities
.u-margin-top {
margin-top: 1rem;
}
const cells = document.querySelectorAll( 'input[type="checkbox"]' );
const uncheckerBtn = document.querySelector( '.js-unchecker' );
uncheckerBtn.addEventListener( 'click', function( e ) {
cells.forEach( ( cell ) => {
cell.checked = false;
});
});
Also see: Tab Triggers