The following words and phrases have a specific meaning when discussing Zenario:
When an administrator is logged-in to Zenario, he or she is in admin mode. This mode is not available to regular visitors or extranet users.
The toolbar that is visible above every page of the front-end of the website while viewed by a logged-in administrator. The admin toolbar contains tabs to switch between the modes: Preview, Edit, Create/Menu, Translate, Item Slots, Template Slots, Template Family Slots.
A person with the rights to edit or manage a site, who has logged into admin mode. Permissions govern the things that an administrator is allowed to do. Note that Administrator accounts and the Admin login screen are separate to Extranet User accounts and the Extranet page.
A means by which administrators are allowed to access certain parts of the CMS's functionality. There are broad permissions - Author, Menu Editor, Publisher, Designer, Extranet User Manager, and some others - and within each broad permission there are more granular permissions (granular permissions not in Community).
The unique, friendly name of a content item. An alias forms the right-hand part of a URL, for example http://zenar.io/portfolio the alias is "portfolio".
A page on a Zenario site. Content items are version controlled: when a published content item is edited, a new version of that content item is created in draft form; when it is published, the previous published version may be retained (depending on the CMS edition) as an archived version. The numeric ID of each content item never changes once the item has been created, although items may be assigned an alphanumeric alias, which may change.
A grouping of content items which have similar properties. Content types include HTML Page, Document, News, Blog, Audio File, and Streaming Video.
A site, or part of a site, which requires visitors to enter a username and password in order to access it. People who may access an extranet area are called users.
A chunk of HTML which determines how the output of a plugin that is in a slot will appear on the web page. When a plugin runs, its output is merged with its selected framework to produce the final output that the visitor will see. Frameworks are only editable in the file system and cannot be edited directly via the CMS.
The visitor-facing part of a Zenario site. This encompasses the view of published content items when viewed by site visitors, and the various views of content items (in draft, published and other modes) that an administrator may see while in admin mode.
An in-built design tool, used to edit the slots on a pages layout. You can control size, position, groupings, device view and define the CSS class of each slot.
A human language in which a visitor may view a website. When a language is enabled, the administrator may choose to load visitor phrases into the database, and after that the phrases of that language may be displayed to website visitors.
Refers to the hierarchy of menu nodes, and describes how deep a menu node is in the hierarchy. Level 1 menu nodes are at the top of the hierarchy, with level 2 nodes beneath them, and so on.
The menu system is the principal kind of hierarchical navigation for visitors. A menu node is a single navigational item in a menu. A menu node usually links to a content item (its destination). A menu node may have child nodes, and those may also have child nodes, to any number of levels.
The administrative back-office of Zenario, also called 'Organizer'. Only administrators can see this area. See also: front-end.
A word or phrase which may be displayed via the front-end of a Zenario site to a visitor.
Certain modules are capable of generating plugins, and those plugins can be inserted on a layout. When a web page is displayed, all plugins that exist in slots on its layout are displayed. These plugins are stored in a central repository, or library, in the CMS. Plugins are typically used where the same piece of content should be displayed in several different places on a site. Editing a plugin that is used in several places will cause a change on every page on which that plugin is in use. A typical example of a plugin may be a company logo, held in a plugin of the Banner module. Plugins have multilingual support, and use visitor phrases to display output in the appropriate language, because plugins are managed centrally, they are not under version control. See also version controlled plugins.
A means by which a module can broadcast a notification that some event has occurred. Other modules may then listen for the signal and potentially take a further action.
A collection of CSS files and images that are hung on a template to determine the layout and appearance of a web page.
A defined area within a layout, usually filled with either a Plugin or version controlled content.
A set of content items (web pages) which are in different languages but all contain the same meaning.
A YAML-based user interface markup language developed by Tribal Systems to facilitate consistent development of administrator interfaces. TUIX defines behaviour in Organizer, in the admin toolbar, in floating admin boxes and in skins.
A person who has an account on a site and who has logged in. See also visitor.
Content when it exists in a slot on the layout level delivers version-controlled content from that content item. For example, a version controlled plugin of the WYSIWYG Editor module will usually be placed in a slot on the layout template. It will then appear on all content items (pages) that use that layout. See also plugin.
Anyone who visits the front end of a Zenario site, whether anonymously or logged in as an extranet user.
YAML is a human-readable data serialisation format. In Zenario, YAML files exist in modules, skins and other places to determine pre-set values and behaviours. YAML files have a hierarchical structure, like an XML file or JSON object. More about YAML.