Typeplate is a “typographic starter kit”. We don’t make aesthetic design choices, but define proper markup with extensible styling for common typographic patterns. A stripped-down Sass or CSS library of your choosing primarily concerned with the appropriate technical implementation of design patterns—not how they look.

Frameworks make decisions for you about how to organize, structure and design a site. Pattern libraries don’t separate styling and markup, making them tough to use in a truly modular fashion. We weren’t satisfied, so we made a thing that doesn’t do that.

§ 1.1 Base Type For a solid base we use default font settings to allow elements to display in their natural size determined by the browser's default stylesheet. This makes for lighter CSS and more flexibility in the markup you choose to use. We also ensure unit values for line-heights are never used per the recommendations of Eric Meyer.

§ 1.2 Typographic Scale Establish clearly distinguishable heading levels with consistent font-sizes over randomly chosen values. Choose a type hierarchy that is harmonious and consistent with your project. In order to do so we suggest using a modular scale that calculates sizes via a ratio ensuring your design and typography can relate in a meaningful way. There’s an excellent calculator for this at modularscale.com. By using culturally relevant, historically pleasing ratios to create modular scales and basing the measurements in our compositions on values from those scales, we can achieve a visual harmony not found in layouts that use arbitrary, conventional, or easily divisible numbers. Tim Brown Heading Giga Heading Mega Heading Alpha Heading Beta Heading Gamma Heading Delta Heading Epsilon Heading Zeta

