Okay, if experience fragment component is loading fine for you on the react app. The easiest way is to create a proxy component that extends experience fragment and call it Popup Modal, and override any labels or fields in CQ Dialog. At this point if you map your new proxy component to react compone...

Have you managed to get experience fragment working with react spa to start with? By default experience fragment when included in page will be returned as Json and not html. So you may need to explain how you are intending to obtain html. There are ways to achieve but then markup is generated by sig...

Just to confirm this theory, did you test using local host instead of a real env? It might confirm if it's an issue with replication user access for target publisher or if it's something else. And just to understand are you rendering to osgi config nodes or conf folder items or something else? 

Looks like I have to overlay all child nodes also for the component along with component properties also for the overall functionality to work as expected. But just in case if you see a better way to handle this, feel free to advise. Thanks 

If you are building apis that accept different parameters or may be upload some to process before responding back you can comfortably use path based servlet. Sling doesn't discourage path based servlets all together. But suggests usage of resource type based servlets when you intend to perform actio...

Solutions provided before me perfectly works fine. But the question is what's the intent. Are you trying to build a search component or something like that? Understanding the intent for retrieving all the pages without any filtering criteria. Can you please breif on that. 

Dear Community, I have a very unique scenario for which I am running out of ideas and suddenly realized there are certain things that require overlaying or extending done in a specific manner. Here is the use case I am dealing with. We had to alter responsive grid markup to include a few extra tags ...

My suggestion is, atleast for the initial setup until u are able to get the integration working create a new maven module with the dependencies you mentioned and have all your maven dependency jars embedded within the jar. Now this maven module can export only the packages you need in your code. Yes...

If you can explain a bit more on the requirement that will be great. Is the idea to use multiple react apps to load components in different areas? Or may be do a hybrid with some Content from traditional aem comps and rest from react? May be I don't understand the overall mfe architecture bit atleas...