<p>VueUse is a collection of utility functions based on Composition API. We assume you are already familiar with the basic ideas of Composition API before you continue.</p>
<ahref="https://vueuse.org/guide/">VueUse</a>
</div>
<ul>
<li>assumes a certain kind of reader</li>
<li>address where to link the necessary resources</li>
</ul>
refer to a particular language context (in this case french), a similar choice was made for vue, by the same developer
quick, faster and leaner development, compared to what?
lean from lean manufacturing?
for "modern" project. what is modern here?
<divclass="opening">
<p>Vite (French word for "quick", pronounced /vit/, like "veet") is a build tool that aims to provide a faster and leaner development experience for modern web projects.</p>
<ahref="https://vitejs.dev/guide/">Vite</a>
</div>
refer to a particular language context (in this case german)
it began as a simple collection: acknowledge the origins of the project
repeat WSGI three times without explaining, implying a certain kind of technical knowledge
time composite documentation: last sentence has been added later on.
<ul>
<li>refer to a particular language context (in this case french), a similar choice was made for vue, by the same developer</li>
<li>quick, faster and leaner development, compared to what?</li>
<li>lean from lean manufacturing?</li>
<li>for "modern" project. what is modern here?</li>
</ul>
<divclass="opening">
<p>
werkzeug German noun: “tool”. Etymology: werk (“work”), zeug (“stuff”). Werkzeug is a comprehensive WSGI web application library. It began as a simple collection of various utilities for WSGI applications and has become one of the most advanced WSGI utility libraries.</p>
<li>refer to a particular language context (in this case german)</li>
<li>it began as a simple collection: acknowledge the origins of the project</li>
<li>repeat WSGI three times without explaining, implying a certain kind of technical knowledge</li>
<li>time composite documentation: last sentence has been added later on.</li>
</ul>
<divclass="opening">
<p>Jinja is a fast, expressive, extensible templating engine. Special placeholders in the template allow writing code similar to Python syntax. Then the template is passed data to render the final document.</p>
time composite documentation: last sentence has been added later on.
acknowledge the origin of the project
<ul>
<li>fast, expressive, extensible</li>
<li>three features oriented to different needs</li>
<li>the figure of the engine</li>
<li>refer to the python community</li>
</ul>
<divclass="opening">
<p>Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. It began as a simple wrapper around Werkzeug and Jinja and has become one of the most popular Python web application frameworks.</p>
address a problem: to keep track of otherwise scattered pads
acknowledge external actors, such as the mediawiki api
refer to a specific context: people orbiting around xpub and lens based wiki, using etherpad
<ul>
<li>set the context: everyday life + artistic practice</li>
<li>digital life deeply connected with the idea of office and workspace</li>
<li>artistic operating system could sound like a disclaimer</li>
</ul>
<divclass="opening">
<p>The Padliography is a tool to keep track of our pads. It is built to interact with the MediaWiki API, and it uses XPUB & Lens-Based Wiki’s pages as archive.</p>
small app small server, probably for small drawings?
open to plurality of sources and destinations
architecture overview (sources and destinations connected through an express server via websockets)
<ul>
<li>address a problem: to keep track of otherwise scattered pads</li>
<li>acknowledge external actors, such as the mediawiki api</li>
<li>refer to a specific context: people orbiting around xpub and lens based wiki, using etherpad</li>
</ul>
<divclass="opening">
<p>A small app for collecting drawings in real time. Runs on a small express server that connects sources (where to draw) and destinations (where to display) via websockets.</p>
<ahref="https://git.xpub.nl/kamo/drw">drw</a>
</div>
<ul>
<li>small app small server, probably for small drawings?</li>
<li>open to plurality of sources and destinations</li>
<li>architecture overview (sources and destinations connected through an express server via websockets)</li>
address a specific public
to improve workflow, what does improve mean ? faster? less keystrokes?
</ul>
<divclass="opening">
<p>Emmet is a web-developer’s toolkit that can greatly improve your HTML & CSS workflow</p>
<ahref="https://docs.emmet.io/">Emmet</a>
</div>
<ul>
<li>address a specific public of web-developers</li>
<li>to improve workflow, what does improve mean ? faster? less keystrokes?</li>
</ul>
</main>
<section>
<h2>Hello worlding</h2>
<p>
An opening is a declaration of intents, it manifests intentions. These intentions are glued together in the smallest context possible of a sentence. They are like a trailer for a movie, or the thumbnail of a youtube video. Often exagerate, click-bait, ideological. How and why these different facets come together? They are a visibile traces of choices made during development, choices that sometimes are made evident within the documentation, and sometimes remain unanswered.
</p>
<p>
From the perspective of someone writing code and therefore code documentation, I'm interested in exploring these openings both from a stylistic and technical point of view. Leveraging on form, they are a perfect device to set the stage for code: a way to illuminate code choosing a particular angle, intensity and target, revealing some aspects and conceiling other ones. From a technical perspective they attach onto already constituted systems of meaning, such as a particular technology, a programming language, framework, or coding paradigm. They trigger mutual influences between code and context, like a telescope that can be used from both sides: from the code to the bigger context, and from the bigger context to the code. A way to infiltrate.
</p>
<p>
As someone that reads code documentation, I'm interested in make these openings more eloquent. Or even just having some tool or practice to decode them. Inflating the opening in a way that differ from the rest of the documentation.
</p>
<p>Every keyword is a branch. Zettelkasten vibes here.</p>
<p>Also a small confession: I'd prefer to exhibit something non digital for grad show.</p>
<p>A scultureeeeeeeee a data sculpture a 3d sculpture of how openings are aligned in 3d space. (pffffffff) Like a 3d diataxis - political compass. Ahaha.</p>
