Toolhub's design document envisions combining "owner" created data in the form of toolinfo.json data files (or local in-app equivlalent) with "annotations" that users of the website add to augment the owner provided data. There are also many ideas in the roadmap for creating "collections" of tools.
Where there is free form text content, there will be vandalism. This is an Internet truism that Wikimedians are well aware of. MediaWiki includes many components to help support patrolling content submissions. Toolhub will need systems for this as well, but what systems? How can we make the process of patrolling Toolhub feel friendly to folks who are used to doing content patrolling with MediaWiki?
** edit history for a toolinfo record
** edit history for an editor
** edit history for all toolinfo records
* **Authenticated users**
** undo an edit
** revert content to a prior edit
** mark edit as reviewed/patrolled
** work queue/edit history filter showing edits that have not been reviewed
** suppress an edit