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.
<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>
<div class="grid">
<nav id="navbar">
<header>Production of vinyl records</header><hr><hr>
<a class="nav-link" href="#Introduction">Introduction</a>
<a class="nav-link" href="#Mastering_material_requirements">Mastering material requirements</a>
<a class="nav-link" href="#Pressing_tools">Pressing tools</a>
<a class="nav-link" href="#Labels">Labels</a>
<a class="nav-link" href="#Completion_of_products">Completion of products</a>
</nav>
<main id="main-doc">
<section class="main-section" id="Introduction">
<header>Introduction</header>
<div class="h2">Recording times and choice of vinyl records</div>
<p>Each side of a record carries a spiral groove with 2 channels (stereo). The groove begins at the edge of the record and ends within a specified diameter from the centre, where the groove closes within itself. Any request involving a different geometrical
groove order needs to be specifically defined as a planned difference from the IEC 98 norm. </p>
<div class="h2">Mechanical parameters of vinyl</div>
<p>The measurements of vinyl records are based on the IEC 98 norm. Record dimensions 12“, 10“ and 7“ are valid for standard weight vinyl in the diagram below.</p>
</section>
<section class="main-section" id="Mastering_material_requirements">
<header>Mastering material requirements</header>
<p>Audio files</p>
<ul>
<li>WAV (Windows PCM) - uncompressed audio</li>
<li>AIF, AIFF (Apple Macintosh) - uncompressed audio</li>
<li>FLAC (Free Lossless Audio Codec) - lossless compression, including error detection </li>
<li>APE (Monkey's Audio) - lossless compression, including error detection</li>
</ul>
<p>Types of vinyl</p>
<div>Code</div>
<code>LP.30cm.RPM 331
/3.</code><br>
<code>MP.25cm.RPM 331.
/3</code><br>
<code>SP.17,5cm.RPM 45.</code><br>
<code>Maxi single.30cm.RPM 45.</code><br>
<code>EP. 17,5cm.RPM 331/3.</code><br>
</section>
<br>
<section class="main-section" id="Pressing_tools">
<header>Pressing tools</header>
<div class="h2">Supplied pressings instruments</div>
<p>GZ Digital Media can press using customer supplied material. GZ accepts lacquers or nickel metal works called father or mother or stampers. Metal works must be without any visible damage, cannot be soiled (stain on nickel metal works, etc) or showing
signs of corrosion. We recommend that all supplied metal works, especially lacquers (which are very sensitive) are packed carefully to avoid any damage during transport to GZ. Stampers have to be supplied as unprocessed originals and not bevelled.</p>
<p>GZ Digital Media is not responsible for the quality of records produced from customer supplied materials. Sound defects such as distortion, noise, etc. and defects caused by incorrect cuts (grooves) will not be accepted and all claims rejected.</p>
</section>
<section class="main-section" id="Labels">
<header>Labels</header>
<p>Records are usually labelled on both sides. Labels on vinyl records are made of paper material and are directly associated with the pressing of the vinyl. Labels are made from offset paper (140gsm paper for 10" and 12" and from 120gsm paper for
7”s), the customer can also choose to produce the records without labels or with labels only on one side.</p>
<p>Basic labels are produced in the following sizes:</p>
<ul>
<li> For 7“ records (17,5 cm) diameter ∅ 84 mm. </li>
<li>For 10“ and 12“ records (30 cm a 25 cm) diameter ∅ 100 mm.</li>
</ul>
</section>
<section class="main-section" id="Completion_of_products">
<header>Completion of products</header>
<p>The product is delivered in internal and external packaging (depending on the customer) and stored in sturdy cardboard boxes. The choice of packaging is specified in the customer order.</p>
<ul>
<li>Inner sleeve</li>
<li>Printed sleeves </li>
</ul>
<p>The outer packaging made in GZ Digital Media can be produced from:</p>
<code>white-grey or white-white
carton with a gsm of 280 – 350 g/m2.</code>
</section>
</main>
</div>
html,
body {
font-family: Tahoma, Geneva, sans-serif;
margin: 0;
padding: 0;
background: #ddd;
}
header {
font-size: 19px;
color: black;
letter-spacing: 0.1em;
font-weight: bold;
}
p {
font-size: 17px;
font-style: oblique;
}
code {
background-color: #ccc;
display: block;
padding: 10px;
}
.h2 {
font-size: 18px;
}
/* antras gridas neveikia tikriausiai, gal reik i divus sudet */
.grid {
display: grid;
grid-auto-columns: minmax(270px, auto) 1fr;
grid-template-areas: "nav main-doc";
grid-gap: 40px;
}
#navbar {
grid-area: nav;
position: fixed;
border-right: #333 2px solid;
background: white;
height: 100%;
}
#navbar > a {
padding: 10px;
color: black;
text-decoration: none;
border-bottom: #333 2px solid;
display: block;
}
a:hover {
background-color: #ddd;
}
#main-doc {
grid-area: main-doc;
background: #ddd;
padding: 10px;
}
@media screen and (max-width: 500px) {
#main-doc {
grid-template-columns: 1fr;
grid-template-areas: "nav" "main-doc";
}
#navbar {
width: 100%;
position: relative;
}
Also see: Tab Triggers