In 2005 UCC ITS chose to extend the tools available to the ministries of UCC with respect to the web. IF your ministry is interested in adopting this solution, talk with the ITS department.
Key reasons this web-based application was constructed:
The global layout, colors, and style can be controlled individually in each instance of the CMS and effect the entire site.
The Manageable Page is editable, and can include images, tables, stylized text, and placeholders. Content in the manageable page can be placed inside a wrapper in the editor to be conditionally available.
The Footer is shown on each page.
The Pictures can rotate through a list of pictures, or randomly present pictures from a pool.
The manager tasks can be customized depending on who is logged in.
Breadcrumbs are hierarchical and show where you're at in the website.
|The Menu's are configured in |
The RSS menu is automatically created based on context, but can be customized in
Global CMS settings in
CSS Folder instructs CMS how to look (colors, spaces, background images, forms style, messageboard style, etc)
Sitegraphics folder hold preconfigured icons, masthead images often referenced by the core CMS code or webpage_layout.asp
xstandard folder is where to put the
Using redirection and processing for CMS directives as described in
Any webpage that is a child of the /home page, can be addressed as just /childname if it does not conflict with other /services - and the request is expanded to be */home*/childname
Pages that are 'pending' status may only be viewed by people that have Admin rights in at least one service.
if /pagenum is requested, return an HTTP 301 redirector to full webpage. this allows very short urls to pages deep on the website if character count is a priority.
pages can be direclty addressed by their childname if they are the first page with that name. returns a http transfer 301 response.
if a requested page does not exist by direct URL request OR exist in the CMS as the request is interpreted or expanded, then a 404 page is sent to the client. this page may include additional information as defined in
/Playground demonstrates live examples to help clarify Modules, Placeholders, and Wrappers
Modules extend foundation functionality of the CMS site wide
Placeholders extend functionality and content at specific locations. Wrappers conditionally exclude content at specific locations
Usage Examples demonstrate combining modules, placeholders, and wrappers to achieve content that cannot be individually created with only a module, placeholder, or wrapper. Playground demonstrates most Placeholders and Wrappers.
Advanced documentation is geared for CMS Administrators and Programmers in the event they need to install a new instance of the CMS, extend functionality, or debug.
New Form Validation Rule