<?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">The Web Doesn't Have Content, the Web IS Content</title>
    <base href="https://doriantaylor.com/the-web-doesnt-have-content-the-web-is-content"/>
    <link href="document-stats#E1uUXI-Jbi0_QTUKnkJMJK" 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="The Web Doesn't Have Content, the Web IS Content"/>
    <link href="lexicon/#EqIUfKvI93wG3TQRQDwoVJ" rel="dct:audience" title="Information Architect"/>
    <link href="lexicon/#ErEcH3z-9vn29IFbZ0GdpI" rel="dct:audience" title="Content Strategist"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="lexicon/#EnewYu-MeZVXNc97q_-jAI" rel="dct:subject" title="Web Development"/>
    <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="the-web-doesnt-have-content-the-web-is-content" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="This was a comment I left in response to Christopher Detzi's post called The Content Conundrum on Boxes and Arrows. It got mangled by their CMS, so I reformatted it here." name="description" property="dct:abstract"/>
    <meta content="2009-08-04T20:03:54+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="the-web-doesnt-have-content-the-web-is-content" property="dct:identifier"/>
    <meta content="2009-08-04T20:26:52+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2009-08-04T20:21:20+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-09-01T19:25:35+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-09-01T19:57:07+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T04:18:52+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" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="The Web Doesn't Have Content, the Web IS Content" name="twitter:title"/>
    <meta content="This was a comment I left in response to Christopher Detzi's post called The Content Conundrum on Boxes and Arrows. It got mangled by their CMS, so I reformatted it here." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="on-the-building-of-software-and-websites" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">On the &#x201C;Building&#x201D; of Software and Websites</span>
            </a>
          </li>
          <li>
            <a href="people-rather-than-features-are-the-largest-common-factor" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">People, Rather than Features, are the Largest Common Factor</span>
            </a>
          </li>
          <li>
            <a href="what-we-mean-when-we-say-website" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">What We Mean When We Say &#x201C;Website&#x201D;</span>
            </a>
          </li>
          <li>
            <a href="document-stats#E1uUXI-Jbi0_QTUKnkJMJK" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:d6e51723-e25b-48b4-afd0-4d42a7909309</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EEKe65AE_UeVRj3bp2-qdK" typeof="bibo:Article">
    <aside role="note" id="E6HxNce64I_ONRw_zcZTIJ">
      <p>This is a reformatted version of my comment on <a href="http://twitter.com/detzi" rel="dct:references">Christopher Detzi's</a> post on <a href="http://boxesandarrows.com/" title="Boxes and Arrows: The design behind the design" rel="dct:references">Boxes and Arrows</a>: <a href="http://boxesandarrows.com/view/the-content" title="The Content Conundrum" rel="dct:references">The Content Conundrum</a>
      </p>
    </aside>
    <p>In some ways I think we still treat the design and production of Web-based systems the same as we do desktop applications (a safe conclusion given the explosive popularity of <acronym title="Asynchronous JavaScript and XML">AJAX</acronym> and the <a href="http://html5.digitalbazaar.com/a-new-way-forward/" title="A Community-Driven Proposal for Developing HTML5" rel="dct:references">recent events</a> around <acronym title="Hypertext Markup Language">HTML</acronym> 5). Since I began using the Web in 1994, I have watched us contort it almost beyond recognition into a signal-degraded mimic of what we have had on the desktop for the <a href="http://en.wikipedia.org/wiki/WIMP_%28computing%29" title="WIMP (computing) &#x2014; Wikipedia" rel="dct:references">last three decades</a>. It's almost as if everyone has missed <a href="http://www.theatlantic.com/doc/194507/bush" title="As We May Think - The Atlantic (July 1945)" rel="dct:references">the point</a>.</p>
    <p>The first half of the acronyms representing <span class="parenthesis" title="HTTP, HTML and the URI">two of the three salient concepts</span> of the Web are <strong>HT</strong> which stand for Hyper<em>text</em>, which enables us to convey information without having to spin the roulette wheel for the correct arrangement of concepts that pass the attrition test we call communication. The Web doesn't <em>have</em> content, the Web <em>is</em> content. Content as it has been for millennia with the addition of an eminently useful, newish form of punctuation known as the <a href="http://en.wikipedia.org/wiki/Hyperlink" title="Hyperlink &#x2014; Wikipedia" rel="dct:references">link</a>. Given the state of the technology you'd think it was hyper<em>buttons</em>, or hyper<em>widgets</em> or something, not hyper<em>text</em>. Content is what gets sandwiched between the code and the lozenges; what supplants <a href="http://en.wikipedia.org/wiki/Lorem_ipsum" title="Lorem ipsum &#x2014; Wikipedia" rel="dct:references">Lorem ipsum</a> on <a href="http://en.wikipedia.org/wiki/Photoshop" title="Adobe Photoshop &#x2014; Wikipedia" rel="dct:references">Photoshop</a> mockups. When it shows up, it is barely distinguishable from its printed counterpart. How exactly did this happen?</p>

    <p><a href="http://boxesandarrows.com/view/the-content" title="The Content Conundrum" rel="dct:references">As Mr. Detzi underscores</a>, content gets treated as orthogonal to programming and design (where <em>design</em> is defined as the production of the part that looks something between a magazine layout and an avionics panel). While I acknowledge that the engineering paradigm tends to dominate any knowledge product where executable code can be found, I wonder if the short-shrift situation of content has something to do with the way it is made.</p>
    <p>We typically write content using tools designed primarily for the authoring of <a href="http://en.wikipedia.org/wiki/Microsoft_Word" title="Microsoft Word &#x2014; Wikipedia" rel="dct:references">printed memoranda</a>, and to a lesser extent, reports. Occasionally, we use tools <a href="http://en.wikipedia.org/wiki/Adobe_FrameMaker" title="Adobe FrameMaker &#x2014; Wikipedia" rel="dct:references">designed for books</a>, <a href="http://www.latex-project.org/" title="LaTeX Project: LaTeX &#x2013; A document preparation system" rel="dct:references">scientific papers</a> or <a href="http://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture" title="Darwin Information Typing Architecture &#x2014; Wikipedia" rel="dct:references">online help</a>. With the possible exception of the very last, how closely do any of these targets resemble hypertext? Is it possible that the way that content is conceived and delivered compromises its potency?</p>
    <p>Finally, it should be noted that code, interaction design and visual design can be spoken of in terms of content. Code is the principal way for programmers to tell one another what they are telling the computer. Interaction is a stochastic conversation between a person and a computation using what is ultimately a domain-specific language. Visual design emotes and implies what words can't reach. Rather than designating content as something that is plugged into a decorated shell, why not endeavour to put it at the centre?</p>
  </body>
</html>
