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.
<header>
<h1>Elizabeth Yalkut</h1>
<h2>Front-End Developer</h2>
<section>
<p>I'm here to make the internet better: more accessible, tidier, and easier to navigate. I believe in creativity, code review, and compassion.</p>
<p><em>I'm not currently looking for a full-time position, and I am very limited in the number and scope of freelance projects I can take on. <strong>If you're a recruiter, please do not contact me.</strong></em></p>
</section>
<section>
<ul>
<li><i class="fas fa-envelope-open-text" aria-hidden="true"></i><a href="https://elizabethyalkut.wufoo.com/forms/contact-me/">Contact</a></li>
<li><i class="fa fa-home" aria-hidden="true"></i><a href="http://elizabethyalkut.com">Website</a></li>
<li class="print"><i class="fa fa-print" aria-hidden="true"></i><a href="javascript:window.print()">Print</a></li>
</ul>
</section>
</header>
<main>
<section>
<h2>Experience</h2>
<h3>Digital Scholarship Front-End Developer</h3>
<aside>
<p class="metadata employer">Center for Digital Scholarship, Brown University Library</p>
<p class="metadata">August 2022 - present</p>
<p class="job-description">Brown University’s digital scholarship hub, the Center for Digital Scholarship (CDS) provides expertise, services, and teaching in digital scholarship methodologies, project development, and publication.</p>
</aside>
<section>
<ul>
<li>Led front-end development on <a href="https://indigenousslavery.org/">Stolen Relations</a></li>
<li>Led UX research on<a href="https://library.brown.edu/create/cds/keeper-project/">The Keeper Project</a></li>
</ul>
</section>
<h3>Senior Front-End Developer</h3>
<aside>
<p class="metadata employer">Web and Advanced Research Platforms, Harvard Medical School</p>
<p class="metadata">July 2019 - August 2022</p>
<p class="job-description">The Web and Advanced Research Platforms team, in conjunction with the Office of Communications and External Relations (OCER), provides support for a wide array of HMS web properties, including the <a href="http://hms.harvard.edu">HMS flagship site</a>, department/center/core sites, and lab websites. Services offered include hosting for self-managed websites, design and development of websites to be hosted on one of our Drupal CMS platforms, and web consulting services.
</aside>
<section>
<ul>
<li>Served as team Senior Front-End Developer
<ul>
<li>Designed and developed dashboard of donor impact website</li>
<li>Enhanced functionality of Paragraph-based content components</li>
</ul>
</li>
<li>Oversaw portfolio of over 40 Drupal 8 and 9 sites, including hms.harvard.edu and all associated sites:
<ul>
<li>Increased SiteImprove accessibility score for hms.harvard.edu from 66.5/100 in 2019 to 92.5/100 in 2021, largely through theme improvements (e.g., improved link styles; semantic refactoring of templates)</li>
<li>Managed sprint deployments to Acquia platform</li>
</ul>
</li>
<li>Created custom Drupal 8 module to allow site editors to update text and links in an SVG</li>
<li>Created bash scripts to automate local development workflow</li>
<li>Mentored junior developer, including detailed review of pull requests and pair programming</li>
</ul>
</section>
<h3>Associate Web Developer</h3>
<aside>
<p class="metadata employer">Columbia College Information Technology, Columbia University</p>
<p class="metadata">April 2015 - July 2019</p>
<p class="job-description">
Columbia College Information Technology (CCIT) is responsible for the infrastructure, hardware, software, web publishing, online marketing, and software development and integration needs of the administrative offices of Columbia College.</p>
</aside>
<section>
<ul>
<li>Collaborated on or led development of:
<ul>
<li><a href="https://wellbeing.columbia.edu">Live Well | Learn Well</a> with University partners</li>
<li><a href="https://college.columbia.edu/campaign">Core to Commencement</a> campaign</li>
<li><a href="http://holder.college.columbia.edu">Holder Initiative</a></li>
<li><a href="ogp.columbia.edu">Office of Global Programs & Fellowships</a></li>
</ul>
</li>
<li>Led relaunch of the internal Human Resources Planning & Performance Tool, including collaborating on design, conducting user research and testing, developing Drupal 7 site, and training site</li>
<li>Maintained portfolio of approximately 26 Drupal 7 and 8 websites</li>
</ul>
</section>
<h3>Web Developer</h3>
<aside>
<p class="metadata employer">Databases & Web Initiatives, Office of Alumni and Development, Columbia University</p>
<p class="metadata">July 2012 - April 2015</p>
<p class="job-description">
The Databases & Web Initiatives team at the Office of Alumni and Development of Columbia University is responsible for maintenance and development of the donor database, as well as internal and external websites and applications.</p>
</aside>
<section>
<ul>
<li>Maintained the Columbia Alumni Association and Giving websites, both built in Drupal 6</li>
<li>Redesigned and redeveloped the internal Human Resources Planning & Performance Tool, including user testing, front- and back-end development, and user training</li>
<li>Led development of the Columbia Alumni Association Arts Access site, including managing a contractor</li>
<li>Implemented automated testing and documentation of front-end code</li>
</ul>
</section>
<h3>Front-End Developer</h3>
<aside>
<p class="metadata employer">Threespot Media</p>
<p class="metadata">October 2011 - June 2012</p>
<p class="job-description">
Threespot is an independent digital engagement agency that crafts experiences and connections between brands and consumers.</p>
</aside>
<section>
<ul>
<li>Served as front-end lead on relaunch of MacArthur Foundation website</li>
<li>Created CSS and HTML for relaunch of Brookings Institute website, as part of a five-person team</li>
</ul>
</section>
<h3>Developer</h3>
<aside>
<p class="metadata employer">Do Something</p>
<p class="metadata">June 2011 - September 2011</p>
<p class="job-description">
Do Something is a New York City not-for-profit dedicated to activating young people in their communities.</p>
</aside>
<section>
<ul>
<li>Conducted A/B testing to improve user conversion rates </li>
<li>Created individually branded microsites for campaigns </li>
</ul>
</section>
<!--<h3>Computing Fellow</h3>
<aside>
<p class="metadata employer">Barnard College Educational Technology</p>
<p class="metadata">September 2008 - May 2011</p>
<p class="job-description">
Computing Fellows at Barnard College Educational Technology help faculty and staff integrate technology into their teaching and learning. </p>
</aside>
<section>
<ul>
<li>Created podcasts introducing Internet law, social media, and user-generated content</li>
<li>Updated social media accounts, including Facebook and Twitter</li>
<li>Supported faculty and staff in use of software, including Office and Dreamweaver</li>
<li>Created, updated, and maintained PHP-based websites for academic departments</li>
</ul>
</section>-->
</section>
</main>
<section>
<h2>Education</h2>
<h3>Barnard College, Columbia University, Bachelor of Arts, History, May 2011</h3>
<p>I wrote my senior thesis on the development of intellectual property law in eighteenth-century England, with particular reference to gender.</p>
<p>Courses include: Statistics, Research Seminar in History, Public Speaking</p>
<h3>Emma Willard School, Diploma, June 2004</h3>
</section>
body {
background: url("https://s3-us-west-2.amazonaws.com/s.cdpn.io/181758/black-linen.png"),
rgba(0, 153, 102, 0.35);
max-width: 80vw;
margin: 0 auto;
font-family: "Josefin Sans", "Gill Sans", "Helvetica Neue", sans;
line-height: 1.6;
>* {
background-color: rgba(#fff, 0.7);
padding: 1rem;
}
}
/* generic typography */
h1,
h2,
h3 {
font-family: "Josefin Slab", serif;
}
h1,
h2 {
text-shadow: 2px 2px 3px rgba(255, 255, 255, 0.75);
margin: 0.25rem 0 0;
text-align: center;
}
a,
a[href] {
transition: all 0.5s ease;
color: #096;
border-bottom: solid 1px transparent;
text-decoration: none;
&:hover {
color: lighten(#096, 10%);
border-bottom-color: lighten(#096, 10%);
}
}
.fa,
.fab,
.far,
.fas,
i[class^="fa"] {
color: #096;
padding-right: 5px;
}
/* section specific */
/* header */
header {
display: grid;
grid-template-columns: 4fr 1fr;
grid-gap: 0 1.5rem;
h1,
h2 {
grid-column: 1 / -1;
}
}
/* experience */
main {
>section {
display: flex;
flex-wrap: wrap;
h2 {
flex-basis: 100%;
}
section {
flex-basis: 60%;
}
aside {
flex-basis: calc(40% - 1rem);
margin-right: 1rem;
}
}
h3 {
font-weight: 600;
font-variant: small-caps;
border-bottom: dashed 2px rgba(0, 153, 102, 0.35);
margin-top: 1rem;
margin-block-end: 0;
flex-basis: 100%;
}
}
ul {
header & {
list-style: none;
padding-left: 0;
}
}
p {
&.job-description {
font-size: small;
font-style: italic;
}
}
@media print {
body {
background: none;
width: auto;
font-size: 12pt;
line-height: 1.4;
}
a,
a[href] {
page-break-inside: avoid;
color: black;
border-bottom: solid 1px grey;
}
a[href^="http"]:after {
content: " <"attr(href) "> ";
border-bottom-width: none;
}
section {
padding: 0;
background-color: none;
}
ul {
padding-left: 1cm;
}
.fa,
.fab,
.fas,
.far,
.print {
display: none;
}
}
Also see: Tab Triggers