One of the magic things that make Elephant easy to use and powerful is the structure is build on. When Elephant takes control you are always in a Context
. As for creating web pages, you'll need to understand what a context is and its relation with other contexts.
A context
is a web page. We didn't called web page
because it seemed too simple for such a marvellous creature, but is nothing more than a web page. Anyway, as to continue making things complicated where they should be easy, we will call this web page a context
.
Context builds up with two different kinds of elements. The actual elements and the layout elements. Despite their names, they respond to a very usual situation. You know how your site should look and don't want to repeat the design for each page. These elements are the layout elements. They are defined at top level, in site's home, and inherited for lower levels.
The image shows what the layout elements are, surrounding the actual content, which is not more than the actual element mentioned above.
By default, the actual element is HTML content, text, written with the special Elephant syntax.
Elephant sites allow creating as many contexts as you might require, remember a context is equivalent to a page. There is no other limit than the available space and your imagination. Creating pages involve thinking where you want to contruct them. To understand this you might think of your site as a tree. The trunk is the home page. First branches will be home its children and so on. Your tree can have many branches, Elephant will take care to make easy the navigation among them.
Each context has several attributes that define its behaviour.
Attribute |
Description |
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. |
Context role |
Protects a context using user's permissions, roles or syndications. See Security . |
Language |
Coma separated list of languages used in this context. This value is inherited from parent context. If you set a language in root context, web site's |
Redirection |
Redirects to a different context when context is selected. If the path contains a full URL, the redirection will also inform the browser is being redirected. A path equal to |
Not to index / Not to follow |
Values passed to search engines. |
Show print version option |
When checked, shows a link to printer version.
Print version will render current page and all its descendants in reading order.
|
Show control version system |
When checked, shows different versions of this page, including language, author and modification date. |
Name |
Context's name. Yoy may need to specify as many names as languages the context has. Name is what appears on menus, tabs, popup menus, etc. |
When you want to show an image in a page, you need first to upload the image file. Where this file goes to it's called repository
. Each context has its own repository. So, you have as many repositories as web pages. Each one with its own structure and content.
Elephant maintains different caches to increase performance.
site.xml
.The Tools menu has an option that allows to reset these caches. Also forces the sitemap generation. Use with caution.