apostrophecms / apostrophecms/apostrophe

3.0: UX of Widget Editor Drawer

Open
#2,920 6 comments 0 reactions 0 assignees View on GitHub
enhancement v3
Dominant language
JavaScript
Stars
4.6k
Forks
650
Avg merge
19h 21m
Merged PRs (30d)
23

Description

Playing around the Widget Editor drawer, I had 2 suggestions to have a better user experience.

1. Allow to possibility to add text bloc and separator
For widget with multiple or unclear options, it could be useful to be able to add descriptive text to help the end-user. The integration could be in a standalone bloc of a `description` option. Separators could also be added to help organize widget with multiple options.

```
fields: {
add: {
complexOption: {
type: 'boolean',
label: 'Label',
description: 'More information related to this field. It could be displayed as muted text under the label or with a "?" icon next to it.'
},
complexOptionText: {
type: 'abstract:text',
content: 'Adding more flexibility, we could have a bloc by itself.'
},
separator: {
type: 'abstract:separator',
}
}
}
```

2. Add an option to `area` to not render in the Widget Editor drawer
Since some area bloc can be pretty complex, it can become a little awkward to display it in the small drawer.

Really having fun working with V3 so far! I'm really looking forward to it!

Thank you!

Contributor guide

Open the contributing guide

Research direction

Start with the Widget Editor drawer described in this issue and review how widget fields and area blocks are currently rendered. Clarify the scope and acceptance criteria for descriptive text, separators, and hiding an area block before implementation. Done means the agreed drawer behavior works consistently for the affected widget configurations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.