How to document a summer academy: Difference between revisions

From Hackers & Designers
No edit summary
No edit summary
Line 1: Line 1:
Vicky's documentation on hybrid publishing
'''[[Vicky De Visser]]'''
 
==Content creation==
 
 
==Choosing the right back-end to collect the documentation==
 
==Categorisation of the content==
 
==Co-editing==
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards.
 
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article.
 
==Making the documentation public: publishing==


[[Category:DIY Manual]]
[[Category:DIY Manual]]
[[Category:WriteMe]]
[[Category:WriteMe]]
[[Category:Print]]
[[Category:Print]]

Revision as of 16:21, 13 November 2015

Vicky De Visser

Content creation

Choosing the right back-end to collect the documentation

Categorisation of the content

Co-editing

After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement. It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards.

Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article.

Making the documentation public: publishing