Open jordanlev opened 8 years ago
If you choose "Hide" when configuring a fieldset (or add hide: true
to the file), it won't show up in the "New Page" overlay.
But point taken, I'd definitely like to think through an improved UX on organizing fieldsets.
It would really improve the editing UX if fieldsets could somehow be isolated to specific content types or fields within pages/collections/etc.
For example, some fieldsets are for "page types" or "post types" or "entry types" (in the parlance of other CMS's), so they should be choosable by the content author when adding a new page via the Control Panel. But other times you have an actual field in a page that is of the "fieldset" type, and this is more of a "content block" or "matrix field" or "advanced custom fields" kinda things (again in the parlance of other CMS's), so that they should only be available when the content author is editing a field that is of the "fieldset" type within a specific page (or global or collection or whatever).
As it stands now, it's really weird to put such a long and confusing (and potentially site-layout-breaking) list of possible fieldsets in front of the content authors when they go to edit sites.