anchor.diff:          	    <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 width="100%" style="margin-top: 20px;">
  +                <div class="developmentkey developmentkeyvapor">
  +                    <p>Not Started</p>
  +                </div>
  +                <div class="developmentkey developmentkeydeveloping">
  +                    <p>Developing</p>
  +                </div>
  +                <div class="developmentkey developmentkeyreleased">
  +                    <p>Completed</p>
  +                </div>
  +            </div>
           </div>
       
           <h2><a id="accordion_security" href="#accordion_security">3. Security</a></h2>
  
positive.code:                 <li><span class="listitemtitle developmentstatusvapor">Peer-to-peer storage:</span> Once data is encrypted, it doesn't matter where you store it. Success of systems like BitTorrent and Bitcoin suggest ways to decentralize storage, but we need to extend their ideas to ensure that browsing anonymity is maintained. Privly's researchers find this aspect fascinating, so we will probably revisit this soon.</li>
                  <li><span class="listitemtitle developmentstatusvapor">Personal Semantic Datastore:</span> Text conversations are not the only type of personal information. Many exciting applications rely on declarations of who you are. When you give Facebook your date of birth, hometown, and likes, you give them a rich dataset that is shared with third-party applications. An anonymized and encrypted personal information database would make it easier for you to use exciting functionality without allowing companies to correlate your personal information with a database of marketing information. You are the customer, not the product.</li>
              </ul>
          </div>
          
          <h2><a id="accordion_protocol" href="#accordion_protocol">Appendix: Projected APIs</a></h2>
  
negative.code:         	    <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 width="100%" style="margin-top: 20px;">
                  <div class="developmentkey developmentkeyvapor">
                      <p>Not Started</p>
                  </div>
                  <div class="developmentkey developmentkeydeveloping">
                      <p>Developing</p>
                  </div>
                  <div class="developmentkey developmentkeyreleased">
                      <p>Completed</p>
                  </div>
              </div>
          </div>
      
          <h2><a id="accordion_other" href="#accordion_other">6. Other Items</a></h2>
  