Pro 6.0 rc1 - access to "customize" tab for components

Beta
#1

I wonder if there is a way to toggle in a component export that the Customize tab of the element can be kept in? My specific use case is being able to add conditions to a component, which currently has to be achieved by wrapping it in a Div, which then causes issues with the flexibility of being able to drag components around easily.

Thinking about it some more, I can understand not wanting to open up the ID, Class and Custom CSS sections for a Component, as the whole point is to abstract the design of these things, but the Hide During Breakpoint and Conditions options would likely be specific to the use-case and implementation of each copy of a Component.

Maybe this is a conversation to be opened with many other beta users too. Not sure what the best solution might be

1 Like
#3

Howdy, @arthurodb!

It sounds like what you’re after is the “Allow Customization” feature of Components, which is outlined in our draft documentation here under “Advanced Component Usage”:

From the article directly:

Allow Customization: Makes the ‘Customize’ controls accessible when using the Component in other builders.

One thing to note here is that this option is only available on a Component Instance, meaning when you use it in another document. If you add a Component to a page and then open its Element Manager, you will see this option. If you enable it, you will be able to adjust the Customize controls for that instance only.

Our thinking here is that this might not be something you want to turn on all the time for every instance of the Component, especially depending on how your team might be working with these, so you can simply opt into it as needed.

While I cannot guarantee anything, I would be curious to know your thoughts on whether you’d prefer to see this as an option at the Component level itself rather than the Instance. I believe there are some limitations with what the instance can “know” about the Component once it is placed, which is why this is only available on an instance by instance basis, so because of this adding it as a base option on the Component itself might not be possible at this time.

Thanks!

1 Like
#4

Oop! Now that you point that out again, I even have a vague recollection of noting it in my earlier experimentations. Sorry that it totally slipped my mind!

Leaving it on the Instance level makes total sense actually come to think of it, as the cases for the Customize controls are probably almost always specific complex layouts involving loopers, or else specific unique styling in a unique location.

All seems to work well as it does already!

Cheers

1 Like