Hi @SurabhiAc3 Over here you can create your own component and in the component definition, adjust the components to be shown to the author to avoid confusion with the multiple components.   { "component": "select", "label": "Option Type", "name": "fil...

Hi @JananiVe Can you please elaborate the steps you have followed over here. Usually post below the steps: 1. Create the repo from the boiler plate i.e. https://github.com/adobe/aem-boilerplate 2. run the command npx aem up --url https://dev--<eds-repo>--<org>.aem.live/, it works   The details relat...

hi @AbhilashMo4 IMO, you can create your own custom component over here, and leverage the options for selecting and decorating the block  { "component": "select", "label": "Button Type", "name": "filter_ButtonType", "valueType": "string", "options": [ { "name": "option1", "value": "Option 1"...

Hi @mguerriero    I tried it out by adding the ?ref=<branch-name> and I am getting the option to author the changes done for the authoring, otherwise you can do it via the alternate approach   There are HELIX5 configurations by which you can bind your environments with the respective branches and th...

Hi @MKarthik87   There is a way to do this in X-Walk. Over here you can create multiple branches & authoring environment. With Helix5 configurations you can map the different branches to the respective environment with 1-1 mapping. This way all the different environment will point to different envs ...

Hi @shikhasoni1 Seems like there is an issue in the logic where you are trying to read the items from the by-default DOM created in the EDS within your decorate block and there is an error while getting the intial value itself due to non-mandatory field.   The statement would look like const [text,...

Hi @Chaithanyaj  Can you please check that the techacct associated with the HELIX5 configuration is correct or not, usually we see that the content is not rendering on the EDS, when the creating the site or updating the site config the techacct is mapped incorrectly. "access": { "admin": { ...

Hi @josephambrose  You can hit the url https://admin.hlx.page/auth/adobe and from here it will ask your credentials. Once done it will show you sometime like  Now navigate to chrome tools -> application. From the cookie you will be able to get the authorization token. Hope this helps! Thanks.    

Hi @rahulda2  There is no direct way of editing the content fragment within the Universal Editor.  And can you please add more details what is the exact use case of editing CF directly in CF, I am assuming you must be using the CF via graphQL in your X-Walk application.  If you wish to use the editi...

Hi @sofiyans8042875  You can create a block (Buttons) and blockItem (Button) { "definitions": [ { "title": "Buttons", "id": "buttons", "plugins": { "xwalk": { "page": { "resourceType": "core/f...