GENUKI Maintainers' Pages
Skeleton Parish Page
There are excellent tutorials on the internet on the subject of HTML and how to create and correct web pages; this is not intended as a substitute for lessons in HTML. However, using only this section, a new maintainer with a rudimentary understanding of HTML should be able to construct and edit GENUKI web pages. There is also a very short tutorial covering the principles of the minimum HTML required for GENUKI purposes.
The sections that follow explain how to create a GENUKI parish page that conforms to the mandatory technical standards. The method used in these sections is to exploit HTML features which do not make use of styles. Most of GENUKI's pages do not use styles - indeed many were first created before styles were developed. However, using styles allows the creation of a similar, and conformant, parish page using much less HTML, and so maintainers are encouraged to familiarise themselves with styles and to start employing them. For further details see the GENUKI style sheets page.
Once you've created and/or updated a GENUKI parish page, it should be easy to extend your experience to the creation and updating of county and other GENUKI pages.
The HTML snippets in this and the following sections are all incorporated into the parish template which is provided to assist maintainers in creating new, or updating existing, parish pages. The template includes HTML that can be modified to fit a specific parish (and county) name. Each of the snippets comes in two versions - a basic one, and one which is abbreviated by means of the use of styles. For example the basic version of the Button Bar at the top of each GENUKI page contains HTML which specifies which icons to use for a given button, its width and its height, etc. The Styled version of the Button Bar is briefer and simpler, and more likely to be correct, because it omits this information, which is defined within the relevant style declaration.
The template, the HTML snippets, and other web pages shown here, were all designed to be served from the /maintenance/ section of genuki.org.uk, and therefore use the appropriate relative addressing of images, style sheets, and other pages and folders. Maintainers wishing to extract HTML code will therefore need to alter the relative addresses if the code is used at a different level in the GENUKI folder hierarchy. The section on Folders and Files provides guidance on relative addressing.
The aim of GENUKI branding is to ensure that users who reach GENUKI via a link from some other website realise that they have arrived at a GENUKI page. One part of the branding is to ensure that all GENUKI pages adhere to the GENUKI look and feel which these skeletons implement, and this is often accomplished by icons and button. GENUKI branding is less evident, but just as important, in:
- the <title> statement of the header
- the <meta> statements of the header
- the <alt> clauses in image statements
The GENUKI branding in title and meta statements has been included in a GENUKI Branding snippet.
Icons help provide a distinctive look and feel but they can delay access to the web page, and not all readers can use them. It is recommended that new maintainers stick to the use of the standard GENUKI button-bar icons. The section on Folders and Files provides advice on the standard location for icons and other images.
There is a set of standard GENUKI button-bar icons for placement at the head of web pages. All GENUKI pages must contain at least:
- the GENUKI logo which links to the Home Page
- an up-arrow to the immediately higher level in the page hierarchy
- a button linking to the Contents page
These button-bar icons are often referred to as the Basic Navigation Bar. In the example which follows, the web page is assumed to be located at the Parish level and so the up-arrow points to the County page.
There is an equivalent set of button-bar icons created using styles and referred to here as the Styled Basic Navigation Bar.
In addition to the minimum three button-bar icons, a GENUKI parish page must also have:
- a link to nearby places
- an up-arrow to the county page
- a link to a list of towns and parishes in the county
At this point, we'll also add an optional icon with a link to obtain a map centred on the parish. Let's call this the Parish Navigation Bar.
As before, there is an equivalent set of button-bar icons created using styles and referred to here as the Styled Parish Navigation Bar.
At the bottom of every GENUKI web page, there must be:
- the date the page was last updated
- the GENUKI Copyright statement
- a link to validate the page's HTML using the W3C validator
- a way for readers of the page to report problems and errors to the author
An error reporting mechanism has been adopted which results in emails being directed automatically to the email address nominated by the maintainer for this purpose in the county database table. Note that this doesn't have to be the email address of the maintainer, simply one that allows problem reports for the county to be received and a response generated. The providers list contains the names of country and county maintainers.
The update date, Copyright statement, W3C validator, and error reporting button can be added in a combined set we've called the Parish Terminator.
There is an equivalent set using styles we might call the Styled Parish Terminator.
The complete parish template is available for maintainers to use. This page will, of course, need to be tailored to suit a specific country, county, parish and maintainer but the places to insert the country, county and parish are fairly obvious. If in doubt, look for instances of "uuu", "ccc", and "Parish". Further tailoring will be needed to centre the map on the parish and add the maintainer's name as author.
Note that, when adding a new parish page, the maintainer will also have to add entries to:
- the list of parishes in the county
- the gazetteer
- the church database
Similarly, a complete styled parish template has also been provided and is available for maintainers to use.