§ 1.3 Color Just like in print, don’t use the darkest black available in your body text ( #000 ). Instead, go for something softer, like #444 . You can use a slightly darker color for titles like ( #222 ) for example. Since these values are considered a de facto standard in practice, they're not necessarily ordained by law. #000

#222

#444

§ 1.4 Word-Wrap The word-wrap CSS property is used to specify whether or not, the browser may break lines within words in order to prevent overflow when an otherwise unbreakable string is too long to fit in its containing box. Lorem ipsum dolor sit amet, consectetur adipisicing elit. Odio iste voluptates saepe ipsa magni repellendus explicabo numquam expedita dolore eveniet accusantium iure sit consequatur? Dolore minus vel blanditiis velit deserunt! We’ll also be checking a few things like the longest word in the world “Methionylthreonylthreonylglutaminylarginylisoleucine” and other stuff like links that are way long such as “Methionylthreonylthreonylglutaminylarginylisoleucine” and other long links like http://192.168.1.100/somedirectory/stayout/of/my/shit

§ 2.1 Indenting On the web, paragraphs are commonly set in blocks, with top and bottom margins. Historically, paragraphs are set using indentation, which makes it easier to scan long-form text and are (we think) more conducive to readability. For the curious, here's a few example sites using the paragraph indentation approach we've chosen for our starter kit…Mark Boulton, Nice Web Type, Andy Rutledge and Nathan Ford just to name a few. Authors choosing to opt out of our default styling may feel free to change the boolean variable in the Sass port to remove this opinionated default as depicted in the example below. CSS people you'll have to settle for the manual route to customize. I crawled out almost immediately, and crouched, my feet still in the water, under a clump of furze. The horse lay motionless (his neck was broken, poor brute!) and by the lightning flashes I saw the black bulk of the overturned dog cart and the silhouette of the wheel still spinning slowly. In another moment the colossal mechanism went striding by me, and passed uphill towards Pyrford. Seen nearer, the Thing was incredibly strange, for it was no mere insensate machine driving on its way. Machine it was, with a ringing metallic pace, and long, flexible, glittering tentacles (one of which gripped a young pine tree) swinging and rattling about its strange body. It picked its road as it went striding along, and the brazen hood that surmounted it moved to and fro with the inevitable suggestion of a head looking about. Behind the main body was a huge mass of white metal like a gigantic fisherman’s basket, and puffs of green smoke squirted out from the joints of the limbs as the monster swept by me. And in an instant it was gone. So much I saw then, all vaguely for the flickering of the lightning, in blinding highlights and dense black shadows. As it passed it set up an exultant deafening howl that drowned the thunder—“Aloo! Aloo!”—and in another minute it was with its companion, half a mile away, stooping over something in the field. I have no doubt this Thing in the field was the third of the ten cylinders they had fired at us from Mars.

§ 2.2 Hyphenation Responsive or not, there’s no reason why we shouldn’t all be designing and building sites on flexible foundations. In a fluid layout, browser width and typographic measure are linked: the wider the viewport, the more characters per line. Keeping in mind that a range of 45-75 characters per line is generally accepted as safe for comfortable reading, there are a few things that can be done to avoid extra long lines of text in fluid layouts. Robert Bringhurst recommends for us to leave at least two characters behind and take at least three forward. Since hyphens is an inherited property, it isn’t sufficient to set it for a limited number of elements and assume you’re done. You have to make sure you’ve turned it off for the elements that shouldn’t be hyphenated. Eric Meyer

§ 3.1 Small Capitals Small caps help to make abbreviations way easier to read, but won’t stand out from the text. We highly suggest this bit of typographic flare with your content. True small capitals are now possible on the web, but alas, they are still difficult and will also depend on the typeface in use. Definitely check out Open Typography for those typefaces and services that provide authentic small caps. Lorem ipsum dolor sit amet, consectetur HTML adipisicing elit. CSS Laboriosam voluptatem a beatae accusantium accusamus dolor provident error consectetur quibusdam suscipit neque temporibus. Velit omnis voluptatum quasi tempora reiciendis expedita reprehenderit.

§ 3.2 Drop Capitals A “Drop Cap” is the art of using an uppercase glyph to mark the start of copy. A technique that has been around for almost two thousand years! There now is your insular city of the Manhattoes, belted round by wharves as Indian isles by coral reefs—commerce surrounds it with her surf. Right and left, the streets take you waterward. Its extreme downtown is the battery, where that noble mole is washed by waves, and cooled by breezes, which a few hours previous were out of sight of land. Look at the crowds of water-gazers there. <p class="typl8-drop-cap">…</p>

§ 3.3 Unicode Ampersands With the unicode-range property, we can avoid using verbose markup and only target the characters we like according to the unicode unique identifier. We also harness the power of the %placeholder in Sass allowing like minded selectors to string together this shared property in a DRY way from one single declaration. Copy and paste the Sass below into Codepen and check out the output for yourself. Hint: create multiple classes. Amper & Sands

§ 3.4 Small Print The small element is used to represent side comments or what’s commonly referred to as ‘small print’: disclaimers, caveats, legal restrictions, or copyrights. It can also be used for attributions or satisfying licensing requirements. …A common use is inline legalese, such as a copyright statement in a page footer, a disclaimer, or licensing information. It can also be used for attribution. Don’t use it for block-level content (paragraphs, lists, etc.), as this would be considered main content. small text does not need to be smaller than surrounding text — if all you want is smaller text use CSS instead. Oli Studholme Buy one widget, get one free! (While supplies last. Offer expires on the vernal equinox. Not valid in Ohio.) <small>…</small>

§ 4.1 Code Blocks Monospace fonts just as you desire for all your code block dreams! Monospace fonts or “fixed pitch” fonts, contain characters that all have the same character width. ‘l’, ‘1’ and ‘i’ are easily distinguished with monospace, ‘0’, ‘o’ and ‘O’ are easily distinguished and clear punctuation characters, especially braces, parenthesis and brackets. .this-widget { max-width: 200px; opacity: 0.5; color: red; }

§ 4.2 Figures Fig. 4.2 | Type Anatomy, a diagram and anatomy of typography. <figure> <img src="" alt=""> <figcaption> <strong></strong> </figcaption> </figure>

§ 4.3 Block Quotes The blockquote element represents a section that is being quoted from another source. Good blockquotes should include a citation, but one is not required. Stylistically, these can look a lot like pull-quotes by using :before and :after pseudo elements for the curly quotes, or, authors can include them inline. The contents of blockquote are limited to headings and paragraphs. header , footer , or cite tags are not allowed. For more examples, see A List Apart's sample blockquote patterns. Embracing the fluid & flexible aspect of responsive web design was an easy decision, but I’ve been less sure-footed when it comes to balancing that with setting type on the web Trent Walton <figure class="typl8-blockquote"> <blockquote cite=""> <p></p> </blockquote> <figcaption> <cite> <small><a href=""></a></small> </cite> </figcaption> </figure>

§ 4.4 Pull Quotes Pull quotes are tricky, but with this little ditty they’re not so difficult or tedious anymore. The example is an improvement based upon the 24 ways article discussing swooshy curly quotes without images. This particular example depicted takes advantage of psuedo selectors and the <aside> tag. Most people who use Helvetica, use it because it's ubiquitous. It's like going to McDonald's instead of thinking about food. Because it's there, it's on every street corner, so let's eat crap because it's on the corner. <aside class="typl8-pull-quote"> <blockquote> <p></p> </blockquote> </aside>

§ 4.7 Footnotes The sites we’ve built to display on a desktop, smartphone, or a tablet today could be on a TV Screen, coffee table display, or mega space yacht projection system tomorrow. Do yourself a favor and heed the advice of the Dao: A fully-scalable web1 <article> <p><sup><a href="#fn-itemX" id="fn-returnX"></a></sup></p> <footer> <ol class="foot-notes"> <li id="fn-itemX"><a href="#fn-returnX">↩</a></li> </ol> </footer> </article>