Skip to main content
Post Reopened by Kris Goncalves, Shamina, David Cheng, Derek F, nbrown
added 87 characters in body
Source Link

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

We are using Aura Component attributes (as described here), but this approach does not let us edit the properties from inside the Experience Builder tool. See image below for the ListView2 component.

How do you configure properties so they can be edited from within Experience Builder?

Experience Builder Component

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

We are using Aura Component attributes (as described here), but this approach does not let us edit the properties from inside the Experience Builder tool. See image below for the ListView2 component.

How do you configure properties so they can be edited from within Experience Builder?

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

We are using Aura Component attributes (as described here), but this approach does not let us edit the properties from inside the Experience Builder tool. See image below for the ListView2 component.

How do you configure properties so they can be edited from within Experience Builder?

Experience Builder Component

added 289 characters in body
Added to review
Source Link

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

What would be the best way to implementWe are using Aura Component attributes (as described here), but this? Is there a best practice for setting and reading approach does not let us edit the properties atfrom inside the site levelExperience Builder tool. See image below for the ListView2 component.

How do you configure properties so they can be edited from within Experience Builder?

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

What would be the best way to implement this? Is there a best practice for setting and reading properties at the site level?

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

We are using Aura Component attributes (as described here), but this approach does not let us edit the properties from inside the Experience Builder tool. See image below for the ListView2 component.

How do you configure properties so they can be edited from within Experience Builder?

Post Closed as "Opinion-based" by Phil W, identigral, glls, Oleh Berehovskyi, Sander de Jong
Source Link

Adding custom properties to a digital experiences site

We are building components for our Experience Cloud sites. The components need to behave slightly differently based on the site they are used in. To implement the different behaviors, we want to our code (either JavaScript or Apex) to be able to read some custom properties from the site they are running in.

What would be the best way to implement this? Is there a best practice for setting and reading properties at the site level?