Pen Settings

CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URL's added here will be added as <link>s in order, and before the CSS in the editor. If you link to another Pen, it will include the CSS from that Pen. If the preprocessor matches, it will attempt to combine them before processing.

+ add another resource

You're using npm packages, so we've auto-selected Babel for you here, which we require to process imports and make it all work. If you need to use a different JavaScript preprocessor, remove the packages in the npm tab.

Add External Scripts/Pens

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.

+ add another resource

Use npm Packages

We can make npm packages available for you to use in your JavaScript. We use webpack to prepare them and make them available to import. We'll also process your JavaScript with Babel.

⚠️ This feature can only be used by logged in users.

Code Indentation

     

Save Automatically?

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

HTML Settings

Here you can Sed posuere consectetur est at lobortis. Donec ullamcorper nulla non metus auctor fringilla. Maecenas sed diam eget risus varius blandit sit amet non magna. Donec id elit non mi porta gravida at eget metus. Praesent commodo cursus magna, vel scelerisque nisl consectetur et.

            
              <html>
<head>
	<title>Sample Annotation Page: Basic Layout</title>
    
</head>
<body>
	<nav>
		<a href="#" >Home</a>
	</nav>
	<section>
		<article>
<p id="1">So, here is how we answered them:</p>
		<h3 id="2">How do we identify what comments were made on what paragraph?</h3> 
		<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>
		<h3 id="4">What if that paragraph or content is deleted?</h3>
		<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> 

		<h3 id="6">What if the author of the article wants to respond but only let the author of annotation know?</h3>
		<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> 
		</article>
	</section>
</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;



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: 60rem;
    }
    margin: 0 auto;
    line-height: 1.5;
    letter-spacing: 1px;
    font-size: 1.5rem;
    text-align: justify;
  }
}
            
          
!
999px
🕑 One or more of the npm packages you are using needs to be built. You're the first person to ever need it! We're building it right now and your preview will start updating again when it's ready.

Console