I believe you just have to create a new Java POJO class which will implement LaunchPromotionParameters interface. Implement the methods of the interface and pass the POJO object to the promoteLaunch method. 

Didn't get your question. You are required to create custom CSS for styling components in AEM. You can use any framework or language to build that CSS and then use a front end development workflow process to compile and deploy it to AEM as a clientlib. You can follow this page for more details on fr...

I think you can achieve the same with following API  - https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/javadoc/com/day/cq/wcm/msm/api/LiveRelationship.html

Yes you will have to write some backend code for getting request attributes. I would recommend that you write a generic backend class which can be used for fetching any request attribute. You can refer to following example - http://www.6dglobal.com/blog/accessing-request-variables-sightly-2015-01-23...

Both the common code and brand repos will be managed in org git repos. We plan to sync these repos with Adobe GIT repos via custom Jenkins Pipeline. You can consider common code just like core components library and it lives in its own repo as it is maintained independently of brands code. Every bra...

Hi @shelly-goel Thanks for your inputs.  As I said, I have got multiple brand AEM code repos and a shared common components repo. Each brand will have its own code as well and it will be deployed to a program and in Cloud Service. The common repo code will be included as sub package in the brand pac...

I have got a repo of all common components which are deployed to multiple brand websites . If I have to migrate this to AEM cloud service then I will create a single brand project based on the new AEM archetype. But then I also need to embed the common components package with the brand package. The ...

Thanks!

We have got requirements to implement UGC related features like forums, comments, blogs etc on ourwebsite. We got to know from Adobe rep that Adobe has discontinued AEM communities and Adobe Livefyre products as they are not selling new licenses anymore. Does anyone of you have any other recommended...

Content fragments can now be exposed via new AEM HTTP API.[0]Is it okay to expose content fragments using this api to external applications or should we expose them via experience fragments, content fragments component and sling model exporter? Any recommendations ? With sling model exporter we have...