Hi @shivakrishna36 - Were you able to confirm which solution worked for you. After spending days I found the root cause. Its the browserlist config in package.json thats causing the issue. Please see link below for the details. https://github.com/adobe/aem-react-editable-components/issues/206#issuec...

Is your intention just formatting or display certain styles in a different icon? For the latter part the links you see from @Harwinder-singh may be a starting point. But for formatting, I think you should be able to override the display styles to show each option group in a column through css change...

What version of Java are you using. If you are using jdk 8 and using latest maven compiler compiler plug in with release tag in it perhaps this could be a potential issue. Let us know these details so we can guide you. We use jdk 11 and using release 8 or 11 works fine as part of build process. Rele...

I assume your understand is right. Content fragments don't save the properties e.g. Elements directly, and in this case ideally graphql would have been the right way to query. But again that requires a custom reporting Ui. @kautuk_sahni - Requesting for assistance from other experts on content fragm...

Like @joerghoh mentioned, based on title or your post I assume you are using core components and use Adobe data layer. Now you can use delegation pattern to additionally add more properties that can either be consumed by HTL code (you can choose to include as part of custom header libs.html) to expo...

I believe some part of it is addressed in universal editor.i mean editing the cf directly from referenced page opens on a modal without having to navigate down the full DAM path. But definitely helps nested cf links 

@Mahedi_Sabuj - I worked on getting the style system attributes integrated into sling models couple of years back for assisting SPA, and eventually updated both react and angular editable components. Recently rolled out the support in Spa 2.0 as well. I will soon add a blog post on consuming the sam...

@shivakrishna36  - Even I encountered this issue and struggling to find root cause. But if you are in earlier stage of development or POC, please use @adobe/aem-react-editable-components v2.0.4 instead of any other latest version. But if you intend to use the latest version, you can perform steps be...

I assume it's ootb behavior that handles model.json resolution for pages in that manner so we can avoid appending jcr content . One option I can think of is writing a sling filter to forward the request to /jcr:content.custom.json when selector is custom and incoming path is indeed a cqpage. But aga...