Explore better ways to guide users looking to use Full Site Editing

[desrosj]

Follow up to #53410.

In [51193,51197], some minimal checks were added to help protect users from accidentally making their site unusable when a theme supporting Full Site Editing is activated without the Gutenberg plugin being active.

The protection put in place was very minimal in the interest of time. This is to explore how to make this better.

[poena]

It is unclear to me what types of improvements are expected for this ticket.
Do we need to move it to the 5.9 milestone?

Personally I would prefer a solution where themes are allowed to require plugins, and can not be activated without them.
A solution not limited to themes that support full site editing that requires Gutenberg.

[desrosj]

Replying to poena:

It is unclear to me what types of improvements are expected for this ticket.
Do we need to move it to the 5.9 milestone?

This was created to explore the thoughts expressed in ticket:53410#comment:17. I had explored adding an install or activate link/button, but it was difficult because of the context of the screen.

[51193] was meant as a temporary fix to prevent scenarios where the user may become lost when trying to activate a theme that requires Gutenberg to be active.

If anything, I advocate for closing this ticket out instead of punting to 5.9. When the rest of Full Site Editing is merged into core (currently targeted for 5.9), there will no longer be a need for this as the requirement for the Gutenberg plugin would be gone, and the changes in [51193] should be removed.

Punting to 5.8.2 for now.

[desrosj]

I've opened #54366 to remove the temporary stop gaps added in #53410, which will render this ticket unnecessary.