Proposal: Release 2.0 Strictly as an installer

Per discussion in indieweb/wordpress-uf2/issues/29 I'm proposing starting a 2.0 milestone in which the IndieWeb WordPress plugin is strictly an installer of the other IndieWeb related plugins.

This would include removing all functionality from the IW plugin and move to the MF2 plugin and agreeing on a new (or improved) UI for walking new users through installing and configuring the required plugin.

Goals would include keeping within the WordPress admin UI aesthetic and simplifying the on boarding experience to users both new to the IndieWeb tools as well as WordPress.

#72 has some notes about the onboarding experience as well as a specific issue with the Getting started page. Is that different from the installer/proposed wizard?

Start by reading the discussion in indieweb/wordpress-uf2#29 and the onboarding notes in #72, then compare whether the Getting started page belongs in the proposed installer wizard. The issue does not identify files, tests, or a concrete implementation boundary; completion would require an agreed 2.0 scope, plugin responsibilities, and onboarding design.

Written by the indexing model from the issue text.