Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WordPress 4.9: Consider "Try Gutenberg" dashboard notice #1656

Closed
jasmussen opened this issue Jul 3, 2017 · 4 comments
Closed

WordPress 4.9: Consider "Try Gutenberg" dashboard notice #1656

jasmussen opened this issue Jul 3, 2017 · 4 comments
Labels
[Type] Question Questions about the design or development of the editor.

Comments

@jasmussen
Copy link
Contributor

This is more of a meta ticket. It's been suggested that Gutenberg could reach WordPress in version 5.0. What form exactly this would take (opt-out?) has yet to be discussed. But even prior to that, reaching WordPress hinges upon the plugin getting a huge amount of installs; 100.000 has been suggested.

Should we explore putting a dismissable dashboard notice in WordPress 4.9, that says "Try a preview of the new WordPress editor", which when clicked would allow you to install the plugin?

@jasmussen jasmussen added the [Type] Question Questions about the design or development of the editor. label Jul 3, 2017
@buzztone
Copy link

buzztone commented Jul 3, 2017

While we probably can't say at this stage if 100,000 active installs is realistically achievable, it's certainly a worthwhile target in my opinion. While 10,000 - 20,000 (currently 1000+) might be sufficient to get widespread usage & feedback, 100,000 active installs would demonstrate support within the community for the advantages Gutenberg offers.

For comparison I'd be interested to see how many downloads MP6 had before it was merged. MP6 certainly had a significant number of users & a very extensive review process. I believe this contributed significantly to acceptance of the MP6 changes when merged. As I recall I was using the MP6 plugin on many sites, before it merged, for the advantages it offered.

Shiny Updates was another feature plugin that I was already using on most sites before it merged. This gave me direct first hand confirmation that Shiny Updates worked as I waited patiently for the merge into core.

@hedgefield
Copy link

I'd be all for it. We were otherwise planning to write a little plugin that sets Gutenberg as default so our content team can get used to it and provide feedback.

@melchoyce
Copy link
Contributor

Should we explore putting a dismissable dashboard notice in WordPress 4.9, that says "Try a preview of the new WordPress editor", which when clicked would allow you to install the plugin?

I think we could even get this into the next point release.

@jasmussen
Copy link
Contributor Author

This is done! Hooray!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Question Questions about the design or development of the editor.
Projects
None yet
Development

No branches or pull requests

4 participants