Content Managed Websites Login


Please ensure that you have read and understand the following topic links before reading on.


For each project on the TOTECS platform there is the ability to set up any number of content managed websites. A content managed website itself is a website that can be created, and modified by an administrator user without necessarily needing to know intimate, technical knowledge for a website to appear on the world wide web. Additionally content managed websites allow administrator users to create, modify, and delete web pages without having to deal directly with underlying computer systems that allow these web pages to be accessed by other people navigating through the world wide web.

Content managed websites are typically used as a front end for organisations in the online world, just like a shop in the real world. The TOTECS platform allows the appearance of a website, as well as the content that sits within it to be comprehensively tailored by an organisation. Some organisations may wish to set up a content managed website that allows the general public to view catalogues and purchase products at retail prices, other organisations may wish to just display news related to their business and sign up people to their marketing, and other organisations may wish to set up several websites that are branded entirely different to do different things. Whatever the purpose the TOTECS platform provides the building blocks to create inovative content managed websites that can be customised, styled, and structured to meet an organisation's objectives.

A content managed website (or any website for that matter) is made up of many assets, most notably webpages. Webpages allow people to navigate around a website through the use of links embedded on each page. In a TOTECS project administrator users can create web pages, and the content in these web pages through the use of the tools embedded in the Websites section of the Administration Centre on the TOTECS platform. The content within these web pages is dictated by the types of areas that are set up on the web pages. Administrator users can choose different types of areas to display information from different locations within a TOTECS project. For example an area on one web page can be configured to list a number of products, where as another area can be used to list news items. There are over 70 different areas that can display different kinds of data, tailored to the user who is viewing the web page at the time.

Each content managed website deployed into a TOTECS project must have a unique domain that allows the website to be found from anywhere on the internet. Examples of domains are, or Once a person navigates to these domains, they will be able to view the content managed web pages in the website. Its important that when setting up a content managed web site that a domain is chosen, then purchased from a domain registry. Once a domain is purchased it needs to be hosted, with the domain settings configured to point to the TOTECS servers that are serving the content managed web site. For more information you can read up on domains, and the Domain Name System that is used over the internet to allow people to locate websites at

Within a TOTECS project there are users who can be assigned to either "Content Managed Websites", or the "Trade" interface. If a user is assigned to a content managed web site then when they successfully login to the project they will be redirected to a content managed web site's designated web page.

Content Managed Website Settings

Below are the following settings that can be configured for each content managed website through the Administration Centre's Websites interface, by clicking on the domain of any content managed website.

Website Setting Description
Website Key Set a unique identifier for the website that is a combination alphabet characters and numbers. The key is used to set up assets behind the scenes and must be unique for each website within a TOTECS project.
Website Domain Set the domain of the website that will be placed at the front of all web page, image and attachment links. Ensure that you have purchased the domain set from a domain registry, and have the domain's IP address pointing to the TOTECS server that the project is running on.
Website Secure Domain Set the domain of the website that will be used to serve up secure content managed web pages. Under most circumstances the secure domain needs to be set to one of TOTECS secure domains. Contact your TOTECS person to work out what the secure domain should be set as. 
Website Root Domain Set the root part of the domain for which browser cookies will be saved to for storing a user's session. It is important that the root domain matches the root component of the website domain setting. If this is not set correctly then when users log into a content managed website and navigate to another web page, then their session will no longer exist and they will be logged out again.
Website Retail Domain Set the website domain that is used when a web page URL could not be determined. Typically set this to be the same as website domain setting.
Website Retail Login URL Set the URL that users (assigned to a content managed website interface) will be redirected to after they have logged in from the Trade login web page.
Website Retail Logout URL Set the URL that users will be redirected to after they have logged out from a content managed website.
Website Email Set the Email address that notifications will be sent to when users submit enquiries on any of the web pages assigned to the website.


Content Managed Webpages

Each content managed web site can have any number of web pages created within it. Each web page is made up of a "webpage template", containers and areas. The web page template provides the structure for the web page, and designates the locations on the page where area containers can be placed. Administrator users can then create areas of the web page that display different kinds of information.

Within the Administration Centre of a TOTECS project, in the Websites interface there are two locations where content managed web pages are located, these are the Webpages folder, and the Email Webpages folder. When a web page is created for Emarketing Emails it is located in the Email Webpages folder, for all other normal web pages they are located in the Webpages folder. In the websites tree you can create web pages to be children of other webpages. This allows the web pages to mimic the structure of a website to help admins visually identify the structure (but has no other function).

For more details on how a content managed web page works, click on the link below.

Content Managed Webpage Templates

A content managed web site can have zero-to-infinite amount of web page templates created within it.

The web page template is a HTML(Hyper Text Markup Language) file that forms the foundation of the web page. It contains the underlying look and feel of the web page, as well as hooks (also known as placeholders) that dictate where the containers are placed onto the template, which set the areas that can have content modified in. The same web page template can be assigned to several different web pages, which allow web pages across a content managed web site to have the same consistent look and feel, as well as reducing the work required to create new content managed web pages. The structure of the web page template is the same of any HTML file, which allows any web designer or developer with HTML skills to create a template and embed any third party functionality such as javascript libraries or Flash animations.

For more details about a content managed web page template follow the link below.

Global Content Managed Webpage Containers

For each content managed website there is the ability to create any number of global web page containers. Each global web page container can be embedded on any web page within the content managed web site, hence why they are termed "global". Additionally each global web page container can store any number of web page areas within it. Because of this these global containers allow the same areas to be displayed on a number of web pages, without having to create the areas separately on each page.

A common example of where global containers are used is to display a Basket Summary area, which allows the user to see how many products they have added to their shopping basket on every web page and checkout. Another common example is to put the Category Listing area in a global container so that way users can always navigate through the top level categories from any web page.

Using global web page containers can dramatically cut down on the amount of time required to set up a number of web pages where there is consistency across a number of webpages within a content managed website. Additionally it can cut down on the amount of time if changes need to made to these same areas across many web pages.

For an administrator user to create a global container, within the Websites administration centre interface the user clicks on the website's domain, then in the Website Detail interface the user can add a global container by giving it a label, and the name of hook that allows it to be embedded in a web page template.

After a global container has been defined within a content managed website, then the administrator user just needs to embed the container's hook into any web page templates that the container is to appear in. After doing this then any web pages using the web page template will have the global container and its areas appear on it.

Ensure that when you are embedding a global container's hook into a web page template that you only embed the container hook once within the template, otherwise the web page may not function as expected.

Web Page URL Routing

For content managed web page URLs generated for products, categories, makes, models, or news/blog items there is the ability to route these entities to display a specified content managed web page. For example this "URL routing" allows for certain product to display on a dedicated web page where as the detail all other products may be displayed on the default web page set up for a content managed website. Using URL routing allows for search engine optimised URLs to be set that do not contain the title of the web page that is used to display the detail of a product, category, make, model, or news/blog item. Additionally general URL routing rules can be set up so that the name of one web page that may not exist is routed out to web page does exist. This may be usefule when the title of a content managed web page changes, but old links exist in Emails and other marketing materal to the old name content managed web page.

Version Controlled File Repositories

Each content managed website can host zero-to-infinite amount of GIT version controlled files repositories.
GIT is a widely popular technology used to version control a collection files and folders (collectively known as a repository), allowing multiple people to work on the same files at the same time, and track any changes that have been made to the files and folders.
Within each content managed website there the ability to create and host two different kind repositories:

  • Public Repository:
    The files within the repository are accessible by the general public through a web browser via the content managed website's domain and associated URL path.
  • Private Repository: 
    The files within the repository are only accessible by users who have been authenticated through TOTECS and pulled the files to their local computer. This ensures that the general public cannot access the files and folders within private repositories.

For both types of repositories the files and folders cannot be directly changed through the Administration Centre, instead they can only be changed by a person modifying the files in the copy of the repository stored on their own computer, then pushed up the changes back to the repository stored in the content managed website.
By using public repositories administrator users may no longer necessarily need to log into the Administration Centre to upload new versions of files to a content managed website.
Additionally the GIT repositories store a log of all the changes made by other people, this allows everyone who has deployed the repository to know who changed a file, what they changed, and when they changed it.

Within the Administration Centre, under the Websites menu, in the Websites interface, for each content managed website a new had been added labelled "Version Controlled Repositories".
Within this tree node will display any version control repositories that have been created. Additionally there is the ability to click on the Plus icon, which will open a dialog where an admin can create a new public or private GIT repository.
Within the "Version Controlled Repositories" node by expanding a version controlled repository users will be able to see the URL of the repository, which can be set within GIT client software, that will allow the repository to be deployed to their local computer.
Once done users can then add files to the local repository, and push the files and changes back up to the content managed website, after authenticating themselves with their admin credentials.
Additionally within the Websites interface admin users have the ability to navigate through repository folders and files to be able to see what is within the repository, without have to clone the repository to their local computer.
Note that the only way to upload files to a repository is using a GIT client application. This also ensures that users cannot overwrite other users changes without first updating their local copy of the files.
Any repositories that are public can have its files be accessible from the content managed websites domain, allowing links to these files to be embedded on content managed templates and web page areas.

