<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>
<p>Draw an image draw an image</p>
</div>
<section>
<h2>Hello worlding</h2>
<p>
@ -151,17 +162,60 @@
</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.
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 from a particular angle, revealing some aspects and conceiling other ones. From a technical perspective they attach onto already existent systems of meaning, such as particular technologies, a programming languages, frameworks, or coding paradigms. 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 encode context in the very first lines of documentation.
</p>
<p>
As someone that reads code documentation, I'm interested in making these openings more eloquent. Or even just having some tool or practice to decode them. Inflating the opening, even in directions that differ from the rest of the documentation. To see connections and genealogies, relations and contradictions in broader ecosystems.
</p>
<p>
Two keywords: encode and decode [context].
These could also be a set of different practices. With different tempo.
</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.
Chae asked: so it's a text based project?
</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>
<p>Draw an image draw an image</p>
<p>Opening as maneuverable object.</p>
<p>
Something maneuverable for who writes.
Something maneuverable for who reads.
Maneuverable meaning?
Meaning interactive?
Meaning small changes with visible effects.
Moire pattern
Shift in perspective
</p>
<divclass="permutations">
<divclass="opening original">
<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>
<p>Flask is a ___________ WSGI web application framework. It is designed to ____ _______ _______ _____ ___ ____, with the ability to ________ to _______ applications. It began as a ______ _______ ______ ________ ___ _____ and has become ___ __ ___ ____ _______ ______ web application frameworks.</p>
<p>_____ __ _ lightweight ____ ___ ___________ _________. __ __ ________ __ make getting started quick and easy, ____ ___ _______ __ scale up to complex ____________. __ _____ __ _ simple wrapper around Werkzeug and Jinja ___ ___ ______ one of the most popular Python ___ ___________ __________.</p>
<p>_____ is _ ___________ ____ ___ ___________ _________. __ is designed to make getting started _____ ___ ____, ____ ___ _______ __ scale up __ _______ ____________. __ began __ _ ______ _______ ______ ________ ___ _____ ___ has become ___ __ ___ ____ _______ ______ ___ ___________ __________.</p>
