CMS Layouts and Themes

Each PrimeAgile™ website is composed of page content, layout and styling.


Layouts are used within PrimeAgile to help separate content, style and positioning on the page.   Layouts are grouped into sets that can be used for multiple pages of a site that have coordinating or similar layouts making them go nicely together for a site.  A set would define different page layouts for example a page layout for the contact us page, and a layout for the home page.

This makes it much easier to build a website because the user can simply select a layout set and all of the default page layouts for that set will be provided to their website.

Because content and theme are different from layout, the user can change the layout to change the positioning of items on the page.  Advanced users can fine tune a layout to modify the size and position of an item on a page.

In addition to changing the layout at any time the styling - or theme of a website can also be changed.  Changing the theme will change the styling site wide.

Page Content

Page Content look and feel are controlled by the layout and the theme.  This also allows the site to be changed without a re-write.  Adding content is controlled by the types of content controllers on the page.  For example, text blocks, date pickers etc.

PrimeAgile™ Content Management System Layouts

Layouts are used to build PrimeAgile pages.  Layouts are grouped together into layout sets.  A layout set contains several layouts that have a common look and feel to them.   A website or application is built using a layout set.

The layout to use in a layout set is indicated by the associated layout mask.  Internal Page for example may be the layout mask within a layout set.  If a site changes their layout set to another set, the corresponsing Internal Page Layout Mask will be used and the pages that are using that layout mask will be built appropriately using the new layout set.

Authorization within a layout

Page level Authorization

An entire page can require authentication to be viewed.  The page would be setup with authentication criteria - for example members of certain groups could be given authorization to view the page.  Members who were not in that group would be denied access indicating they do not have privileges.  If the user has not yet been authenticated, then the user would be directed to an authentication page before the page could be accessed. Once authenticated, if the user does not have sufficient authorization to view the page, he would be informed of this and denied access to the page.

UI Component Level Authorization

Each UI component on a page can be displayed or hidden based on the authorization of the users.  This is for a page containing content or an appliication.  

To learn more about PrimeAgile user authorization go here