You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
74 lines
3.0 KiB
HTML
74 lines
3.0 KiB
HTML
2 years ago
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
<head>
|
||
|
|
<meta charset="UTF-8">
|
||
|
|
<title>04 - Tree</title>
|
||
|
|
<link rel="stylesheet" href="/style.css">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<header>
|
||
|
|
<h1>doc doc doc</h1>
|
||
|
|
<div class="sub">documenting code documentation</div>
|
||
|
|
<div class="info">
|
||
|
|
hello! welcome. this is an archive to navigate trough documentation practices
|
||
|
|
</div>
|
||
|
|
<div class="attempt">
|
||
|
|
<p>
|
||
|
|
The path through documentation resources in the making of a project could be represented as a tree structure, where the root is the project idea or need and then branches all the explored direction and lateral resources.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
Tree structures recall hierarchy, because of the different structural positions of branches and leaves. However what I'm interested here is the temporality of the tree. There is a starting point, a root, and then different tryouts, with dead ends, ramifications, different experiments.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
An example is <a href="https://github.com/mbbill/undotree">undo-tree</a> where instead of the linear approach of <code>ctrl-z</code>, a fluorishing history of attempts is preserved.
|
||
|
|
</p>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
</header>
|
||
|
|
|
||
|
|
<section>
|
||
|
|
<p>
|
||
|
|
So the plan is: keep track of your path. Start from something (could be an idea for a project, a need for understanding, the writing of some documentation) and then keep track of the various resources encountered through time in a tree-like structure.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>
|
||
|
|
This excercise seems flexible enough to host different approaches and materials. Could be an history of navigation through hyperlinks, but also contain reflections and snapshots of how the initial idea changes during time. Ideally every node of the tree could be a potential entry point / backdoor to reflect on documenting practices.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<p>
|
||
|
|
It could be tried in alone or in group, with one or many trees. To have a less linear and more entangled structure. It could host practices such as the one of <em>03 - Pair</em>, where one driver go through and the navigator map into the tree.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
<ul class="questions">
|
||
|
|
<li>how to think about the tree as a writing machine?</li>
|
||
|
|
<li>how to store information in a way that is not too intrusive for the process?</li>
|
||
|
|
<li>how to represent the tree?</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
|
||
|
|
<section>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<h2>Prototype
|
||
|
|
</h2>
|
||
|
|
|
||
|
|
<div class="root">
|
||
|
|
<h3>
|
||
|
|
Comparative Iceberg Studies
|
||
|
|
</h3>
|
||
|
|
<p>
|
||
|
|
Write a image scraper to download a bunch of picture from the iceberg meme template (that maps facts about a topic from the tip, common knowledge, to the bottom, esoteric, misterious, unknown details). Group the image and align all of them. Call people within the field of each topic and make them comment the result. Edit and bound.
|
||
|
|
</p>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|