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

UX improvements for custom fields editor #18406

Open
orthagh opened this issue Nov 28, 2024 · 0 comments · May be fixed by #18577
Open

UX improvements for custom fields editor #18406

orthagh opened this issue Nov 28, 2024 · 0 comments · May be fixed by #18577
Assignees

Comments

@orthagh
Copy link
Contributor

orthagh commented Nov 28, 2024

Summary:

  • fields now include their label inside -> reduce width usage in the viewport
  • we remove the preview of the field nature (input/dropdown)
  • we keep preview of some attributes (mandatory, full width)
  • a side panel helps retrieve all fields and drop them into the viewport
  • a separate section permits the creation of custom fields
  • native and custom fields are clearly identified
  • A search input filters available fields
  • We have 2 states for a field in the viewport: default and selected
  • We show the controls for editing or hiding the fields only for selected state
  • grip for drag&drop is always shown (to be discussed, we may have the selected state also)

Note, it's a proposed design, If you have suggestions, time to make them is before starting dev.

Current design: https://design.penpot.app/#/view/7ad540b5-8190-815d-8005-57c26f8b15dd?page-id=7ad540b5-8190-815d-8005-57c26f8b15de&section=interactions&index=0&share-id=a0a8e792-b2d2-818e-8005-57d3e4d4a58d

Image

@orthagh orthagh self-assigned this Dec 2, 2024
@cconard96 cconard96 self-assigned this Dec 18, 2024
@cconard96 cconard96 linked a pull request Dec 18, 2024 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants