introduction

Core Principles

Tank uses a magazine metaphor. The complete magazine is your website and the design style (your visual identity) is locked into your Templates. In your publication you have various Sections (sport, property, business). Within each section are a number of Pages (which are also your sub-navigation buttons) and on each page you have a number of Articles. One can have several different kinds of articles, so the template designer decides what kind of article goes into a particular slot on the page. Eg some slots on the page could be designed to contain a banner, some contain a feature article and some contain sidebars etc. Some slots can only contain a single article while others can contain many. Setting this up is down to the template designer. Like a magazine, websites change, so Tank uses the concept of Versions. Often the writers are working on the next edition (version) of the magazine which is only seen by the readers (visitors) when it is publised.

Depending how your site has been designed, pages may have one large article or multiple articles. 


Interface

Tank uses a dual frame design. The version of the website you are working on is displayed in the right pane. The controls for editing the website are displayed in the left pane. 

If the 'Show Edit Controls' button at the top is checked then you will also see controls on your website to allow you to edit the relevent content by clicking on your website. The NumLock key is setup as a shortcut to enable you to switch from editing your site to previewing your site quickly. These controls are never available to the end users, they are just visible when using tank. To turn off these controls so you can see how your site would look to end users, uncheck the 'Show Edit Controls' checkbox.

 


User Types

Staff are split into three types: Writers (write/edit content only), Editors (edit content, publish content and manage general site settings) and Administrators. Within the user settings your site administrator can set up your preferences and update usernames and passwords for you.
Lastly there are the readers, who only see the live version of the site.  


Versions

Good websites rarely stay static -  new articles get written, information gets changed, additional pages are added. From time to time, the look of the website may be changed completely. Tank allows for this with the concept of Versions. 

There is always a 'live' version of your website which is what visitors to your site see. When changes are made the staff will work on the next edition (version) of the site. When that version is ready for publication, an Editor will 'publish' a version which then becomes the 'live' version of the site. 

The existing site is backed up as version called 'old live' so you can undo all the latest changes and revert back if necessary. Writers are restricted from editing the 'live' version of the site - this enables Administrators to check their work before publication. If they want to, an Administrator can work directly on the 'live' version which means any changes will be instantly visible to end users. For major changes to the site, it is recommended that people work on an alternate version and then 'publish' it when ready.

Before publication it is recommended that the site is 'verified', ie tank will check the site for pages with missing articles or other potential mistakes.
copyright tankcms 2009