CSWeb provides dual document views: basically, one set of pages for people external to UKC, and one set for people internal. So, for example, there may be two versions of Fred Bloggs' business card page; one internal, the other external. The internal page might contain Fred's telephone extension number and teaching details, while the external page might contain Fred's direct dial telephone number and no teaching details. [Example: internal and external view of the business card web page for Tim Hopkins.]
When a person first visits the Computer Science web site http://www.cs.kent.ac.uk/,
they are automatically directed to the relevant view. Anyone connecting from
a machine matching the domain *.kent.ac.uk is coming from the university
campus and is sent to http://www.cs.kent.ac.uk/welcome.local (the
welcome page for the internal view). If the machine is from any other domain
then they are coming from off-campus and they are directed to http://www.cs.kent.ac.uk/welcome.html
(the welcome page for the external view).
So to summarise:
Filenames ending in.localcannot be seen outside of UoK.
Filenames ending in.htmlcan be seen both outside and inside UoK.
Once directed to the correct welcome page, all further links point to pages
in the same view. That is to say all links from welcome.html point
to filenames ending in .html. This ensures the user always stays
in the same view.
Since staff and students are typically accessing the web site while they are
at the university they are directed to the internal view. Internal users can
see the external version of a page (if there is one) by changing the file extension
part of the page URL from .local to .html. Some local
pages already contain hyperlinks to their external counterparts. Note that external
users can not do the reverse operation and change .html URLs to
.local ones, for the reasons detailed above.
Most build scripts produce the internal and external views automatically for
you. When publishing general web pages using the bap
build script you must specify whether you want the external view, internal view
or both by providing the -e, -i or -b flag. The differences in content between
the two views is achieved by using the template language constructs #local,
#endlocal, #external, #endexternal and
html inside the template. Please consult the Template
Definition Language for further details.
If you have a lot of web pages which you want published with a local view only,
you can create a directory called LOCAL-ONLY and place all your
web pages in it. Anything published under a LOCAL-ONLY directory
has the local view regardless of the web page suffix (.local, .html). This local
view also applies to sub-directories of LOCAL-ONLY.