Attributes
Each context has several attributes that define its behavior.
When creating a context...
When adding a context to the tree, a dialog will ask for a name. This name is the path name, as it appears in the link (URL) of the page. Keep it simple, lowercase and no special characters or spaces.
| Attribute | Description | Inherited |
|---|---|---|
| Name | Context name as it shows in the menus. If you have more than one language configured, you'll have as many inputs as languages. | |
| I18n Key | Uses an i18n key. If you are using the translation features, using this key doesn't require setting names per language, the translator will use it's own values. | |
| Order | Controls context ordering. It's an alphanumeric value, write numbers with leading zeros. ex. 001, 002 and so on. | |
| Show in navigators | When selected the context is shown in navigators. It's useful when you have pages you don't want them accessed directly. | |
| Show always | Even if the context is protected by a role, it will show in navigators. With this attribute set to true, a context will force visitors to login if they want to see the content. | |
| Traversal navigation | When set to true, Elephant adds a traversal menu. Traversal menus ensure the user can press on next context, previous context or parent context, taking into account the indentation levels, similar as passing page in a book.
Traversal menus appear on the top and bottom of the content. |
|
| Internal attribute that tells the context, when set to true, to be part of the printed version of the page. The main purpose of this attribute is to hide content from printed versions. | ||
| Server driven | Only visible to su, when true tells the page to execute the template rendering on the server side. Defaults to false, to provide all features. Use with care, and for a reason, like hiding content in exceptional cases. | |
| Context role | Protects the context from users with not enough permissions. A simple use is user:in (user logged in), hiding the context to visitors. You can specify much more complex roles, see Permissions
. |
|
| Language | Comma separated values, prefixed with _ and in ISO 639-1 indicating languages for this page. For example: _en,_ca,_de means English, Catalan, German. Languages are inherited, setting them in the root context will propagate to all pages. |
|
| Web tag | Allows tag navigation, mainly used on funneling. | |
| Redirection | Used for navigation purposes. Will locate the context in menus, and when selected will move to the redirection. Use relative paths within the web, and full URLs when navigating outside the website. | |
| Not to index | Tells the robots (crawlers) not to index this page. | |
| Not to follow | Tells the robots (crawlers) not to follow links in this page.
Prevent robots from messing up Set Not to follow to true when the page contains pagination, categorization or multiple links. For example projects, publications and the like. Elephant auto-creates a sitemap with all these links.
|
|
| Printer version | Shows a print button at the end of the content. | |
| Version control | Shows a list of previous versions of the page. | |
| Layout root | Only visible to su, indicates the template root. Elephant already uses a default value. Use with care, and only if you are writing alternative templates with a different framework. | |
| Layout | Tells the layout to be used in this page. You'll learn more about layouts in the following pages. This value is inherited by the children. Defaults to default-web. |
|
| Local layout | Tells the layout to be used in this page, and not to inherit by the children.
Setting a root landing page
default-web works best for normal pages, and includes the option menu when the current context has children. When setting a root landing page, you can indicate with this attribute to use default-landing locally. In combination with Layout =default-web will tell the children to use a simple format.
|
|
| AI | When using AI, tells Elephant AI to use the page content as an AI feed, and which language to use.
Feed structured text Pages with images, videos and other multimedia, won't work well as a feed. Use text pages, separate concepts with headers, and whenever possible, use the same language for feeds.
|
| English | 06/08/11 17:56 | Lluís Turró Cutiller | |
| English | 08/27/20 10:28 | Lluís Turró Cutiller | |
| English | 03/17/21 04:16 | Lluís Turró Cutiller | |
| English | 10/04/21 19:49 | Lluís Turró Cutiller | |
| English | 07/26/26 22:50 | Lluís Turró Cutiller |
