Please see this page in the CQ docs: http://dev.day.com/docs/en/cq/current/developing/mobile/responsive.html scott

Dispatcher does not cache pages that do not have an extension. I don't know of any way around this. scott

You might also consider limiting who can change the content of the parsys:http://dev.day.com/docs/en/cq/current/developing/boilerplates.htmlscott

msplant, did you see this section? http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatalyst.html#Implementing%20SiteCatalyst%20tracking%20for%20custom%20componentsscott

I think this is how it works:Create a few page components, each one defining a different set of CQ analytics variables. On the framework, map all the CQ analytics variables to SiteCatalyst variables. When the page is loaded, only the variables that that exist on the page will be sent to SiteCatalyst...

I never noticed that myself, until now  I am trying to find an answer for you. scott

I'm not sure about the Segmentation, but there does not seem to be an out-of-the-box way to define a segment based on user group. I suppose  you could add the information to the client context [0] when the user logs in, and then use the Generic Store Property to access it in the segment [1].For exec...

hi,are you referring to machine translation, or to internationalization of component strings?thanks,scott

in addition to the links that Scott provided, there is this docs page about authoring targeted content: http://docs.adobe.com/docs/en/aem/6-0/author/personalization/target.htmlscott

Hi,No, sorry they are not offered as a download. Package Share does offer 5.x CQ documentation in a package, but it does not include API references.scott