Take a closer look at the software behind
Diversity Websites

The Page Hub is where you'll spend most of your time editing your sites content. Various tabs allow you access to your data such as META tags, design view, content view and page administration.

With the page checked out for editing, you can edit one of the text regions. All styles created by the designer are available here via the styles and format drop downs. These can be individually tailored per page or region.

Images can be edited using a Static image region where the designer of your template has set the dimensions and quality of the image, or by using the in-line edit option to insert images. All images are web optimised upon saving so you'll never have oversized images slowing down your pages.

On all pages, you can right click to get a list of short cuts to other parts of the CMS.

Some items in the CMS, notably folder icons for Data Lists, Image Libraries and Templates, have a different short cut context menu to help find commonly used options.

In addition to the main CMS application, you can also install pre-built CMS Apps which can be accessed from this menu. If you ask us to create a custom feature for the CMS with its own data management, you'll typically find it as an App here.

The Image Library can be used to store commonly referenced images in your pages or data lists. High quality images are stored here and then imported into the size required for your page or data list item. As with all CMS images, the file sizes are optimised for fast web downloads while still retaining image fidelity.

The Resource Library allows you to manage shared data resources, commonly Data Lists. These can then be assigned to pages by the designer or open to users to select which data list to use.

Global data allows you to create your own lists of micro data that can shared between different list item folders. This helps to keep a common list of shared data values across multiple data stores.

Data Lists are like mini-databases, you can allow your CMS users to pick which data source to get records from, or you can fix it in the Toolkit control. You can also allow your users to pick and choose a category filter and/or choose a subset of list items from the main store to display.

Folders set the core list item values such as display order, image sizes, advanced text edit (CSS styles that can be used when editing list item text) and advanced field creation to customise data input and output.

Every list item has a standard set of fields, some mandatory, to store data. You can also define your own fields for users to add to and then display in your site allowing you to extend the data beyond the standard feature set.

Using the editor for small to medium amounts of data is great, but sometimes you may need to import a large data set of hundreds of records with lots of extra data fields. You can use this option to import data from an Excel spreadsheet either exported from another application or managed yourself. You can map the data columns to the same or similar fields you've created in the data list.

A list item can exist in 3 modes: Red - unpublished, Yellow - Viewable on Preview only and Green - published to Live and Preview. This allows you to test items at different publishing points.

Items have a wealth of information to edit with all of some of it being displayed in your site as news, events, FAQs etc. As with page content, you can also add in-line and static images (automatically web optimised), add a file attachment or assign multiple categories to the list item.

You can use one CMS application to edit multiple websites, whether they are individual sites, microsites or multilingual sites.

Each website is called a group (containing templates, images and resource library items), you can also specify different locale information for correct page headers and language enocding as well as a file name standard for how to save your physical sites pages, e.g., OverviewFeatures.aspx, Overview-Features.aspx or Overview_Features.aspx.

All pages are "physically" written to the server, there's no dynamic re-linking of a page so when a search engine visits your site, it has real pages to index with very little "dynamic" overhead code to get in the way.

You can define a naming style for your site to use no spaces, a hyphen or an underscore (e.g, My-Page.aspx or My_Page.aspx). In addition, any dynamic menus are written has HTML content upon publish rather than dynamically so there's no need to worry about heavily ID'ed links, just plain and simple URLs!

There's no "in code" development required to use our Toolkit controls, so you don't need to learn a language like PHP or ASP.NET, just put our CMS controls wrapped in HTML comment tabs, and the CMS takes care of the rest!

You can set up 3 types of CMS users: Publishers who can control all content and publishing, Editors who can edit content but can't publish, and Preview Only users who can login but only view the Preview site with no CMS access.

You can define what websites and pages an Editor can have access to as well as if they can edit image library or data lists.

All page requests made to the site are screened for common injection attacks. Although we can't project for every new instance, a vast majority of incidents are trapped by the CMS sanitising each request made.

When data is passed between CMS pages, each request is hashed automatically in the query string. If the resulting page finds the content in the query string has been altered, it aborts the transaction so preventing any "man-in-the-middle" attacks.

Every page in your site is created from a template we or your designer creates using the designers toolkit. Publishers and Editors of the CMS can then use these templates to add more pages.

Preview your template before you use it. The preview option shows your page "in context" with the CMS editable regions marked in red.

No ones perfect, we've made mistakes (and still do), we're only human after all. The worst case is where users edit content on a "live" site. Before you know it, you're mistakes are live to the world. Diversity offers a solution. Each site has two domains, a live one and a preview one. All CMS data is edited on the preview site before it goes live to the public; the preview site is hidden behind a password allowing you to test the site privately before you hit that live publish button.

The CMS publishes a physical snapshot of your database driven content as static web pages to our servers. This means you can continue to work on your site without affecting the Live site allowing you to keep a "work in progress" site and a "live" site, replacing the current live site with the preview one when you are ready.

You can publish either all of your site content, just changes, just pages or just data list content. You can also choose which of your web groups to publish for multiple site management.

Menus can be driven from physical page structure you design in the CMS or via another source such as a data list. As and when you add pages, the menu will also reflect that change upon the next publish.

By assigning categories to a data list, you can create a dynamic filtering system to display all or some of the data items stored in a folder.

The toolkit is flexible enough to allow you to integrate the export data with other libraries like jQuery as shown in this HTML gallery example.

Use a data list to output your items as in a calendar format and use the end data to create a range of days covered. You can style the calendar using CSS.

Standard content auth is always enabled allowing individual users to check out, edit and check back in pages and content assigned to themselves preventing other users for working on the same content at the same time causing a data conflict.

For clients who require more control over their content, you can specify various "approval" options for pages, text, images and data lists. Every time a user edits content, it will need to be approved by a Publisher before it can be published.