You have a lot of brands – AND, ONLY, etc. – and a lot of pages fo

1.	You have a lot of brands – AND, ONLY, etc. – and a lot of pages for these brands in your AEM content structure. The site hierarchy for these brands cannot be segregated. For each of these brands, the client expects a particular theme.
Answer» I'd address the SITUATION with the following suggestions: Global Configuration Page: Make a Global Configuration Page (assuming Dynamic CSS) where consumers may specify which brand has which CSS/theme included. This configuration page can be used to select a specific brand, its CSS (either a set path or a zip PACKAGE), its logo, and any other adjustments specific to that brand. The CSS file from this global configuration page WOULD be picked up by all pages, which would then apply the theme based on the brand. Tags on the page, selectors for specific brands, or a pre-specified path could all be used to identify the brand. Consider Fixed CSS: If we have a fixed CSS file, we may map the Tags on the page directly to it. If a specific Tag (e.g. AND, ONLY) is PRESENT on the page, the CSS will be applied directly to that page. Tags could be created by CQ authors using Page attributes. Selectors can also be used to solve the problem. Segregation: A better and ideal case would be to SEPARATE the brands in a site hierarchy so that a single theme could be applied to all pages under a node for a certain brand.

You have a lot of brands – AND, ONLY, etc. – and a lot of pages for these brands in your AEM content structure. The site hierarchy for these brands cannot be segregated. For each of these brands, the client expects a particular theme.

Answer»

I'd address the SITUATION with the following suggestions:

Global Configuration Page: Make a Global Configuration Page (assuming Dynamic CSS) where consumers may specify which brand has which CSS/theme included. This configuration page can be used to select a specific brand, its CSS (either a set path or a zip PACKAGE), its logo, and any other adjustments specific to that brand. The CSS file from this global configuration page WOULD be picked up by all pages, which would then apply the theme based on the brand. Tags on the page, selectors for specific brands, or a pre-specified path could all be used to identify the brand.
Consider Fixed CSS: If we have a fixed CSS file, we may map the Tags on the page directly to it. If a specific Tag (e.g. AND, ONLY) is PRESENT on the page, the CSS will be applied directly to that page. Tags could be created by CQ authors using Page attributes. Selectors can also be used to solve the problem.
Segregation: A better and ideal case would be to SEPARATE the brands in a site hierarchy so that a single theme could be applied to all pages under a node for a certain brand.