Gutenberg interface without content editor

  • Steve Taylor

    (@gyrus)


    3 years, 7 months ago

    AFAIK if a post type doesn’t support ‘editor’, the edit screen is the classic style interface, without TinyMCE.

    Is there a way for a post type that doesn’t support ‘editor’ (as in, the post_content field is irrelevant) to still use the overall Gutenberg interface (for custom fields etc.)? Or is Gutenberg entirely based around the editor experience?

Viewing 1 replies (of 1 total)
  • Adrian Toll

    (@adriantoll)

    3 years, 7 months ago

    I’d like to know this too. The problem is defining custom post types that don’t need a content area, but do have custom fields. Currently the editing experience is disjointed because it flips between the Gutenberg interface for posts that have the content area and the classic interface for posts that don’t.

Viewing 1 replies (of 1 total)
  • The topic ‘Gutenberg interface without content editor’ is closed to new replies.

Tags