The Editing Team sees Edit Check – in part – as a system that enables volunteers to program policies directly into visual editor-powered editing experiences.
This task involves the work of becoming more clear about the constraints that will guide how this "volunteer programming" happens and the forms it takes.
Open questions
- Is there a central repository of Checks?
- Are Checks hosted/implemented on a per-project basis
- Do Checks need to be merged in our codebase to run?
#Are there a relatively few number of generic Checks (e.g. text matching, absence/presence of specific elements (e.g. images, captions, references, templates, annotations, etc.) that can be extended/configured to accommodate more nuanced/specific Checks?