On Thu, Aug 27, 2009 at 11:32 AM, Markus Pallo<[email protected]> wrote:
> its not a typical hosting environment, there is a company group (same big
> company) which like to have for each individual company a custom layout. But
> there will be several things shared. Also "website content", "apps",
> "config" probably "users" ....
Re-reading my statement about content vs. components/scripts I think I
wasn't very clear. What I wanted to say - and your description of the
use case underlines that - that one should see everything as content,
including design and configuration, not just the core content to
display. So if you store your design information in your templates,
regardless of their location, your scripts will be able to read them
upon rendering and thus not only display different (or same) content,
but also in a different layout depending on the site.
So, the situation might be that both sites have different layout, but
the same content. They could share the same components (ie. resource
types) but their layout content is different. Or they can have
different layout and different content. In any way, having only one
set of scripts that acts upon different content and design
("everything is content" with a JCR) is the preferred way to go. And
with the super resource type mechanism in Sling it's easy to quickly
extend a resource type if you really have a specific case.
Regards,
Alex
--
Alexander Klimetschek
[email protected]
