Skip to content

[Feature Request] Entry field default selection #7864

@TheFunkyMonk

Description

@TheFunkyMonk

Description

We have a pretty common setup for creating new landing pages in most of our sites where the author can add a hero, a set of "modules" from a Matrix-style block field, and in this case, a large CTA at the bottom of the page that contains some copy and a link to a different piece of content.

Screen Shot 2021-04-30 at 2 03 19 PM

Since the author is going to use the same CTA 90% of the time, we've set the CTA field up as an entry selector for a "Footer CTAs" channel containing an entry containing the CTA content so they don't need to re-write the headline/copy for the CTA every time they want to use the default one.

By default, we'd like all new landing pages to link to the entry we've already created in this channel while giving the author the option to either remove it or replace it with a different entry they've created in the "Footer CTAs" channel.

Current Behavior

Currently, the only ways to accomplish this default selected entry behavior are:

  • Hardcode the default entry into the template
  • Create a global field to set as the default entry

Both of these are a little more confusing from an authoring perspective, and would require an additional lightswitch toggle to disable/hide the CTA if they want a page to not include a CTA at all.

Requested Behavior

Entry fields support a default entry selection.

entry-select-default

This way, we could eliminate the need to manually select an entry every time a new page is created, as well as clearly indicate when an entry should not be shown.

Metadata

Metadata

Assignees

No one assigned

    Labels

    content modeling 📓features related to content modelingenhancementimprovements to existing features

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions