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>
<html>
<head>
<title>Miss Rachel Rose's Portfolio</title>
</head>
<!--WELCOME TO MY WELCOME SECTION-->
<body>
<main>
<div id="welcome-section">
<h1>Rachel Rose</h1>
<p>web development, networking, technical writing</p>
<h1>May I show you around?</h1>
</div>
<!--HERE IS MY NAVBAR-->
<div>
<nav id="navbar">
<a class="nav-link" href="#about">about</a>
<br>
<a class="nav-link" href="#projects">projects</a>
<br>
<a class="nav-link" href="#contact">contact</a>
<br>
<a class="nav-link" href="#welcome-section">home</a>
</nav>
</div>
<!--HERE ARE THE TILES-->
<div id="project-container">
<div id ="projects">
<div class="project-tile">
<h2 class="header-two"><a href="https://www.alteayoga.es">Alteayoga</a></h2>
<br>
<p>Alteayoga is a project that I started in 2008, when I started yoga teacher training. Initially, I typed all my class notes straight into HTML and posted them. Later, I tried to get a little community started, posting various teachers' class times. Eventually, it just became my yoga web site. I have a Wordpress backend and recently updated the template. I have not finished it yet, because most people find me through social media or my Google page. I use the name "Alteayoga" on my Facebook, Twitter, Tumblr, YouTube and Instagram accounts. I have nearly a thousand followers, all told. Nothing too glamourous, but not bad for a DIY operation.</p>
</div>
<div class="project-tile">
<header><h2 class="header-two"><a href="https://www.rosetintyourlife.com">Rose Tint Your Life</a></h2></header>
<br>
<p>Rose Tint Your Life is a wellbeing concept project. The idea is "to see life through rose-tinted glasses". I am not into straight-up positivity. I am a realist, and, as a result, a very happy person. I think that the little things really count, and rose-tinting your life by eating well, resting, loving, playing, moving, singing and creating is the best way to make use of the little time we have here in this incarnation.</p> </div>
<div class="project-tile">
<header><h2 class="header-two"><a href="https://rachel-rose.net/">rachel-rose.net</a></h2></header>
<br>
<p>rachel-rose.net is my main domain for whatever I feel like posting. Over the years, I have used it for a bit of everything - music, massage, yoga, blogging, whatever. Right now, it is super simple, and I am putting my coding and my music on there, nothing else. It's my creative hub.
</p>
</div>
<div class="project-tile"><header><h2 class="header-two"><a href="https://codepen.io/missrachelrose/pen/RwRNaOV">Spanish tortilla</a></h2></header>
<br>
<p>This is a recipe that I wrote out for one of the FCC assignments. Da la vuelta a la tortilla, hombre. ¿Porque no?
</p>
</div>
</div>
</div>
<section class="main-section" id="about">
<header><h2 class="header-two">About Me</h2></header>
<p>I am Rachel and I love science and technology. Current challenge: the freeCodeCamp curriculum. Please check out my <a id="profile-link" target="_blank" href="https://www.freecodecamp.org/fccf1bc4abc-ad76-4e21-a401-9f76dea9d04c">FCC profile page</a>. I have also created a <a href="https://github.com/missrachelrose">GitHub profile</a>, but there's not much there...yet!</p>
<p>My University degree is in Applied Chemical and Biological Sciences. After graduation, I got swept up in the dot-com boom and bust, working in WANs and network security and web hosting. I re-trained in nutrition and physiotherapy, and spent 20 happy years helping people become whole and healed.</p>
<p>Now, however, <strong>I am back on the code again and wanting to get into UI/UX</strong>. UI/UX is a natural fit for me as my unique talent is easily straddling the strange divide between humans and the machines they build. Tech seems difficult to some only because of the frequent disconnect between coder and end-user. I can understand the coder because I am naturally smart, methodical and process oriented. But, having worked with thousands of very normal human beings on their healing journeys, I have a unique insight into the end-user. Central tenet: A computer only does what we tell it to do. We need to make it easy for end-users to tell the interface what they want.</p>
<p>People are frequently betrayed by their emotions. When faced with a frustrating technical interaction, whether at the bank or with a household appliance, the inability to control the interface shows up as shame. Shame is the hardest emotion to sit with because it is a very tender emotion. So, most people cover it up with anger. Behold, the angry end-user feared by all help desk people. This is where I see myself fitting in. I am no longer a snob about people's ability to adapt to an increasingly technological world. Nor am I under the illusion that coders have some over-arching worldview and all should conform.</p>
<p><strong>The truth lies somewhere in the middle, as always. For me, in tech, in 2020, that means UI/UX. Want to talk?</strong>
</p>
</section>
<section class="contact-section" id="contact">
<header>
<h2 class="header-two">How can I help your customers love your tech?</h2>
<p align="center">I would love to talk to you.</p>
</header>
</section>
<div class="contact">
<div class="project-tile"><a href="https://www.facebook.com/rachel.rose.564813">Facebook</a></div>
<div class="project-tile"><a href="https://github.com/missrachelrose">Github</a></div>
<div class="project-tile"><a href="https://twitter.com/missrvir">Twitter</a></div>
<div class="project-tile">email 📧 </div>
<div class="project-tile">Phone 📞</div>
</div>
</main>
</body>
</html>
body {
background-image: linear-gradient(to right, rosybrown, pink, navajowhite, cornsilk, navajowhite, pink, rosybrown);
font-family: avenir, futura;
color: black;
font-size: 12pt;
}
h1 {
font-size: 32pt;
}
a {
color: saddlebrown;
visited: deeppink;
}
div {
margin-top: 0px;
}
.header-two {
text-align: center;
}
.main-section {
max-width: 70%;
padding: 10%;
text-align: justify;
align: center;
}
.project-tile {
background-color: lightyellow;
border-style: solid;
border-width: 1px;
border-color: pink;
margin-right: 3%;
padding: 5%;
box-shadow: 0 10px 20px rgba(0,0,0,0.19), 0 6px 6px rgba(0,0,0,0.23);
}
.contact {
display: grid;
max-width: 75%;
padding-left: 20%;
grid-template-columns: 15% 15% 15% 15% 15%;
font-size: 10pt;
}
.contact-section {
padding-bottom: 1%;
}
#welcome-section {
height: 100vh;
}
@media (min-width: 400px){
#project-container{
grid-template-areas:
}
#projects {
height: auto;
max-width: 100%;
display: grid;
grid-template-columns: 25% 25% 25% 25%;
text-align: justify;
}
#welcome-section {
text-align: center;
margin-top: 25%;
}
#navbar {
position: fixed;
top: 0px;
right: 0;
width: 4em;
background: lavenderblush;
border-radius: 10%;
padding: 10px;
}
Also see: Tab Triggers