Post Editor: Wire up the dialog opt-in button to set the blog's editor to Gutenberg. [WIP] #27799
Conversation
kwight
added
[Feature] Post/Page Editor
|
That's a great PR description, thank you so much for your effort! Generated by 🚫 dangerJS |
kwight
added
[Status] Needs Review
kwight
force-pushed
the
update/gutenberg-opt-in-dialog
branch
from
c0f1f9a
to
b7fc25c
Compare
kwight
changed the title
|
@dmsnell I've updated this to use an action more in-line with our API discussions today – let me know if I've headed in the wrong direction, and feel free to push if you know more details! 👍 |
kwight
added
[Status] In Progress
and removed
[Status] Needs Review
client/state/action-types.js
Outdated
| @@ -212,6 +212,7 @@ export const EDITOR_SAVE = 'EDITOR_SAVE'; | |||
| export const EDITOR_EDIT_RAW_CONTENT = 'EDITOR_EDIT_RAW_CONTENT'; | |||
| export const EDITOR_INIT_RAW_CONTENT = 'EDITOR_INIT_RAW_CONTENT'; | |||
| export const EDITOR_RESET_RAW_CONTENT = 'EDITOR_RESET_RAW_CONTENT'; | |||
| export const EDITOR_SET_GUTENBERG = 'EDITOR_SET_GUTENBERG'; | |||
There was a problem hiding this comment.
we might want to double-check our naming here. if we are going to offer opt-out then something like EDITOR_SELECT or EDITOR_OPT_IN which takes a parameter specifying the editor experience might be more clear in its intent
|
@kwight this is going in the direction yeah that I'd expect. let's connect on Monday and check again after putting in the API having a Redux action is a good idea and probably necessary so we can adjust other UI concerns in Calypso about it. |
upcoming API work for a Gutenberg "opt-in" endpoint.
unnecessary sites schema changes.
kwight
force-pushed
the
update/gutenberg-opt-in-dialog
branch
from
b7fc25c
to
021393d
Compare
|
Replaced by #27893 . |
Upcoming API work will add an endpoint for setting a blog to use the Gutenberg editor. This PR stubs out an action to consider while the API work happens.
Testing instructions
/post/:siteand then "Learn more" in the sidebar's Gutenberg visual.TBD.