**Feature summary** (what you would like to be able to do and where):
Make the platform for legible and accessible for technical contributors who will write edit checks and suggestions in the future.
**Benefits**: technical contributors can easily start new checks.
**What does done look like?**
- [ ] A brief overview of `TextMatchEditCheck`, in case the user can be directed there instead
- [ ] A minimal VE + Editcheck dev setup guide for mwcli – eg a pointer to other documentation and `LocalSettings.php` changes.
- [ ] One or two examples
- [ ] Lifecycle documentation
- What listeners exist, when they fire, what data they receive
- What context data is available, eg action tags (dismissal etc), modified ranges, selection
- [x] Brief guide to working in the codebase
- [ ] Pointers to VE data model concepts and a brief overview
- [ ] Examples of how to do the following with the data model:
- Search for strings (modified or otherwise)
- Identify modified nodes
- Identify nodes of a particular type
- [x] Notes on enabling checks for development
- [ ] Pointers to configuration files and how they're laid out