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.
<html>
<head>
<title>003: Mobile View: Expanded</title>
<link rel="stylesheet" href="css/003/styles.css"></link>
</head>
<body>
<nav>
<a href="#" >Home</a>
</nav>
<section>
<article id="commentable-container">
<div data-section="1" class="annotation--container clearfix">
<p id="1">So, here is how we answered them:</p>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech has-annotations"><p>15</p></h3>
<div class="comments-container">
<span class="comments-container--text">Lorem Ipsum </span>
<span class="comments-container--text">Your documentation source should be written as regular Markdown files,
and placed in a directory somewhere in your project.
Normally this directory will be named docs and will exist at the top level of your project,
alongside the mkdocs.yml configuration file. </span>
</div>
</div>
</div>
<div data-section="2" class="annotation--container clearfix">
<h3 id="2">How do we identify what comments were made on what paragraph?</h3>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech"><p>+</p></h3>
<div class="comments-container">
</div>
</div>
</div>
<div data-section="3" class="annotation--container clearfix">
<p id="3">We developed an engine in our content app, which assigns unique IDs to each content type on which annotations can be created by the
user before it is saved to the database.
For every article, these IDs start from 1. The obvious limitation being that the we cannot have annotations on a page where
more than one database entries are being displayed. I think that is okay, for annotations on blurb listing pages would be absurd for me.
Anytime the content gets updated, the previous IDs remain intact (unless the content is deleted). Even in the event of content deletion,
the ID is never reused (it is a linear list which constantly increments). The annotations are saved with keys to their article and its paragraph ID.
</p>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech"><p>+</p></h3>
<div class="comments-container">
</div>
</div>
</div>
<div data-section="4" class="annotation--container clearfix">
<h3 id="4">What if that paragraph or content is deleted?</h3>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech"><p>+</p></h3>
<div class="comments-container">
</div>
</div>
</div>
<div data-section="5" class="annotation--container clearfix">
<p id="5">The answer lies not in how we save annotations, but in how we display it. Annotations are displayed in two places on a page.
One is where they belong, on the margins of the text. Next, they are also collected down in a separate tab adjacent to the comments tab.
If there are some orphaned annotations, you can find them in this annotation bucket.
Plus, if you want to treat them as regular comments, so be it, they are here, at the bottom of the page.</p>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech"><p>+</p></h3>
<div class="comments-container">
</div>
</div>
</div>
<div data-section="6" class="annotation--container clearfix">
<h3 id="6">What if the author of the article wants to respond but only let the author of annotation know?</h3>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech"><p>+</p></h3>
<div class="comments-container">
</div>
</div>
</div>
<div data-section="6" class="annotation--container clearfix">
<p id="7">Since we have already proposed that we would want to maximize tunability of privacy in our projects, scalability of such flexibility is paramount.
But we have to make tradeoffs to make something work, and since we value your privacy more than anything,
we have found our answer in dealing with this problem outside the context of annotations.
But to understand the rationale of our solution, you will have to understand what annotations mean to us.
Annotations are personal interjections, or ponderings that happen while reading an article.
They are not exactly debatable, but can be a short feedback of sorts to authors, something said by a person to a person, and not broadcasted to everyone.
Thus, annotations that are aimed at starting conversations must result into conversations, but not on the post, but in the privacy of message boxes.
Say, a person made a public annotation on an article, and somebody wanted to respond to it. He can respond to it via a message.
This is possible rather easily because the other person too is a member (since annotations are for signed up users).
This can lead to great friendships and establishing novel social study circles while keeping the article relatively clean of the informal chatter that might then take place.
The concept of group messaging shall allow more people to join in the conversation should the two (original people in conversation) oblige unanimously.
Unanimous vote is required because even one person who does not oblige will be offended, and if that is so, we have a problem.
</p>
<div class="comments clearfix">
<h3 class="comments--toggle rectangular-speech has-annotations"><p>15</p></h3>
<div class="comments-container">
<span class="comments-container--text">Lorem Ipsum </span>
</div>
</div>
</div>
</article>
</section>
<script src="//code.jquery.com/jquery-1.10.2.js"></script>
<script src="//code.jquery.com/ui/1.11.2/jquery-ui.js"></script>
<!--
<script>
$(function() {
$( ".comments" ).accordion({
collapsible: true,
active: false
});
});
</script>
-->
</body>
</html>
//== Color Schemes
$text-color: rgb(33,33,33);
//== Media queries breakpoints
//
//## Define the breakpoints at which your layout will change, adapting to different screen sizes.
// Extra small screen / phone
//** Deprecated `$screen-xs` as of v3.0.1
$screen-xs: 480px !default;
//** Deprecated `$screen-xs-min` as of v3.2.0
$screen-xs-min: $screen-xs !default;
//** Deprecated `$screen-phone` as of v3.0.1
$screen-phone: $screen-xs-min !default;
// Small screen / tablet
//** Deprecated `$screen-sm` as of v3.0.1
$screen-sm: 768px !default;
$screen-sm-min: $screen-sm !default;
//** Deprecated `$screen-tablet` as of v3.0.1
$screen-tablet: $screen-sm-min !default;
// Medium screen / desktop
//** Deprecated `$screen-md` as of v3.0.1
$screen-md: 992px !default;
$screen-md-min: $screen-md !default;
//** Deprecated `$screen-desktop` as of v3.0.1
$screen-desktop: $screen-md-min !default;
// Large screen / wide desktop
//** Deprecated `$screen-lg` as of v3.0.1
$screen-lg: 1200px !default;
$screen-lg-min: $screen-lg !default;
//** Deprecated `$screen-lg-desktop` as of v3.0.1
$screen-lg-desktop: $screen-lg-min !default;
// So media queries don't overlap when required, provide a maximum
$screen-xs-max: ($screen-sm-min - 1) !default;
$screen-sm-max: ($screen-md-min - 1) !default;
$screen-md-max: ($screen-lg-min - 1) !default;
//Mixins
@mixin border-radius($x-radius: 0px, $y-radius: 0px ) {
-webkit-border-top-left-radius:$x-radius $y-radius;
-webkit-border-top-right-radius:$x-radius $y-radius;
-webkit-border-bottom-right-radius:$x-radius $y-radius;
-webkit-border-bottom-left-radius:$x-radius $y-radius;
//Escape
-moz-border-radius:#{$x-radius}/#{$y-radius};
-ms-border-radius:#{$x-radius}/#{$y-radius};
border-radius:#{$x-radius}/#{$y-radius};
}
@mixin border-bottom-right-radius($x-radius: 0px, $y-radius: 0px ){
-webkit-border-bottom-right-radius:$x-radius $y-radius;
-moz-border-radius-bottomright:$x-radius $y-radius;
-o-border-bottom-right-radius:$x-radius $y-radius;
border-bottom-right-radius:$x-radius $y-radius;
}
@mixin border-bottom-left-radius($x-radius: 0px, $y-radius: 0px ){
-webkit-border-bottom-left-radius:$x-radius $y-radius;
-moz-border-radius-bottomleft:$x-radius $y-radius;
-ms-border-radius-bottom-left:$x-radius $y-radius;
-o-border-bottom-left-radius:$x-radius $y-radius;
border-bottom-left-radius:$x-radius $y-radius;
}
// Background color gradient
// Color stops are not available in IE9 and below.
@mixin background-gradient($start-color: #555, $end-color: #333, $start-percent: 0%, $end-percent: 100%){
background:-webkit-gradient(linear, 0 $start-percent , 0 $end-percent, from( $start-color ), to( $end-color ));
background:-moz-linear-gradient($start-color, $end-color);
background:-o-linear-gradient($start-color, $end-color);
background:linear-gradient($start-color, $end-color);
background-repeat: repeat-x;
filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#{ie-hex-str($start-color)}', endColorstr='#{ie-hex-str($end-color)}', GradientType=1); // IE9 and down
}
@mixin transform-translate($x-transform: 0px, $y-transform:0px){
-webkit-transform:translate($x-transform, $y-transform);
-moz-transform:translate($x-transform, $y-transform);
-ms-transform:translate($x-transform, $y-transform);
-o-transform:translate($x-transform, $y-transform);
transform:translate($x-transform, $y-transform);
}
//CSS Styling
//--------------
html, body {
font-size: 14px;
margin: 0;
padding: 0;
width: 100%;
color: $text-color;
}
nav {
display: block;
background-color: smokescreen;
color: black;
box-shadow: 0 2px 3px 0 rgba(33,33,33,0.6);
}
section{
position: relative;
width: 100%;
@media(min-width: $screen-md){
width: 80%;
}
margin: 0 auto;
article{
width:95%;
@media(min-width: $screen-md){
width: 55rem;
}
margin: 0 auto;
line-height: 1.5;
letter-spacing: 1px;
font-size: 1.5rem;
text-align: justify;
.annotation--container{
position: relative;
width: 100%;
@media(min-width: $screen-md) and (max-width: $screen-lg){
transform: translate(-25rem,0);
transition: all 1s;
}
&>*{
position: relative;
display: block;
@media(min-width: $screen-md){
overflow: visible;
}
}
&>*:not(.comments){
padding-right: 60px;
}
.comments{
@media(min-width: $screen-md){
position: absolute;
max-width: 60px;
right: 0px;
top: 0;
z-index: 5;
}
&:focus, &:hover{
border: none;
}
.comments--toggle{
display:none;
position: absolute;
right: 0px;
top: -50%;
@media(min-width: $screen-md){
top: 20px;
left: 5px;
right: auto;
}
padding: 1px 3px;
margin:0;
background-color: rgba(228, 226, 226, 1);
//@include background-gradient(#dcdada, #dcdada);
border-color: rgba(228, 226, 226, 0.8);
&.has-annotations{
display:inline-block;
}
&:hover{
background-color: rgba(96, 148, 2, 1);
//@include background-gradient(#b8db29, #5a8f00);
border-color: rgba(96, 148, 2, 1);
}
/*
&:not([class*="has-annotations"]){
background-color: rgba(228, 226, 226, 0.8);
border-color: rgba(228, 226, 226, 0.8);
@include background-gradient(#dcdada, #dcdada);
}
*/
}
.comments--toggle__oval{
display: inline-block;
border-radius: 3px;
}
.comments--toggle__rectangle{
display: inline-block;
}
.comments-container{
padding: 0;
padding-left: 10%;
position: relative;
/* On larger screens, their widths are smaller, constrained*/
@media(min-width: $screen-md){
width: 30rem;
padding: 20px 0 0 40px;
}
color: lighten($text-color, 40%);
.comments-container--text{
display: block;
position: relative;
padding-top: 20px;
font-size: 1.2rem;
&:first-child{
padding-top: 5px;
}
}
}
}
}
}
}
#commentable-container{
.annotation--container:hover > .comments > .comments--toggle {
display: block;
}
}
.clearfix{
&:before, &:after{
content: " ";
display: table;
}
&:after{
clear: both;
}
}
/* ------------------------------------------
PURE CSS SPEECH BUBBLES
by Nicolas Gallagher
- http://nicolasgallagher.com/pure-css-speech-bubbles/
http://nicolasgallagher.com
https://twitter.com/necolas
Created: 02 March 2010
Version: 1.2 (03 March 2011)
Dual licensed under MIT and GNU GPLv2 Nicolas Gallagher
------------------------------------------ */
/* ============================================================================================================================
== OVAL SPEECH BUBBLE (more CSS3)
** ============================================================================================================================ */
.oval-speech {
position:relative;
min-width: 25px;
min-height: 20px;
width:auto;
padding: 0;
margin: 0;
text-align:center;
color:#fff;
background:#5a8f00;
border-color: inherit;
/* css3 */
@include background-gradient(#b8db29, #5a8f00);
@include border-radius(100%, 100%);
p {
font-size:0.5em;
margin:0;
padding:0 3px;
}
/* creates part of the curve */
&:before {
content:"";
position:absolute;
z-index:-1;
bottom:-7px;
right:50%;
background:inherit; /* need this for webkit - bug in handling of border-radius */
border: 7px solid;
border-color: inherit;
border-top: 7px solid transparent;
border-left: 7px solid transparent;
/* css3 */
@include border-bottom-right-radius(100%,100%);
/* using translate to avoid undesired appearance in CSS2.1-capabable but CSS3-incapable browsers */
@include transform-translate(0, -2px);
}
/* creates part of the curved pointy bit */
&:after {
content:"";
position:absolute;
z-index:-1;
bottom:-7px;
right:50%;
background:#fff;
border: 7px solid white;
border-top: 7px solid transparent;
border-left: 7px solid transparent;
/* css3 */
@include border-bottom-right-radius(100%,150%);
/* using translate to avoid undesired appearance in CSS2.1-capabable but CSS3-incapable browsers */
@include transform-translate(-50%, -2px);
}
}
.rectangular-speech{
position:relative;
min-width: 25px;
min-height: 20px;
width:auto;
padding: 0;
margin: 0;
z-index: 2;
text-align:center;
color:#fff;
background:inherit;
border-color: inherit;
/* css3 */
//@include background-gradient(#b8db29, #5a8f00);
@include border-radius(15%, 15%);
p {
font-size:0.5em;
margin:0;
padding:0 3px;
}
&:before {
content:"";
}
/* creates the triangle */
&:after {
content:"";
position:absolute;
z-index:-1;
bottom:-10px;
right:10%;
border: 10px solid;
border-color: inherit;
border-right: 10px solid transparent;
border-bottom: 10px solid transparent;
/* css3 */
/* using translate to avoid undesired appearance in CSS2.1-capabable but CSS3-incapable browsers */
@include transform-translate(0, -2px);
}
}
Also see: Tab Triggers