SOLVED: Components first impression and a bug

Okay, first impression:

First and foremost. Great that it finally landed. Please make it very clear that we are in edit mode. The purple should primarily appear there. I find it acceptable in the structure panel, but having the instance look nearly the same as when in edit mode is confusing, to say the least. Additionally, exiting a component should be very clear as well. I often exit by selecting something else on stage, which I find confusing and disorienting. I would prefer to see an exit button and a purple bar across the entire edit panels only in edit mode.

I have a suggestion: How about some modes for visibility of the rest of the page while inside a component:

  • Visible (like it is now), so it shows all the elements on the page even though we are inside the component.
  • Faded, so all other elements that are not in the component are shown with reduced opacity or something like that.
  • Isolated, so it hides all the rest of the site apart from the components.

I had trouble adding new elements inside a component once it was created. I keep exiting the editing experience. Relinking properties is also not trivial, or I might be missing something. Okay, it seems I can’t link Rich Text yet. That is why I didn’t see the purple plus
 I guess the full extent of property types is still in the works.

Please don’t put the component description into a box
 It feels like a button. Maybe support Markdown in the description, as AI writes great documentation, and I’d like to preserve the formatting when copying such description over.

Bug: When dragging a button to the stage in a component, it just doesn’t show up.

Hi @MaxZieb,

first, thank you for testing and for your report. Let’s first check the bug
 yep, I can replicate it, and I’ve added it to the internal bug tracker.

About the suggestions, it’s worth creating separated topics in Feature Requests / Improvements , so that other users can also comment on them. That way we can gather user feedback the best. So, my suggestion would be that you do that :slight_smile:

Btw, you can connect property to “Rich text”, it’s just that the property needs to be “Rich text” type.

Thanks.
Matej.

To make it clear if you are controlling instance and main component I suggest to use two different purple color .
Strong purple => main component
Light purple => instance

Strong and light purple can be for example
Strong :

  • border purple
  • bg purple

Light:

  • border purple
  • bg purple semi transparent

That might be the problem. I think it should show the + always to link, but if there is no element it can link to, there should be an indicator like in the dropdown, e.g. “no properties” or even link to create a new property. Now it just doesn’t show the +.

Hi, yeah, that’s a nice idea. I’ve added it as an idea to our tracker :slight_smile:

Matej

Hello @MaxZieb,

We’ve implemented this feature in Bricks 1.12, now available as a one-click download from your dashboard.

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.12 Changelog – Bricks

Best regards,
Matej

Hey Matej, thanks! Much appreciated. Btw, it would be great if somebody initializes a new property through ‘Create new’ over the +. Then we’d also like to see the new property directly linked from the origin of creating it.

Hi,
yeah, about this idea, we talked about it internally but decided that. (for now), we will not connect it automatically.
I don’t remember what was the exact reason for this decision though.

Best regards,
Matej

Thank you for the feedback. Please reconsider this request in the next team meeting again as I’m not only posting on my behalf, I’m posting also on the behalf of some users of the Discord and feedback I saw from YouTube videos. As a user does make his intention very clear by going through the control that the property is created for that control should be linked. As you need to track from which control we are coming because we’re going to link it. We can also have a little back button or have the workflow after the creation redirect back to the control.