GENUKI Maintainers' Pages
Skeleton County 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 county 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, county 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 county page, it should be easy to extend your experience to the creation and updating of parish and other GENUKI pages.
The HTML snippets in this and the following sections are all incorporated into the county template which is provided to assist maintainers in creating new, or updating existing, county pages. The template includes HTML that can be modified to fit a specific county (and country) 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 County level and so the up-arrow points to the Country 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 county page must also have:
- an up-arrow to the country page
- a link to a list of towns and parishes in the county
- an internal link down to information related to "All of the county"
Let's call this the County Navigation Bar.
As before, there is an equivalent set of button-bar icons created using styles and referred to here as the Styled County Navigation Bar.
Every county web page needs an alphabetic list of parishes which act as links to parish pages.
The GENUKI convention, based on that used in the Phillimore Atlas and Index of Parish Registers, is that parishes that are part of a significant town (or were in the past) are listed by indenting them and prefacing them with the town name. This town name can then serve as a link to a town page, on which there can be additional links to the parishes.
The list of parishes will be lengthy and the parish names should be grouped alphabetically under their initial letters. A long list of parishes can be moved from the county page to a separate page which is linked from the "Towns and Parishes" button-bar icon on the county navigation bar; see the section on the complete county template for details.complete county template.
The FFHS provides us with a list of contacts for all societies in the Federation. This covers nearly all English and Welsh societies and is available for maintainers as a reference.
Each entry is accessible individually by name and a simple reference can deliver the reader to the specific county FHS website or contact point. A sample lookup is provided but, note, that the specific FHS is located by a unique anchor number which you must obtain from the list above.
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 County Terminator.
There is an equivalent set using styles we might call the Styled County Terminator.
The top of the county template web page, complete except for specific parish content, displays as follows:
The complete county template web page is available for use by maintainers. It will, of course, need to be tailored to suit a specific country, county and maintainer but the places to insert the country, county and maintainer names are fairly obvious. If in doubt, look for instances of "uuu", "ccc", and "Maintainer". As elsewhere, there is a styled county template web page.