1.1 KiB
Who is writing?
can documentation be an interface between different knowledges? trigger different kinds of economy around software?
-
interface between code, developer, world
-
post meritocracy manifesto
-
trans*femminist server whishlist
-
360 degrees of proximity
Software documentation comes in different formats.
The Díataxis framework (Procida, 2017) maps them into four main quadrants using a systematic approach. It focuses on four main needs of the user: to learn, to understand, to get the work done, and to gather specific informations.
In this thesis the term documentation is less structured: it tries to encompass different forms of care. Instead of prescribing the recipe for a perfect solution, it attempts to describe a surface, and ways to navigate it.
Expanding the four quadrants, mixing them we can include transversal practices like that proposed for 360 degrees of proximity.
not a rigid framework but a surface: a set of practices something to be negotiated and expanded
example: a practice that gets instantiated in the form of workshop (360 degrees of proximity)
alt text poetry