WordPress.org

Make WordPress Core

Opened 7 weeks ago

Closed 7 weeks ago

Last modified 2 weeks ago

#53786 closed feature request (invalid)

Improved Gutenberg configuration possibilities for custom theme developers

Reported by: adfisch Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords:
Focuses: Cc:

Description

Dear WordPress core team,

I have done some research before and hope this post is not a duplicate (at least I couldn't find anything related). I've been a custom WordPress theme developer for small businesses for quite some time now. While I'm not one of the oldschool developers who tends to generally dislike Gutenberg (and I am actually pretty happy with it), I feel that some of my requirements have been overseen. Therefore, I finally took the time to make this improvement suggestion. Maybe others feel the same way.

When I create individual custom themes for small enterprises, there are two important aspects:

  • The budget is usually quite limited. This means that I can only provide the HTML and formatting for a certain amount of page elements. In order to prevent usability issues I need to be able to limit page editing options to the functionality that is supported by the frontend of the theme.
  • The Corporate Design guidelines usually provide very strict formatting rules. This means that a lot of default WordPress block types usually provide too much functionality. For instance, employees should not be able to choose font colors that are not mentioned in the guidelines etc.
  • There's usually not enough budget to evaluate which adaptions need to be done by the theme ecery time WordPress updates.

While I can use the allowed_block_types_all filter in order to reduce the block types to the supported ones, I find it very difficult (if not impossible) to define, which configuration options are available within a certain block type. It would be awesome, if I could enable/disable color pickers, font pickers, set available formatting options, the maximum amount of columns available in the columns block etc. simply by using a PHP filter.

Also I would suggest two different feature activation modes: By default, new configuration options for core block types are automatically added. Theme developers, however, should be able to change this so that block types only show the configuration options that are explicitely activated. This means that we would not have to update the theme everytime WordPress/Gutenberg comes with a new setting.

I've seen so many themes on the market that use their own page builders. Sometimes I feel the above mentioned issues are one reason for this because there is too little control over the editor. Even I sometimes recreate the simplest block types in order to gain more control and not to get surprises on updates. Maybe my suggestions make more theme developers use the native Gutenberg. I'm looking forward to receiving your feedback.

Change History (2)

#1 @adfisch
7 weeks ago

  • Resolution set to invalid
  • Status changed from new to closed

Sorry, just realized the new theme.json in WordPress 5.8 is pretty much what I had been asking for. :-)

#2 @desrosj
2 weeks ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.