Purpose
Ideally, all pages within a site should belong in a container or module
to make them easier to search. In reality, however, there are a number
of webpages within a site which do not belong in any 'organized'
container (or module). In essence, these 'orphan' web pages need a way
to be managed, and is why this module was developed.
This module
allows for the management of ordinary web pages within the site. Core
pages allow a web page to be entered, and assigned to any section (Site
Navigation) of any site within the enterprise. These pages can also be
referred to within other records or pages from the site, giving
autonomy to the management of miscellaneous web pages.
Description
This module allows management of ordinary web pages within the site.
Core pages allow a web page to be entered, and assigned to any section
(Site Navigation) of any site within the enterprise. These pages can
also be referred to within other records or pages from the site, giving
autonomy to the management of miscellaneous web pages.
Web pages
are very flexible allowing normal HTML, images, third party script,
external URLs, internal URLS, and even forms to be easily managed
anywhere within the site.
The value to managing pages within Core
pages, vs. ordinary HTML pages is that they are completely search-able
like any other module. In this way, a search for 'Policy' within the
site may bring up records from the 'Policies' module, maybe a record
from the Employee Directory module 'John Smith, Director of Policy',
but would also scan all core pages for the keyword 'Policy' which would
also be able to be found within the search.
This module allows
you to manage a variety of pages, including third party code, forms,
html, internal links, external links (controlling whether the window
pops up or not), and even allows for the management of 'hidden' links.
(Those links that you do not wish to release to the website, but
instead may want to reference 'from' other webpages.)
How To Use
This module is found within the Site Content tab of your Client Console. Simply click on 'new' to add a new record. The module will ask you for the Title of the record, Start date and end date for the record (which will determine when the page will go live to the site, and automatically be taken down from the site....always keeping it in archive, unless deleted), and the Body Copy of the web page being added.
You can copy and paste information directory into the Body Copy or Description fields, or click on the small HTML tab at the bottom of the window to add your own code. Additionally, you can upload images either directly from the Rich Text Formatting toolbar, or through file upload, if it is an available feature in your module.
Next it will ask 'which' Audience Type or Site that this page will be seen on (you may select as many of these as needed, or ALL), and also, what the 'Access Level' of the record is (public/private or both). This will allow you to determine which users will see the page, public being accessible by everyone, private being accessible by only your privileged site 'members' (managed by the Members module).
Finally the module will ask you for the Display Status of this record (hold/release). Releasing this record will release it to the live site (assuming that you are not subject to editorial review) whereas Hold will keep the record, until you decide to release it (which is a handy tool for reviewing and preparing content BEFORE it goes live.)
Tips About This Module
You can remove Core Pages from your Search results if you want, by going to Site Modules (Under the Admin tab of your Client Console) and de-selecting this module from the Global site search.
If you are not managing multiple Audience Types and Sites within your portal, it is a safe bet to always tag these records to ALL. In this way, if you ever decide to activate an Audience type or site in the future, it will have these records available to it automatically, upon creation.
If you are not managing digital rights of your members (public and/or private) it would be a good idea to tag these records to 'both'. In this way, if you ever elect to open up areas of your site to only private (logged in members), these records will be available.