From f3b0bba9fff8c7300f890397836070d9adf86859 Mon Sep 17 00:00:00 2001 From: "kam (from the studio)" Date: Tue, 1 Nov 2022 16:04:03 +0100 Subject: [PATCH] trolley --- projects/grs/index.html | 111 ++++++++++++++++++++++++++++++++++++++++ projects/grs/style.css | 30 +++++++++++ 2 files changed, 141 insertions(+) create mode 100644 projects/grs/index.html create mode 100644 projects/grs/style.css diff --git a/projects/grs/index.html b/projects/grs/index.html new file mode 100644 index 0000000..51066ae --- /dev/null +++ b/projects/grs/index.html @@ -0,0 +1,111 @@ + + + + + + + Software documentation as a form of care??? + + + +

The problem with
software documentation

+ +

+ Software comes from a really specific occidental cultural tradition. Software tends to + priviledge masculine, binary, exploitative and extractive practices. Software is + shrouded in technical obscurity. Software comes invisible, transparent, neutral. + Software models the world in order to control it. +

+

+ To make software means not only to write code, but also to take a stance regarding this + trends. To make software means not only to write code, but also to create a context and + community around it. +

+

+ Documentation is a space that interfaces the different actors around software. Software + documentation is a space with potential to renegotiate and reclaim given margins and + entry points. It is a chance to overwrite what is normalized, and let different + knowledges and voices participate in the discourse around software. +

+ +

+ Documenting software is a complex practice. Documenting software is a process of + translation. Writing documentation it's more difficult than writing software itself. It + requires a lot of time and energy, and it involves many different skills: writing, + coding, knowing how to share and at which intensity. It's a collaborative practice that + could open to different voices. +

+

As a piece of code would write: I am documented, therefore I am.

+ +

+ Coding is not just production of software, but also production of knowledge. A dialogue + between human and more-than-human actors. The guestlist of this conference of the bits + is often compiled by chance: the choice of a particular programming language, the coding + style, the development environment and ecosystem, the infrastructure that runs the code, + and so on, are the result of specific contingencies. +

+ +

+ These contingencies are situated in precise contexts, and these contexts are different + one from another. Programming is not just sharing code, but sharing context. Programming + means to provide a point of view and a perspective to look at the world, before + attempting to get some grip onto it with a script. That's the reason why even if source + code, even when obfuscated, speaks for itself, it cannot always cast light around its + surroundings. +

+ +

+ To make place for code turns to be a necessary act of care in the process of sharing + knowledge. This does not mean to constrain the usage of some piece of software, or + provide opinionated solutions or tutorials, but rather letting others know where does + this code come from, and where it would like to go. +

+ +

+ Documentation is a way to produce narrations around software. To create a world for a + software to inhabit, to give it affordances and stretch what is possible to do or to + think with it. Documentation is a space for the political of software. It's a surface + that could host ideas in close contact with codes, letting them entangle and shape each + other. +

+
+

The plan

+ + + + diff --git a/projects/grs/style.css b/projects/grs/style.css new file mode 100644 index 0000000..de211b6 --- /dev/null +++ b/projects/grs/style.css @@ -0,0 +1,30 @@ +html, +body { + font-size: 21px; + line-height: 1.4; +} + +h1 { + font-family: "Redaction 35"; + line-height: 1; +} + +img { + border: 1px solid currentColor; + max-width: 100%; + object-fit: contain; +} + +hr { + break-before: always; +} + +li { + margin-bottom: 24px; +} + +@media print { + .pagebreak { + page-break-before: always; + } /* page-break-after works, as well */ +}