Timeline for Adding custom properties to a digital experiences site
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2022 at 15:13 | history | reopened |
Kris Goncalves Shamina David Cheng Derek F nbrown |
||
| Mar 15, 2022 at 17:47 | history | edited | Mark Hansen | CC BY-SA 4.0 |
added 87 characters in body
|
| S Mar 15, 2022 at 15:54 | review | Reopen votes | |||
| Mar 18, 2022 at 15:13 | |||||
| S Mar 15, 2022 at 15:54 | history | edited | Mark Hansen | CC BY-SA 4.0 |
added 289 characters in body
Added to review
|
| Mar 15, 2022 at 11:27 | history | closed |
Phil W identigral glls Oleh Berehovskyi Sander de Jong |
Opinion-based | |
| Mar 13, 2022 at 6:28 | answer | added | sumit bhatt | timeline score: 3 | |
| Mar 12, 2022 at 23:12 | review | Close votes | |||
| Mar 15, 2022 at 11:27 | |||||
| Mar 12, 2022 at 22:37 | comment | added | Phil W |
For me the most portable mechanism is to simply parameterize the components (adding @api properties) that you set as needed in each site's component usage (as defined in the properties for the components in the various page views). Yes, each component use that needs to vary must be explicitly parameterized, but this doesn't use non-portable values like the network ID or changeable aspects like the URL.
|
|
| Mar 12, 2022 at 19:36 | history | asked | Mark Hansen | CC BY-SA 4.0 |