<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jpcody)</title>
    <link>https://pinboard.in/u:jpcody/public/</link>
    <description>recent bookmarks from jpcody</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://alistapart.com/article/creating-style-guides"/>
	<rdf:li rdf:resource="http://trulia.github.io/hologram/"/>
	<rdf:li rdf:resource="https://github.com/necolas/idiomatic-css"/>
	<rdf:li rdf:resource="http://oli.jp/2011/style-guide/"/>
	<rdf:li rdf:resource="http://paulrobertlloyd.com/about/styleguide/"/>
	<rdf:li rdf:resource="http://taitems.github.com/Front-End-Development-Guidelines/"/>
	<rdf:li rdf:resource="http://yellowshoe.com.au/standards/"/>
	<rdf:li rdf:resource="http://www.salford.gov.uk/webstandards-styleguide.htm"/>
	<rdf:li rdf:resource="http://developer.fellowshipone.com/patterns/code.php"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://alistapart.com/article/creating-style-guides">
    <title>Creating Style Guides · An A List Apart Article</title>
    <dc:date>2014-04-20T23:00:36+00:00</dc:date>
    <link>http://alistapart.com/article/creating-style-guides</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Several years ago, I was working on a large, complex application. It was a bit of a legacy project: many different designers and front-end developers had come and gone, each appending a new portion to the sprawling application. By the time I arrived, the CSS was huge, the styles were varied, and it took a lot of effort to find out if anything was reusable.

]]></description>
<dc:subject>styleguide css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:1b8117b1d839/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://trulia.github.io/hologram/">
    <title>Hologram - Style Documentation Build System</title>
    <dc:date>2013-06-21T11:25:25+00:00</dc:date>
    <link>http://trulia.github.io/hologram/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Hologram is a Ruby gem that parses comments in your CSS and turns them into a beautiful style guide.

]]></description>
<dc:subject>css styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:35c362dbf6af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/necolas/idiomatic-css">
    <title>necolas/idiomatic-css</title>
    <dc:date>2012-06-18T21:27:57+00:00</dc:date>
    <link>https://github.com/necolas/idiomatic-css</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The following document outlines a reasonable style guide for CSS development. It is not meant to be prescriptive and I do not wish to impose my style preferences on other people's code. However, these guidelines do strongly encourage the use of existing, common, sensible patterns.]]></description>
<dc:subject>css styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:2524bcc09919/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://oli.jp/2011/style-guide/">
    <title>oli.jp style guide ❧ Oli.jp (@boblet)</title>
    <dc:date>2011-12-08T16:13:24+00:00</dc:date>
    <link>http://oli.jp/2011/style-guide/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This is a personal style guide for oli.jp. I’m publishing it to share and for feedback, and also because I <strong>ly believe you should build a style guide for every site you make. Hopefully this one will give you a head start.

]]></description>
<dc:subject>styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:6ad59f2c2c4a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://paulrobertlloyd.com/about/styleguide/">
    <title>Styleguide — Paul Robert Lloyd</title>
    <dc:date>2011-12-08T16:13:13+00:00</dc:date>
    <link>http://paulrobertlloyd.com/about/styleguide/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This document is a guide to the mark-up styles used throughout the site.

]]></description>
<dc:subject>styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:f34906a44ef6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://taitems.github.com/Front-End-Development-Guidelines/">
    <title>Front End Development Guidelines</title>
    <dc:date>2011-05-06T01:06:22+00:00</dc:date>
    <link>http://taitems.github.com/Front-End-Development-Guidelines/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The absence of a DOCTYPE is a crime punishable by death. You may have relied on the following DOCTYPE in the past, but it's important to know that this is now being superceded by a leaner and meaner snippet.

]]></description>
<dc:subject>styleguide html css javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e31e3d3b7d23/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://yellowshoe.com.au/standards/">
    <title>Front end standards</title>
    <dc:date>2011-04-12T00:16:27+00:00</dc:date>
    <link>http://yellowshoe.com.au/standards/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This little book is to aid a shared understanding of front-end development best practice at PUP.

It's to help us deliver high quality content that works better, reaches more people - not only in today's browsers & devices, but in tomorrows.]]></description>
<dc:subject>standards bestpractices css styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:ccd038f6ce89/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.salford.gov.uk/webstandards-styleguide.htm">
    <title>Web application development guide - Salford City Council</title>
    <dc:date>2010-06-21T19:13:49+00:00</dc:date>
    <link>http://www.salford.gov.uk/webstandards-styleguide.htm</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The following document is a style guide to assist in the production, implementation and continuing development of all Salford City Council websites and web applications. This document outlines the overall file structure, naming conventions, design and coding guidelines, styles and resources used in the construction of this site. To ensure design continuity and maintain the lifespan of sites, it is important that everybody involved in the development, maintenance and updating of sites read, understand and adhere to this guide.

]]></description>
<dc:subject>styleguide code webapp</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:0dbc7106e00f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:webapp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.fellowshipone.com/patterns/code.php">
    <title>Design Patterns Library | Fellowship Technologies</title>
    <dc:date>2009-10-28T19:27:20+00:00</dc:date>
    <link>http://developer.fellowshipone.com/patterns/code.php</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Fellowship One's coding standards style guide.]]></description>
<dc:subject>code standards styleguide style</dc:subject>
<dc:identifier>https://pinboard.in/u:jpcody/b:a3eb4dc32225/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:style"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>