Hi @Tessa_learner1  If that is the case as mentioned by @salamswapnil use Tagmanager API read name from the parsed Tag object it should solve your problem.  

You can write the custom logic in the workflow process step to activate the child nodes/pages as well. This article shows how to replicate from servlet same can be applied in workflow process step. https://aem.redquark.org/2018/10/day-19-replication-api-in-action.html Hope this is helpful

Do you want to read them from the component and display on the page as text ? If that is the case which one do you want to display is it tagname or tagId ? Can you explain more on this ?

Below link explains how to create and organize the pages https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/sites/authoring/fundamentals/organizing-pages.html?lang=en Hope this is useful

Hi @gargkrishna  This article explains writing JUNITS for sling model and as well to servlet class refer this to get more information. https://taylor.callsen.me/unit-testing-aem-sling-models-and-servlets/ Hope it is useful.

Yes, where exactly you are applying them I hope it is on page properties?

1. Write servlet which is common to all the filter  Ex: /aem/search/servlet 2. Servlet should be responsible for capturing the type of filter user selected (filter1, filter2) 3. Based on the filter/filters selected have a service with different query builder queries. 4. Map the result back to UI   B...

You have to do all the configuration setup in Author instance and publish them. Other option is to take the package of ACLs and install them in the publish environment.

If the data is in AEM using querybuilder API with proper indexed data should work fine. Make a custom servlet which call the different service layers depends on the filter and retrieve those back to front end as JSOn object and make every subsequent call be an asynchronous call to the servlet.  

Simple Funda for committing the changes to git for anything in AEM is take the package for those content extract the zip once package is downloaded and then copy the structure in the respective project folder. Add the filter in the module filter.xml to make sure it is available in the next deploymen...