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.
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
# 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 |