Attachment File Libraries

 In each content managed website folders can be created that contain a list of files that can be attached to content managed web pages, and allows users to download the files if they are embedded on a content managed web page. Each folder is called an Attachment Library.

Use attachment libraries to group different types of files together, for example a website might have a library called CSS, which contains all the files that a web page template uses to style the structure of content managed web pages.

Note: There are restrictions on the filesize limit of attachments being uploaded. If you have a file that is bigger than the limits then consider using a dedicated file hosting provider to store the large file, such as Dropbox to host the file, and embed a link to provider's file on your web pages. The limit is there is to ensure that the TOTECS servers have the capacity to serve websites fast, and are not overwhelmed with lots of people downloading big files.

Image File Libraries

 In each content managed website folders can be created that contain a list of image files that can be displayed on content managed web pages. Each folder is called an Image Library.

Use image libraries to group different types of image files together, for example a website might have a library called Template Images, which contains all the files that a web page template uses to style the structure of content managed web pages.

Note: There are restrictions on the filesize limit of images being uploaded, as well as the file type. If you have a file that is bigger than the limits then consider using a dedicated file hosting provider to store the large file, such as Dropbox to host the file, and embed a link to provider's file on your web pages. The limit is there is to ensure that the TOTECS servers have the capacity to serve websites fast, and are not overwhelmed with lots of people downloading big files.

Please ensure that if you are uploading JPEG images up to an image library, that the colour profile of the image is RGB based. This means that the colours set in the image are designed for computer screens, and not print media. You can find out this information using a image manipulation computer program such Gimp, or Photoshop.

We recommend that you resize your images, and set the quality of the images so that they are a balance between small filesize and respectable quality. The smaller the file size will allow the web pages to load faster that the image is placed within.

Content Managed Webpage Area Formats

All formatted areas on a content managed web page use "formats" to define the structure, styling and content around pieces of data available to the given area. Formats are made up from HTML with hooks imbedded (just like web page templates) that dictate where certain types of data are placed within the area. Formats are used to provide consistency when the same kind of data needs to be repeatably shown, such as a list of products assigned to product category.

Each TOTECS project allows any number of web page area formats to be created within it. Formats created in the project are called "Local Formats", since they reside only in the project. Additionally the TOTECS platform comes with "Global Formats", that is area formats that exist for all projects in the platform. Global formats provde examples on how specific types of formats can be structured. Additionally administrator users can open a global format, and then save it as a local format. More information about area formats can be found in the link below.


For each content managed web site, it can have content managed web pages set up with Enquiry Form areas. These areas allow a website user viewing the web page to fill out a form, based on the questions and fields defined by an administrator user. Once the website user has submitted tne form, the details of the enquiry are sent out as an Email to the administrator user, as well as being accessible to view from within the content managed web site within the Websites administration centre interface. A table will display all the enquiries that website users have submitted from within the content managed website. Administrator users can then mark these enquiries as having been read, and responded to.


For any given content managed web site, any number of regions can be set up within it. A region defines a location for which guest users visiting the website can be grouped together. An example might be that a website has 3 regions set up for it, Oceania, Asia, North America. For each region a customer account, guest user and Recommended Retail Price (RRP) Level can be set up. Then rules can be set up so that if a public user is navigating to the website from a specific geographic location, then the user will be assigned to a region appropriate to them. Once they are assigned a region they can then see web pages, product pricing, currency, and anything region specific to the user. Using regions allows content managed websites to contain information that is specific to different types of users, and optionally use the same web pages to display the differing information.

Content managed web pages can be configured to allow the user to change regions, or force a region to be assigned to the user if they land on a specific web page.

A common example is to set up a guest user for a number of regions, then assign those guest region users to a currency applicable to their region. Then on each web page give the users the ability to swap regions, and allow them to view product pricing in different currencies, with pricing that is based on guest region user's assigned customer account's price-level that has been set in the accounting system.

Regions can be set up in many different ways, and they do not necessarily need to be based geographic locations. However if you do need to set up geographic regions that are filtered based on where the user is navigating from, please contact your TOTECS person to set up the geographic IP (Internet Protocol) address rules with your regions.

Recycle Bin

Within the Websites administration interface, if an administrator user deletes a web page, web page template, image library file or an attachment library file, the user has a choice to permanently delete the asset, or move it to the recycling bin. Once an asset is in the recycling bin it can then be restored if it is required again. The recycling bin provides a safe way to delete assets if an administrator user is unsure whether an asset should be deleted or not.