@ -34,16 +34,16 @@ Every piece of documentation will try to reflect on different angles.
More precisely these four aspects will be addressed:
More precisely these four aspects will be addressed:
- **Tone and style**
- **Tone and style**
How to make a documentation more accessible? How to create multiple entry points in a complex topic? How to address different kind of users, and not just a generic one?
How to make a documentation more accessible? How to create multiple entry points in a complex topic? How to address different kind of users, and not just a generic one?
- **Participation**
- **Participation**
Who gets to write, and who is forced to do it? How does development and technical writing interact? Is technical writing a subaltern position in the industry of software development?
Who gets to write, and who is forced to do it? How does development and technical writing interact? Is technical writing a subaltern position in the industry of software development?
- **Destination**
- **Destination**
Who can read documentation? Who can access? Where is the documentation hosted? How does it relate with a bigger context, if any?
Who can read documentation? Who can access? Where is the documentation hosted? How does it relate with a bigger context, if any?
- **Susteinability**
- **Susteinability**
How to face the lack of resources when approaching technical writing? Strategies to share workloads and collaboration. Strategies to take care of shared piece of software.
How to face the lack of resources when approaching technical writing? Strategies to share workloads and collaboration. Strategies to take care of shared piece of software.
The critical and theoretical research will be weaved around the actual documentations, in order to create a discourse and annotate the development of this practice.
The critical and theoretical research will be weaved around the actual documentations, in order to create a discourse and annotate the development of this practice.
