Business Services and Projects
Web CMS Project
Guidance notes for completing the Site Setup form
Localisations created for a site at setup, Adminweb sites (example with Adminweb 3-column Style)
1
2
3
_
4
1.
5
Site name. This will be the site’s name in the CMS. It is also used:
(a)
in the breadcrumb3
(b)
in the text of the custom ‘File not found’ page
(c)
in the browser title bar, following the page name
(d)
as the name of the site’s area in the Media Library within the CMS
2.
Site URL. URLs are always lower case
3.
Default Style. Pages of the site will use this Style except where indicated differently in the Website IA
spreadsheet. Normally the defaults will be either:
(a)
Adminweb 3-column Style
(b)
Oxweb 3-column Style
The other default Style options are: Adminweb 2-column; Oxweb 2-column; Adminweb 1-column;
Oxweb 1-column. Use of these as defaults should be confirmed with the webteam.
4.
Banner1. The text of the site label to display on the banner (‘AAD Academic Administration Division’ in
the example). The UAS sub-label is compulsory for all Adminweb sites.
5.
Webmaster email address5.This should not be a personal email account. If a new generic account
needs to be setup, record the name(s) of the people who need to access it.
6.
Metadata
(a)
Used in the Description (shown e.g. in the browser titlebar) and DC.Title (Dublin Core title
value)
(b)
Site level keywords which will be added to every section. This list can comprise a maximum of
240 characters (including commas and spaces).
(c)
The name of the unit/group that owns the site, used for DC.Author
(d)
Temporal or spatial parameter for the site, e.g. the period of validity of the site content, or the
countries for which the content would be valid. Used for DC.Coverage, the default is
‘Unlimited’.
[DC or ‘Dublin Core’ is a metadata standard in the fields of library and computer science which defines
conventions for describing things online in ways that make them easy to find.]
Keywords can be added to specific pages using the ‘meta’ tag on the page section. This adds to the list
in 6(b).
7.
Users. This should list the users who will be maintaining the site, not only those involved in migrating
it.
In the default SiteManager workflow, a Contributor or Moderator adds content, then a Moderator
approves the content for publication. (Special workflow requirements are captured separately in the
Site Spec document.)
8.
Authorisation. The Site Setup must be authorised by the Site Co-ordinator, i.e. the manager who has
ongoing responsibility for the website. Authorisation may be received either by signature on a
printout of the form, or by an email direct from the Site Co-ordinator.
9.
Notes.
In addition to the above, the following features are setup by default for each site:
(a)
a local sitemap4
(b)
a local ‘collection’ on the University’s Google Search Appliance to provide the search area for
restricting searches of ‘this site’2 (Adminweb sites)
(c)
a utility to enable Google Analytics web statistics tracking for the site
(d)
a custom 404 ‘File not found’ error page with the following content:
“File not found
The server could not find the requested file. It may be missing or have been removed. You may:
1. Search 'This site' for related information held on the [Site Name] website using the search box provided above.
2
2. Select a link from the [Site Name] website Site Map
3. Go to the University Administration and Services Homepage and follow the menu choices given.”
10.
Oxweb.
The Oxweb Style has fewer local customisations. Items 4 (banner) and 5 (webmaster email address)
on the form are normally omitted. There is no local site search, and the footer including the sitemap,
and the Google Analytics tracking, are fixed and inherited from the parent site. A custom 404 can be
provided.
As the Oxweb Style does not support a local banner, the Site Name appears above the left hand
column instead, as well as in the breadcrumb6.
Nb: Adminweb Styles are always used for Adminweb sites. Oxweb sites normally use Oxweb Styles;
however, this is not a constraint. An Adminweb Style can be used, depending on the level of local
customisation required by the site.
NB: If the site is intended to go into oxweb therefore having url similar to
http://www.ox.ac.uk/somesite PAD will need to approve/Authorise the request prior to work being
carried out by the web team.
Localisations created for a site at setup, Oxweb sites (example with Oxweb 3-column Style)
3
6
3
4