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

HCMS: Configure Dynamic Zone and Object field to be expanded by default #4109

Open
ma-schmidt-de opened this issue May 3, 2024 · 1 comment

Comments

@ma-schmidt-de
Copy link

ma-schmidt-de commented May 3, 2024

Is your feature request related to a problem? Please describe.

In our customer project, we see the requirement to always render a dynamic zone open with it's content. Right now, every time a DZ is rendered, it is collapsed and editors always have to spend an additional click to open it and see the inner content.

Describe the feature's behavior.

To improve editor UX, it would be best to configure a DZ or an object (accordion renderer) to always be expanded when rendered initially.

  • The AccordionItem react component used in dynamicZoneRenderer.tsx does indeed support an open property which I expect does open the accordion item by default
  • I'd say, there are only two things we need to do:
    • Extend the CmsModelFieldSettings by an open?: boolean attribute or use it's definition [key: string]: any to support the new open configuration.
    • Pass the value of the open configuration to the open property of the AccordionItem in the dynamic zone renderer and the object renderers (single & multiple). Something like:
<AccordionItem
  title={title}
  description={description}
  className={className || defaultClassName}
  open={field.settings?.open || false}
  >
    {children}
</AccordionItem>

Describe alternatives you've considered.

No response

@ma-schmidt-de
Copy link
Author

My considerations are based on the case that the content model is defined in-code.
Additional masseurs have to be taken in order to enable the open config for the no-code content model editor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant