Sure.. I have created a package with 2 teaser components - one using teaser and other one with experience. Here is the link:experience-campaign.zip - Google Drive Check page : http://localhost:4502/cf#/content/geometrixx-outdoors/en/men/coats/edmonton-winter.html - In first component, I have using c...

You can take a look at my comment on this Re: How to add multiple rootPath in Coral 3 Pathfield 

I am not sure if and how that can be done..

It depends on the campaign structure. If all are under a single campaign, use teasers and campaign path would be used to resolve these. If they are spread across different campaigns, use "experience". Instead of "campaign path", "location" in teaser component is used to resolve experiences.

You can cache the necessary things in JCR..Load dropdowns from JCR, if not there -> call API.. Once API returns, store the info in nodes again...

smacdonald2008​: This is just a clarification and not the correct answer. The issue is still there

You can overlay or extend "/libs/cq/workflow/components/model/participant" and update the dialog as per your needs

You need to locate the first resource and then iterate over its properties... So, from component 2, you should get its parent..something like resource.getParent()... this is common parent for both your components... then do parentComponent.getChild(<first component path>). Now that you have it, you ...

You can check Adobe Experience Manager Help | Configuring Adobe Experience Manager Touch UI Rich Text Editors . Looking at the screenshots there, I see the "link" option in the toolbar

Give every section a name..This should be authorable. So whenever author creates a section, new  name needs to be assigned to it. And segment definition should also use same name..In terms of code, you can set section name authored and set this value. This should take care of everything.