Skip to content

make block types controlpanel wider#8041

Merged
davisagli merged 3 commits intomainfrom
blocktypes-styles
Mar 24, 2026
Merged

make block types controlpanel wider#8041
davisagli merged 3 commits intomainfrom
blocktypes-styles

Conversation

@jnptk
Copy link
Member

@jnptk jnptk commented Mar 23, 2026

Before After
image image

@jnptk jnptk requested review from davisagli, sneridagh and tisto March 23, 2026 10:41
@tisto
Copy link
Member

tisto commented Mar 23, 2026

@jnptk changelog entry pls.

@davisagli @sneridagh I asked @jnptk to record a screencast for the release of Plone 6.2. I noticed the implementation of the table is off with our lo-fi prototypes. Therefore I asked Jonas to make those amendments.

Copy link
Member

@tisto tisto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks a lot better! Let's merge and release asap.

Copy link
Member

@davisagli davisagli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Asking @sneridagh to review since he did the first pass on these table styles. It makes sense to me.

@sneridagh
Copy link
Member

@tisto @jnptk @davisagli in which sense this is better? I have a hard time trying to figure out which row corresponds to what with this distance...

@sneridagh
Copy link
Member

sneridagh commented Mar 24, 2026

@tisto @jnptk @davisagli to be fair, the whole concept of control panels need a profound review... I just checked and every one of them uses different styles, wrappers, etc... Let alone to know if their settings make sense or have any effect on Volto. It's a complete mess.

@davisagli
Copy link
Member

davisagli commented Mar 24, 2026

@sneridagh True. It's always hard to find time to prioritize improving the UX of the control panels compared to the rest of the CMSUI. Maybe we could come up with a representative high-fi design of one control panel, a list of guidelines for how they should be, and then bring up making them more consistent as a possible work area for the Beethoven Sprint. I think one reason it's been hard to make progress on them is that we don't have a clear goal.

@tisto
Copy link
Member

tisto commented Mar 24, 2026

@sneridagh I agree and we can discuss how to do a full overhaul of the control panels in the future.

However, we have a low-fi prototype for control panels with the table configuration that is reflected in this PR. This low-fi prototype uses a full-width table like all the other control panels use. For both consistency and UX reasons I would like to merge this PR. Otherwise we have a wild mixture of tables.

So let's please merge and release this PR so that we can make a screencast for the upcoming Plone 6.2 release and move on.

@tisto
Copy link
Member

tisto commented Mar 24, 2026

@davisagli we have a bunch of lo-fi designs for control panels ATM. I would say for the control panels we do not need a hi-fi design. However, we would be willing to sponsor those efforts if necessary. Any hi-fi design will be based on a low-fi prototype though. Therefore the configuration of the table is not going to change. Good UX means consistency. Tables with different widths for every control panel are not consistent.

@davisagli
Copy link
Member

@tisto Personally I agree with you, but I thought Victor's concern (not being able to see clearly which row a number is in) was also valid. I suggest we merge this, but also ask a designer for input on this particular question.

@tisto
Copy link
Member

tisto commented Mar 24, 2026

@davisagli @sneridagh sure. I am not saying that the solution we have right now is perfect. As said, I am open to re-visit this at Beethoven sprint and further improve things. I agree with @sneridagh that we need a full overhaul of the control panels, both technically as well as UX/UI wise.

@davisagli davisagli merged commit add36ed into main Mar 24, 2026
78 checks passed
@davisagli davisagli deleted the blocktypes-styles branch March 24, 2026 20:02
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 this pull request may close these issues.

4 participants