[Plan] Site Audit 3.x

Problem/Motivation

The 2.x version of Site Audit has a number of problems. It works only as a Drush plugin, it has no exposure in the Drupal UI, composer doesn't install it properly, incompatibility with Drush 9...

Proposed resolution

Site Audit 3.x should be a regular Drupal module with a UI exposed to run reports. If some checks cannot be run without privileged access, a Drush and Drupal Console command will be provided to run reports as expected.

Remaining tasks

1. Redefine Site Audit as a normal Drupal module.
2. Convert the existing DIY plugin system for checks into the standard plugin system with extensible @site_audit_check plugins. #2969605: Create plugin manager for Site Audit Checks →
4. Create Admin UI to allow checks/report to be enabled/disabled. #2971352: create settings UI to disable/enable reports and checks →
5. Port all 2.x checks to 3.x. - one issue per report
   • #2971354: Port Abstract Report and Checks →
   • #2971355: Port Best Practices Report and Checks →
   • #2971356: Port Block Report and Checks →
   • #2971357: Finish Porting Cache Report with all Checks →
   • #2971358: Port Codebase Report and Checks →
   • #2971359: Port Content Report and Checks →
   • #2971360: Port Cron Report and Checks →
   • #2971361: Port Database Report and Checks →
   • #2971362: Port Extensions Report and Checks →
   • #2971363: Port Frontend Report and Checks →
   • #2971364: Port Insights Report and Checks →
   • #2971365: Port Roles Report and Checks →
   • #2971366: Port Security Report and Checks →
   • #2971367: Port Status Report and Checks →
   • #2971368: Port Users Report and Checks →
   • #2971369: Port Views Report and Checks →
   • #2971370: Port Watchdog Report and Checks →
6. Deprecate 2.x as hard as possible, as it doesn't quite work right anyways.

User interface changes

We'd actually have one. It should appear under admin/reports similar to the Hacked! module.

API changes

• Checks would be extensible through the standard Drupal plugin system.
• Reports too, probably.
• Drush 9 commands to run an HTML, Text, or JSON report. #3001200: create Drush 9 integration →
• Drupal console support would be nice too. #3001204: Add Drupal Console commands →

Data model changes

Not applicable, unless if we want to store reports locally. If we do, steal the data model from https://www.drupal.org/project/site_audit_collector → and create a submodule ("site_audit_store"?) for the feature.