[wp-trac] [WordPress Trac] #50214: Consider introducing the concept of "Editors"
WordPress Trac
noreply at wordpress.org
Wed May 20 15:55:55 UTC 2020
#50214: Consider introducing the concept of "Editors"
-----------------------------+-----------------------------
Reporter: johnstonphilip | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version:
Severity: normal | Keywords:
Focuses: |
-----------------------------+-----------------------------
The recent release of the Iceberg Editor plugin
[https://github.com/useIceberg/iceberg-editor] (built on Gutenberg) has
got me thinking about the concept of "Editors" and Publishing flows. The
REST API opens up a huge world of possibilities in regards to
editing/publishing experiences. WordPress core itself currently has 2
"Editors" (until at least 2022, perhaps longer):
- The Block Editor (Gutenberg)
- The Classic Editor (5+ million installs)
There are many other plugins which introduce other Publishing experiences:
- Iceberg (https://github.com/useIceberg/iceberg-editor)
- Elementor (5+ million installs)
- Divi
- Beaver Builder
- etc
If WordPress embraced these Publishing flows with a proper
Editor/Publisher Registry, it would allow all of these amazing Publishing
experiences to be used together, with the user being empowered to pick the
right tool for the right job.
This would even open up possibilities for plugins like WooCommerce, where
a "Product Editor" could be created for "Products", allowing a completely
streamlined experience for publishing products.
Every type of content (and especially for post_types) could benefit from a
streamlined publishing experience. For example, for publishing videos, a
Video Editor (plugin) could emulate YouTube's step-by-step publishing
experience.
If WordPress core created a proper registry for Editors/Publishers, it
could empower both developers and users to build streamlined and focused
publishing experiences right into the WordPress dashboard in a way that a
single Editor never could.
This seems like a natural next-step in the WordPress journey, especially
watching the explosion of creativity and user-response (millions upon
millions of installs) happening around publishing experiences and flows
for WordPress.
A flow for creating a new post might look like this:
1. Click on "Create new post"
2. If multiple Editors are installed+registered for this post_type, show
an Editor Picker. If only a single Editor exists for this post_type,
immediately show it.
3. You now experience the publishing experience provided by that Editor,
and publish.
4. Future edits to that post will automatically use the Editor initially
chosen.
5. When viewing your existing posts in the posts UI table, a column for
"Editor" is shown to indicate "Gutenberg", "Elementor", etc.
I think ideally this registry is something that would exist in WordPress
core, giving developers an official API to work with, and a consistent
flow for users to pick their editor of choice.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/50214>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list