<?xml version="1.0"?>
<?xml-stylesheet href="/transform" type="text/xsl"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:bibo="http://purl.org/ontology/bibo/" xmlns:bs="http://purl.org/ontology/bibo/status/" xmlns:ci="https://vocab.methodandstructure.com/content-inventory#" xmlns:dct="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xhv="http://www.w3.org/1999/xhtml/vocab#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" lang="en" prefix="bibo: http://purl.org/ontology/bibo/ bs: http://purl.org/ontology/bibo/status/ ci: https://vocab.methodandstructure.com/content-inventory# dct: http://purl.org/dc/terms/ foaf: http://xmlns.com/foaf/0.1/ rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# xhv: http://www.w3.org/1999/xhtml/vocab# xsd: http://www.w3.org/2001/XMLSchema#" vocab="http://www.w3.org/1999/xhtml/vocab#" xml:lang="en">
  <head>
    <title property="dct:title">Documents Make Lousy Documentation</title>
    <base href="https://doriantaylor.com/documents-make-lousy-documentation"/>
    <link href="document-stats#EYgyrRw-3V51hq4OjZ6ZVI" rev="ci:document"/>
    <link href="elsewhere" rel="alternate bookmark" title="Elsewhere"/>
    <link href="this-site" rel="alternate index" title="This Site"/>
    <link href="http://purl.org/ontology/bibo/status/published" rel="bibo:status"/>
    <link href="" rel="ci:canonical" title="Documents Make Lousy Documentation"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="file/documents-make-lousy-documentation" rel="dct:hasPart foaf:depiction"/>
    <link href="file/abcs-of-content-driven-systems" rel="dct:hasPart"/>
    <link href="file/cool-uris-dont-change" rel="dct:hasPart"/>
    <link href="file/data-sovereignty" rel="dct:hasPart"/>
    <link href="annual-program-2019" rel="dct:references up" title="Annual Program: 2019"/>
    <link href="javascript:sendMail('doriantaylor.com','research','Documents%20Make%20Lousy%20Documentation');" rel="dct:references"/>
    <link href="person/dorian-taylor" rel="meta" title="Who I Am"/>
    <link about="./" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="f07f5044-01bc-472d-9079-9b07771b731c" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="this-site" rel="alternate"/>
    <link about="./" href="elsewhere" rel="alternate"/>
    <link about="./" href="e341ca62-0387-4cea-b69a-cdabc7656871" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="this-site" rel="alternate"/>
    <link about="verso/" href="elsewhere" rel="alternate"/>
    <meta content="documents-make-lousy-documentation" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="false" datatype="xsd:boolean" property="ci:indexed"/>
    <meta content="Motto: Disencumbering organizational reference material." name="description" property="dct:abstract"/>
    <meta content="2019-06-27T05:04:06+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="2019-06-27T05:14:23+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2019-06-27T09:30:49+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2019-08-15T21:03:26+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T15:10:50+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta about="person/dorian-taylor#me" content="Dorian Taylor" name="author" property="foaf:name"/>
    <meta content="summary_large_image" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="Documents Make Lousy Documentation" name="twitter:title"/>
    <meta content="Motto: Disencumbering organizational reference material." name="twitter:description"/>
    <meta content="https://doriantaylor.com/file/documents-make-lousy-documentation" name="twitter:image"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="annual-program-2019" rev="dct:references" typeof="bibo:Note">
              <span property="dct:title">Annual Program: 2019</span>
            </a>
          </li>
          <li>
            <a href="cool-uris-dont-change" rev="dct:references" typeof="bibo:Note">
              <span property="dct:title">Cool URIs Don't Change</span>
            </a>
          </li>
          <li>
            <a href="data-sovereignty" rev="dct:references" typeof="bibo:Note">
              <span property="dct:title">Data Sovereignty</span>
            </a>
          </li>
          <li>
            <a href="the-abcs-of-content-driven-systems" rev="dct:references" typeof="bibo:Note">
              <span property="dct:title">The ABCs of Content-Driven Systems</span>
            </a>
          </li>
          <li>
            <a href="toys" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Toys</span>
            </a>
          </li>
          <li>
            <a href="document-stats#EYgyrRw-3V51hq4OjZ6ZVI" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:620cab47-0fb7-4579-8d61-ab83a367a655</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EVqbQMTS4YRbELO5Px8oLK" typeof="bibo:Note">
    <article>
      <figure id="EA8jeupVKTtEmlOcFFdACL">
        <img src="file/documents-make-lousy-documentation;knockout" alt="Documents Make Lousy Documentation"/>
        <h1>Documents Make<br/>Lousy Documentation</h1>
        <p><em>Disencumbering organizational reference material</em></p>
      </figure>
      <p>Documents&#x2014;deliberately-prepared, edited, curated, formatted, <em>sequences</em> of content&#x2014;are great for telling <em>stories</em>. They're great for conveying <em>arguments</em>. However, if you already buy the argument and you're just looking for <em>facts</em>, documents have a number of characteristics that, when compared to newer&#x2014;as in <em>invented sometime in the last few decades</em>&#x2014;technology, simply get in the way.</p>
      <p>We are 30 years into the Web, meaning we are 30 years into a robust and mature global hypermedia system. Why, then, are we still so preoccupied with documents? Why do Word, Excel, and Powerpoint (and their Google and <abbr>PDF</abbr>-taxidermied counterparts) still dominate? Why, when we need to locate some intraorganizational reference material, do we still have to slog through simulated paper where the information we want is buried in superfluous exposition? Especially now, in the burgeoning era of <dfn>design systems</dfn>, <a href="design-system-as-style-manual-with-web-characteristics" rel="dct:references" title="Design System as Style Manual With Web Characteristics">which are inherently hypertextual?</a></p>
      <section id="Eg2ZgY7wqpiPPmNZkfWbxJ">
        <h2>Origin Story</h2>
        <p>This theme represents something I have been chipping away at for over a decade: Documents are great for <em>stories</em>, and stories are great for presenting an argument, but if you&#x2019;re already convinced of the argument, what you need is a <em>reference</em>. The best kinds of references are the ones that get you in and out with the information you need with the least overhead lost to searching and scanning. It is also important to be able to filter, aggregate, reformat, and ultimately repurpose said information, so merely indexing your documents for full-text search doesn't finish the job. What it spells is <dfn>hypertext</dfn>: lots of little pieces strung together with links. <em>Lots</em> of links.</p>
      </section>
      <section id="EmcHzTAmgXEQ2ijVAGU5FK">
        <h2>The Program</h2>
        <p>There are two obvious targets under this theme:</p>
        <ol>
          <li>How to go into an organization and dissolve a corpus of documents into a tight hypermedia reference,</li>
          <li>How one could not only <em>make</em> such an asset, but also package and deliver it.</li>
        </ol>
        <p>The challenge is that what I am terming <dfn>dense hypermedia</dfn> has a great many more moving parts than an ordinary website, however the <em>opportunity</em> is that these assets can be delivered piece by piece. Indeed, this website, which began <q>dense</q>&#x2014;and has since thinned out over the decade of its existence&#x2014;is perfect non-<abbr title="non-disclosure agreement">NDA</abbr>-encumbered fodder for demonstrating the rehabilitation technique, which will feed back into both client projects and general consumption.</p>
      </section>
      <footer>
        <form action="javascript:sendMail('doriantaylor.com','research','Documents%20Make%20Lousy%20Documentation');" id="Em0OGNom78t2fJboUR_M9K">
          <h3>Interested? <button>Get In Touch</button></h3>
        </form>
        <h5>Or, have a look at these other research themes:</h5>
        <nav>
          <a rel="dct:references first" href="data-sovereignty" title="Data Sovereignty">
            <img src="file/data-sovereignty;knockout" alt="Data Sovereignty"/>
            <h4>Data Sovereignty</h4>
            <p>Possession is nine tenths of the law</p>
          </a>
          <a rel="dct:references prev" href="the-abcs-of-content-driven-systems" title="The ABCs of Content-Driven Systems">
            <img src="file/abcs-of-content-driven-systems;knockout" alt="The ABCs of Content-Driven Systems"/>
            <h4>The ABCs of<br/>Content-Driven Systems</h4>
            <p>Decoupling <strong>a</strong>ccess control from <strong>b</strong>randing <em>and</em> <strong>c</strong>ontent</p>
          </a>
          
          <a rel="dct:references last next" href="cool-uris-dont-change" title="Cool URIs Don't Change">
            <img src="file/cool-uris-dont-change;knockout" alt="Cool URIs Don't Change"/>
            <h4>Cool URIs Don't Change</h4>
            <p>How much value gets lost to broken links?</p>
          </a>
        </nav>
      </footer>
    </article>
  </body>
</html>
