search

Automattic / gutenberg-ramp

Control conditions under which Gutenberg loads - either from your theme code or from a UI
https://wordpress.org/plugins/gutenberg-ramp/
76 stars 15 forks source link

Cross linking an issue in regards to additional editing options #57

Closed paaljoachim closed 6 years ago

paaljoachim commented 6 years ago

Hey

I just want to cross link this issue as a possibility... Making it easier to transition to Gutenberg https://github.com/WordPress/gutenberg/issues/7060

Using Gutenberg on some specific post types it would be good to have the opportunity on the frontend when clicking edit to have it open in either Gutenberg or the classic editor.

maevelander commented 6 years ago

Hi @paaljoachim - thanks for your suggestion.

it would be good to have the opportunity on the frontend when clicking edit to have it open in either Gutenberg or the classic editor.

This is possible using the Classic Editor plugin. Screenshots: classic-editor-1 classic-editor-2

With this in mind, I do not see a great need to replicate this functionality in Ramp.

In fact, Ramp plugin was designed for a slightly different use-case - to fit the needs of complex, often highly customised authoring workflows like those we see on large enterprise sites at WordPress.com VIP. In these cases we explicitly do not want authors able to choose which editor to use (Gutenberg or Classic). Rather, that decision is set by the theme developers at a higher level, and locked on a post type or post_id basis.

So for both these reasons I don't think this is something we'd incorporate into Ramp.