anchor.diff:          <div>
           	<ul class="posts">
           	    <p>The Privly developers survived the blink tag and midi song era of the internet, and we don't want to return to a time when sites are pieced together with inconsistent typography and generally bad style. Never. Again.</p>
  -        	    <li><span class="listitemtitle">Allow for Site-Specific CSS:</span> Privly content should identify itself, but should also fit its context. User submitted or host-page CSS should provide generalized styling of text content. <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
  -        	    <li><span class="listitemtitle">Provide Domain Specific Language (DSL):</span> Markdown is an excellent starting point for generating HTML for page injection, but it is not intended for systems like Privly. A DSL could solve many formatting problems. <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
  -        	    <li><span class="listitemtitle">Non-text Content:</span> Private information is not limited to text, and neither is Privly. <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
  +        	    <li><span class="listitemtitle developmentstatusvapor">Allow for Site-Specific CSS:</span> Privly content should identify itself, but should also fit its context. User submitted or host-page CSS should provide generalized styling of text content.</li>
  +        	    <li><span class="listitemtitle developmentstatusvapor">Provide Domain Specific Language (DSL):</span> Markdown is an excellent starting point for generating HTML for page injection, but it is not intended for systems like Privly. A DSL could solve many formatting problems.</li>
  +        	    <li><span class="listitemtitle developmentstatusvapor">Non-text Content:</span> Private information is not limited to text, and neither is Privly.</li>
               </ul>
           </div>
       
  
positive.code:         <div>
              <p>There are numerous ways to identify who you want to share something with. Content should be permissioned by whichever platform you use.</p>
          	<ul class="posts">
          	    <li><span class="listitemtitle">Share by Email</span> <span class="developmentstatus developmentstatusdeveloping">Under Development</span></li>
          	    <li><span class="listitemtitle">Share by Password</span> <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
          	    <li><span class="listitemtitle">Share with PGP key</span> <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
          	    <li><span class="listitemtitle">Share by Domain (Organizational sharing)</span> <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
          	    <li><span class="listitemtitle">Share by Geography (geoIP)</span> <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
          	    <li><span class="listitemtitle">Share by Diaspora Aspect, Google+ Circle, Twitter List, etc</span> <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
          	    <li><span class="listitemtitle">GeoIP Based Restrictions:</span> No major platforms have sharing rules for geographic regions. While GeoIP is not a robust security measure, it does make it difficult to access content outside an intended area. <span class="developmentstatus developmentstatusvapor">Not Under Development</span></li>
              </ul>
          </div>
      
  
negative.code:         <div>
              <p>Privly will never assert content ownership, but that promise is meaningless without providing ways for users to move their content into and out of content hosts.</p>
          	<ul class="posts">
          	    <li><span class="listitemtitle developmentstatusdeveloping">Content Server:</span> Users have a default server to post private content. The <%= link_to "server source code", "https://github.com/smcgregor/privly-web" %> is available for anyone to download and extend. As soon as we can guarantee browsing anonymity, anyone can host their own content.</li>
          	    <li><span class="listitemtitle developmentstatusvapor">Content Portability:</span> Users need the ability to export/import all their content to/from common formats.</li>
          	    <li><span class="listitemtitle developmentstatusdeveloping">Content lifetime:</span> Users have the ability to define a lifetime for their content (e.g. automatically delete after 30 days) as well as purge their content entirely.</li>
              </ul>
          </div>
      
  