chapters cleanup and placeholders

chapters/01_who_is_reading.md

@@ -1,36 +1,17 @@
 # Who is reading
 
-_documentation as a surface to build worlds around software?_  
-_docs to lower barriers and create entry points_
-
 ```
-a surface to build worlds?
-    where software circulate
-    who gets to use it
-    political of the software
+documentation as a publishing surface?
 
 yes because
-    it's often first thing one reads when approaching software - see getting started   it's consulted not just from beginner, but also experienced users - see a code companion
+    it's often first thing one reads when approaching software - see getting started   
+    it's consulted not just from beginner, but also experienced users - see a code companion
 
 yes but
     it should be less hostile - see welcoming writing
-    it should stop assuming reader
-
-leading to --> 2. welcoming different knowledges
+    it should stop assuming reader - see natural readers
 ```
 
-## Hello worlding
-
-why and what a surface to build worlds?  
-articulate intro
-
--   where software circulate
--   who gets to use it
--   political of the software
-
-again versioning tiger ding sun ? --> https://tdingsun.github.io/worlding/
-(did already here --> https://hub.xpub.nl/soupboat/~kamo/projects/api-worldbuilding/ )
-
 ## Getting started
 `("Getting startled" could also make for a nice title)`
 

chapters/02_welcoming_others.md

@@ -1,30 +0,0 @@
-# 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

chapters/02_who_is_writing.md

@@ -0,0 +1,12 @@
+## 2. Who is writing?
+_2000_
+
+The second part explores documentation as a crossroads, where different knowledges meet in the making of software.
+
+Documentation is a space that interfaces between the code, the user, the developer, and the world. A space where to welcome different voices: not just engineers, not just experts, not just dudes. A space to acknowledge the massive labor of care besides technicalities, often marginalized by coding culture.
+
+__Sections:__
+
+A section that focuses on who is writing the software, but not just the code. From software as inherently collaborative practice to the post-meritocratic manifesto.
+
+A section about who is writing documentation, and how. Different strategies to approach it, from different knowledges. `wip`

chapters/03_hello_worlding.md

@@ -0,0 +1,11 @@
+## Hello worlding
+
+The third section is focused on worlding, and the relation between code, documentation practices and political aesthetic.
+
+Here documentation is seen as a surface that could host principles in close contact with algorithms, letting them entangle and shape each other. A way to orientate our instruments towards "non-extractive relationships, but in the meantime, being accountable for the ones they are complicit with." (A Wishlist for Trans\*feminist Servers, 2022)
+
+__Sections:__  
+
+A first part of theoretical examples of technology and worlding: Trans\*feminist Servers, Zach Blas, Tiger Ding Sun, James Bridle, Soon and Geox, Richard Gabriel.
+
+A second part of case studies. The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip`

chapters/03_orienting_software.md

@@ -1,6 +0,0 @@
-_can documentation be an ideal surface to build worlds?_
-
--   the screenless office
--   ian cheng
-
----