Save the KS Toolkit wiki
This is the landing page to organize the work to be done to transfer and update the content of the KStoolkit.
Initiative started by Lucie mid February 2018
Contents
People interested in helping out
alphabetically by name
- Arwen Bailey
- Carl Jackson
- Davide Piga
- Johannes Schunter
- Lucie Lamoureux
- Nadejda Loumbeva
- Nadia von Holtzen
- Nancy White
- Pete Cranston
- Peter J. Bury
- Sophie Alvarez
Ideas, suggestions and similar
Integrate KS Toolkit with KM5Dev wiki
Is that an option if KS Toolkit 'owning' organizations cannot foot the bill for an alternative Wiki platform?
(more details to be added to this idea: proponent, advantages, disadvantages and things that might get tricky)
Rebuild the KS Toolkit using Google Apps
We could consider turning the toolkit into a Google Site where each tool and each method is documented on a Google Doc instead of a website page. We would lose tagging, but we would gain printable pages and easier maintenance.
- See a prototype
At the basis of the toolkit there would be a Google Drive folder which would contain all tools and methods.
Suggested default permissions for the folder and the documents in itwould be "anybody with the link can comment", which means that anyone would be able to suggest changes by simply typing into the documents. Edits, before reflecting in the docs, would have to be approved by admins (just like the "track changes" function).
Proponent: Davide Piga
Advantages
- if we need to migrate again, we can just embed the folder in some other website
- thanks to the fact that the toolkit is also a folder, it can be easily taken offline (toolkit on the go)
- each tool/method is a collaborative document
- it’s generally easier for users to add/edit tools/methods as they would just have to create and edit a google document (possibly starting from a standard template that we would provide to them) instead of editing a wiki (which requires knowledge of wiki syntax and an account on the wiki). Assumption: the vast majority of people have a Google account.
Disadvantages and things that might get tricky
- Migration is a manual process. There are currently 400+ methods/tools on the toolkit. It will take some work, or some money (approximately 30 days for one consultant)
