Coming Soon v2 post-launch tasks

[ramonjd]

Things have been up for a while. No major issues. What do we do next?

Here are some high-/low-/somewhere-in-between-level tasks.

Immediate

• Preserve Private + Viewer user privileges D53164-code and Check for public coming soon mode and show the viewers tab #47666 (priority high)
• Update FG document PCYsg-py7-p2 (priority high)
• Refactor the MU plugin Coming Soon MU plugin #47486
• Add login hooks to the Atomic Coming Soon page Add login hooks to the Atomic Coming Soon page #47775
• Ensure Coming Soon page doesn't import theme CSS for Atomic sites (we think it might be doing that)
• Remove Calypso coming-soon-v2 flags and conditional code Coming soon: remove flag and permanently enable v2 for viewers tab #47854 Coming soon: remove flag and permanently enable v2 for site creation #47849 Coming soon: remove flag and permanently enable v2 for the site badge #47850 Removing the coming-soon-v2 flag #48346 Coming soon: remove flag and permanently enable v2 for seo settings notice #47851 Coming soon: remove flag and permanently enable v2 for site settings #47852
• Use a hook to return the localized_wpcom_url from the WPCOM side instead of using a WPCOM-only method in the ETK Coming Soon: add coming soon wpcom localized url filter #48076 D53828-code
• Ensure the badge updates when a user changes the settings Coming Soon: remove update_option_blog_public hook #48153

Can be done now, but only if we get time

• Update the fallback coming soon page design Update the fallback coming soon page #46641 and maybe look at the UX of the buttons/layout for .com and Atomic
• Hide privacy settings for unlaunched sites Hide privacy settings for unlaunched sites #46629

Down the track

We might like to do another data request to check how many users are running coming soon v1 mode. See pa1C6h-Qp-p2

At this point we've already prepared to deliver the coming soon v2 functionality to users who haven't yet switched to coming soon v2 (via option checks or whatever).

• Audit v1 code: where is it? What should we keep? What should we remove?
• Decouple privacy by default from Coming Soon
• Centralize Coming Soon functionality: where we can, to the ETK plugin, where we can't, to the WPCOM mu-plugin
• Remove references to Coming Soon v1
• Cleanup WPCOM and WPCOMSH launch banner logic