Content Profiles
The Widget Framework allows you define multiple sets of templates
called content profiles. The purpose of content
profiles is to make it possible for a single publication to be generated
in two completely different forms. You could, for example, have a
default
content profile for generating your standard
web site and a newsletter
content profile for
generating a newsletter from the same content.
Widget Framework content profiles (that is, template hierarchies)
are organized under the root section config
. By default
there is just one content profile, called
config.default
, which might look like this:
config
config.default
config.default.section
config.default.section.ece_frontpage
config.default.section.news
config.default.section.sports
config.default.article
config.default.article.type.story
config.default.article.type.picture
config.default.topic
config.default.master
Adding a second newsletter
content profile would
result in two parallel template hierarchies like this:
config
config.default
config.default.section
config.default.section.ece_frontpage
config.default.section.news
config.default.section.sports
config.default.article
config.default.article.type.story
config.default.article.type.picture
config.default.topic
config.default.master
config.newsletter
config.newsletter.section
config.newsletter.section.ece_frontpage
config.newsletter.news
config.newsletter.sports
config.newsletter.article
config.newsletter.article.type.story
config.newsletter.article.type.picture
config.newsletter.topic
config.newsletter.master
Note that the config
section is not itself a
template: it is just a container for content profiles.
The templates that make up a content profile are created by publication designers using Content Studio. For information about this and the rules and conventions governing template naming, organization and inheritance, see Templates, in the Widget Framework User Guide.