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...

Like @aanchal-sikka mentioned, if its in early stage go with Nested CF approach, as it allows querying the properties via GraphQL and probably is the reason Adobe may not have directly provided the composite multifield, since it requires its own schema or definition, leading to creation of a new cf ...

Was about to say the same. If the intention is just clientside, a custom clientlib doing validation is good. But since the post mentioned about pages created programmatically as well, I suggested the back end approach

I am assuming this theory but feel free to point out if there is an issue with my thought process. Hypothetically speaking. This may not be so straight forward but probably may require multiple customizations. Today no matter we create pages using Ui or backend, we may end up going with page manager...

It's not that hard. Just take a look at any sling filter. You have ability to add type selector extension. So you can attach model and Json as selector and extension. Now traverse through your Json, check if runmode is author and if wcmmode is edit (assuming this is only for inside author). Now for ...

Just like any other content creation api. Dedicate a node for all form responses. Now setup a servlet with postmethod which can be set as form action for react form and upon submission let the servlet create a new node with nt unstructured type for every form submission with all data and assign each...