The method you've used in other systems will work fine in AEM, too. Simply expose a property via your template's page properties cq:dialog (`./pageClass` for example), and output the value of that property into the class attribute of your template's HTML element. In JSP:">or Sightly:You can now define your page specific styles as follows (for example, to style paragraphs when pageClass is set to 'homePage'):.homePage p { margin: 0 1em; }A general discussion on the topic can be found here [0].[0]...

You can get rid of the unwanted inherited tabs by including the following property on the `items` node that is a parent of the tabs:sling:hideChildren="[permissions,cloudservices,thumbnail]"

Try hitting your component without the 'dynamic' selector (for example, http://localhost:4505/content/myapp/mypage/_jcr_content/rightPar/dynamicComponent.html). The contents of dynamicComponent.jsp (including 'render this') will not be included in the response when the selector matches another script.I would also suggest renaming dynamicComponent.dynamic.jsp to simply dynamic.jsp.

I hacked up a little example using the excellent AEM Fiddle (part of ACS AEM Tools [0]):<%@include file="/libs/foundation/global.jsp"%><% %><%@page session="false" contentType="text/html; charset=utf-8" pageEncoding="UTF-8" import="org.apache.sling.api.resource.Resource, org.apache.sling.api.resource.ValueMap"%><% // Get the text resource Resource textResource = resourceResolver.getResource("/content/userblog/2015/06/blog_post/jcr:content/par/entry"); // Get it's properties ValueMap textResource...

Yes, it's possible. Check out the Externalizer service [0] for access to the hostname, and the Sightly Use-API [1] for exposing that value to your Sightly scripts.[0] https://docs.adobe.com/docs/en/aem/6-1/develop/platform/externalizer.html[1] http://docs.adobe.com/docs/en/aem/6-1/develop/sightly/use-api-in-java.html

A componentGroup property set to '.hidden' means the component will be hidden from the side panel Components tab (touch-optimized UI) and the Sidekick (classic UI). Hidden components can be used by developers as the sling:resourceType of a template, or included directly in a component's script via cq:include (JSP) [0] or data-sly-resource (Sightly) [1].[0] https://docs.adobe.com/docs/en/cq/5-6-1/developing/components.html#[1] http://docs.adobe.com/content/docs/en/aem/6-0/develop/sightly.html#res...