The Component Message takes up an awful lot of visual real estate in the builder, effectively de-emphasizing the parameters that show up below it. Given that parameters are likely to be used in this context significantly more than clicking to edit the component set, I’m wondering if this visual hierarchy should be changed at all (e.g. putting the parameters higher in the list, or maybe de-emphasizing the styling of the Component Message slightly, etc.)
Good points here. You’re right, the primary action will be using the parameters. The main purpose of that message is actually to emphasize the distinction of it being a component vs a normal element. The link (broken at the moment) is a nice bonus. We experimented with putting the message at the end, but it could be out of view if the list of Parameters is long enough.
We’ll think about this some more. I can see how it could feel like it gets in the way of the actual work that needs to be done. Maybe there’s a better way to strike the right balance of making it clear what’s being edited.
2 Likes
On a similar note here, when we in the Component Builder could there be the extra tab called “Parameters” with a button to edit parameters? (similar to how it looks when we add a parameter in the JSON editor)
Currently having to right click on the element then click on Edit Parameters seems a bit overkill. I know it’s the same amount of clicks but it feels like it fits in better as its own tab, specially because most of the times when we use component there will very likely be the use of parameter, in my opinion.
I know it’s a little awkward having to go through the context menu 100% of the time. It’s one of those areas where we’re in-transition. We don’t have all the features on the table to properly organize everything, but we have some completed features that need to be accessed right now. We most likely won’t have a dedicated button just for Parameters, but there might be a dedicated way to open the Element Manager quickly without needing the context menu. It kinda depends on where we land with the next wave of features. We know it’s going to necessitate a bit or reorganization to make everything easily accessible naturally.