Implement settings splash notice

postphotos commented 6 years ago

As a new user of the AMP WP plugin, I need a splash screen that helps with understanding of what the plugin does, what settings do and how to solve AMP errors.

[x] AC1: WORDING - Identify or write copy that helps explain what settings do, what next steps are past activation (related #1366).
[x] AC2: DESIGN - Finalize design (related #1288) of what this should look like in a high fidelity fashion with all art assets prepared for the plugin.
[x] AC3: INTERFACE - On the settings page, implement the ability to have a dismissible splash "panel" that sits above the toggles.
[x] ~AC4: Implement new settings toggle design (related #1288) from AC2.~
[x] AC5: Combine AC1, AC2 and AC3, AC4 work in visual styles and functionality.
[x] AC6: Add call-to-action button linking to full plugin documentation when product site is ready so a user would be able to understand what the plugin does, how AMP works and why they should use this tool.

cc: @jwold @jillchu

jwold commented 6 years ago

@postphotos thanks for adding definition to this. This is really helpful for moving forward. When should we plan to have this ready for development to pickup?

kienstra commented 6 years ago

Question About Design

Hi @postphotos, Thanks for working on this.

Is there someone that can work on the design from AC2 and AC3? It would really help to have this ready for development soon.

Thanks, Leo!

postphotos commented 6 years ago

Hi @kienstra! We have two different designs in progress (@jwold @jillchu) a couple of questions right now around how much effort we can place toward settings.

There's a chance we may minimize the effort here to focus on what is easiest to release for v1.0-RC1, I'll let you know when I know more. 😄

kienstra commented 6 years ago

Thanks, @postphotos!

kienstra commented 6 years ago

In Progress

Though we can be flexible in changing the copy of the notice, I'm beginning development on this.

kienstra commented 6 years ago

PR Has Placeholder Message

PR #1442 has a placeholder message, which can be dismissed. Once it's dismissed, it won't display again for that user.

postphotos commented 6 years ago

Hi @kienstra and @jwold - for AC1, the final proposed wording we have is as follows:

# Welcome to the AMP for WordPress plugin v1.0
Thank you for installing! Bring the speed and features of the open source AMP project to your site, the WordPress way, complete with the tools to support content authoring and website development. 

## What's New
From granular controls that help you create AMP content, to Core Gutenberg support, to a sanitizer that only shows visitors error-free pages, to a full error workflow for developers, this v1.0 release makes it easier than ever to bring a rich, performant experience to your WordPress site via AMP HTML.

kienstra commented 6 years ago

Thanks, @postphotos! That looks good.

jwold commented 6 years ago

@kienstra

I'd like to suggest the following changes to the welcome banner (note that I changed a few lines of text as well). What do you think?

And the icon:

icon.svg.zip

cc @postphotos

jwold commented 6 years ago

@ThierryA, @amedina, @postphotos:

We had a meeting this morning to chat about changes to this notice, anything we're missing? Or does this look good? Thanks!

icon_r2.svg.zip

And the text from the notification:

Welcome to AMP for WordPress

Bring the speed and features of the open source AMP project to your site, complete with the tools to support content authoring and website development.

From granular controls that help you create AMP content, to Core Gutenberg support, to a sanitizer that only shows visitors error-free pages, to a full error workflow for developers, this release enables rich, performant experiences for your WordPress site.

kienstra commented 6 years ago

Hi @jwold, Thanks, this looks really good.

Where would the 'Learn More' link go to?

jwold commented 6 years ago

I was thinking the learn more link would go to the Product Site

postphotos commented 6 years ago

@kienstra as product site won't be ready until likely after RC, we should (for v1.0-beta4 purposes) not include the button. 😄

I broke out the CTA subtask into its own AC, and when it's ready we can move this forward.