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

Add data entry focused editing mode #6803

Closed
travislopes opened this issue May 17, 2018 · 2 comments
Closed

Add data entry focused editing mode #6803

travislopes opened this issue May 17, 2018 · 2 comments
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript

Comments

@travislopes
Copy link
Contributor

For Gutenberg to truly succeed in the manner it needs to, I believe there needs to be a dedicated data based mode added alongside the existing code and visual modes.

Up to this point, the focus of Gutenberg has been to improve the experience of writing a post within WordPress. This will cover the primary usage of a lot of WordPress users, who use WordPress to mainly write posts and publish pages. However, when proposing an overhaul to what is arguably the most important screen within WordPress, the majority of use cases have to be considered and covered. The tools provided today do not accomplish that.

Plenty of WordPress plugins and custom themes utilize custom post types that are not focused on writing a story, but on entering data that can then be rendered appropriate by the theme or utilized via various internal APIs or the REST API to connect with other objects across the site. Look at the edit Product screen for WooCommerce. Sure, there's the main editor at the top for writing the product description, but most of the important data related to the product (pricing, taxes, inventory, shipping, etc) is entered in through a metabox.

With a dedicated data entry mode, Gutenberg can be used by more data focused post types. Rather than presenting a BlockList where the user can only insert blocks that are saved to the post object's content property, a new MetaboxList component could be rendered allowing developers to insert their own Metabox components that allow the user to enter in data related to that post type. (They do not need to be referred to as Metaboxes.) This provides a better toolset for developers to create more complex experiences than they can with today's editor screen and jQuery combo along with being able to transition to the new primary user interface of WordPress.

@danielbachhuber danielbachhuber added the Framework Issues related to broader framework topics, especially as it relates to javascript label May 18, 2018
@danielbachhuber
Copy link
Member

Hi @travislopes,

Thanks for the suggestion! I've filed this away in the Ideas project for future consideration. At this point in the Gutenberg development cycle, we're focusing on finishing the remaining features and then switching to bug fixing / polish.

@ZebulanStanphill
Copy link
Member

Possibly related: #3330, #4441, and #6442

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript
Projects
None yet
Development

No branches or pull requests

3 participants