Domains represent the top level entity for generating content. Here's what you should know.

Basics

One of the major design decisions for Baltic Content Framework was to be able to host multiple web sites (i.e. domains or sub domains), and manage them from a single administration panel. When you work with content (creating folders, articles, etc.), you work within the scope a single domain. Each piece of content that you create belongs to the domain that is currently active in the admin panel, and can be used in any article (or multiple articles) of the domain. Once created, a content component cannot be moved to another domain.

Plugins work differently in that they belong to the system, not the domain, and can therefore be used by any article in any domain. For more, see plugins.

Domain Configuration

A domain maintains various properties that can apply to all of its articles. The most important is its template property. The template property, which is mandatory, identifies a main template (an .html file) that is used for all articles within the domain, unless overriden. See templates and placeholders for more.

Another important domain property is its default language. This doesn't affect how you write your articles, but it does affect how certain plugins insert automatic text, and how templates are located. And -- as with templates, you can override the default language further down the hierarchy.

Other domain properties include:

• Domain name. The name of the domain, such as example.com. Used in management.
• Site name. The name of the site, such as Good Foods. This value can be inserted into content via placeholders. For instance, the name of this site (inserted via placeholder) is: Baltic Content Framework.
• Site name (short). Same usage as site name, except a shorter value that can be used, for example, in CSS media query aware portions of site templates to display a shorter value on smaller screens.
• Domain token. A system generated read only value. Used to locate resources for the domain.