I've tried to keep the structure of BeebMaster as simple as possible, but in case you get lost, the information below on how things work may help. It's also a good reminder for me in case I forget.
I think of the BeebMaster layout as a hierarchical structure, a bit like an ADFS disc in fact. There is the home page, which is like the Root, linked to each of the main sections on the home page. Most of the main sections have sub-sections and some have further sections beneath until the lowest level of individual items is reached.
Clicking on the BeebMaster logo at the top of each page will always return you to my home page. Logos for main sections can also be clicked to go back to the main page for that section.
Each picture set has an index page with small images of all the pictures in the set. Each of these small pictures can be clicked to give a full-size image with further information. In many of the picture sets, I have put "Next" and "Previous" arrows at the bottom of the page to aid progress through the set.
I have started to introduce a link at the bottom of some of the index pages to explicitly refer to the parent page in the hierarchy. This is to eliminate the possibility of going round in an endless loop when using the Next/Previous arrows.
In November 2009 I decided I would try to make it simpler to view the pictures in a set by introducing a link on the large pictures to the next picture in the set, with the final picture linking back to the index page. This means that you don't have to scroll down for the Previous and Next arrows to continue, or return to the index page each time to see the next picture.
This new feature will be used for all picture sets created from November 2009 onwards, but it would be a lot of work to apply the feature retrospectively, so if clicking on a main image doesn't take you to the next picture, you'll have to use the old method, I'm afraid!
Many of my pages have references in the text to other items on my website and as far as possible I have put in links to the appropriate page so that you can see the item in question with a single click rather than having to search for it later.
At the very bottom of each page I used to have a the "back" option. This has exactly the same effect as pressing the Back button in your internet browser, i.e. you will always be taken to the previous page visited. Originally the "back" link was an explicit link to the referring page, but as the site developed and the number of links to other pages within the text increased, there was a possibility that clicking on the "back" link would take you to a page not previously visited, so I replaced all these explicit references with a relative link back to the previous page viewed. After that I erased all (almost all) of the back links as visitors seem to prefer using their browser buttons to shuffle about.
In my Domesday Section, I have added an additional navigation feature to some of the screenshots of the Domesday System in action. Clicking on the left-hand side of the picture will navigate to the previous picture in the set, and clicking on the right-hand side will go to the next one. This is akin to the navigation system used within the Domesday Machine.
On the technical side, I write all the HTML myself. This is done using GEdit in Ubuntu, I don't use any fancy software or tools for doing it. I don't have "templates" as such, but when I am creating a new page, I select one of the existing pages to use as a base and save a copy and then work on it. This means that I don't have to start from scratch every time and it also helps to ensure that all the pages are uniform in terms of HTML header information and layout.
For the first time in December 2009, I decided to try to collect together some of the more commonly used bits of HTML, such as the page headers, table styles, etc. into a single "library" document which I can use to cut and paste into new pages to help to ensure uniformity in the page layout.
The HTML pages are stored in different directories within my webspace according to which section they fall into. Picture files are held separately in a sub-directory to the relevant section, usually called "Pics" or "Pics". The only exception to this is that the pictures related to the Econet sub-directory are held in a sub-directory to the root directory's "Pics", called "Econet". It's just the way I did things when I started, but it's easier now to have a "Pics" sub-directory in each main section directory.
I make sure that links to other pages and to image files within the HTML code are always given in relative terms which means I can create all the webpages off-line and have a working local copy for updating and testing. I can then upload the finished pages to my webspace, which has the same directory structure, when they are ready.
Occasionally I need to do a blanket update to many - or sometimes all - my pages of HTML, either to fix some broken code or to apply a change to all pages. I used to use Regexxer, but I now use KFileReplace which I think is easier to use.
In 2011 I started using gFTP to upload files to my website. Previously I had used the FTP facility in Ubuntu's Dolphin for uploading files, but I always found logging in to be a little bit unreliable as sometimes it took a few attempts to get my online storage to display. gFTP is similar to a thing I used to use in Windows called CuteFTP, basically you get a local storage pane and an online storage pane and left and right arrows in between to choose which direction the up- or downloading takes place on selected files.
I was pretty good, but it couldn't cope with my December 2011 blanket update when I tried to copy everything in one go. It didn't seem to understand how to cope with directories, and I didn't want to have to go to the trouble of entering each directory individually, selecting all files and copying them across, so I abandoned it for that particular operation. I went back to Dolphin, although I wasn't able to distinguish between HTML and non-HTML objects, so I had to re-upload the entire site!
I now use Filezilla which is quite happy with recursive uploads. All I have to do is drop my local master directory over the remote one and it updates and replaces as necessary. It usually takes about 20 minutes, and will skip any file that hasn't been modified.
The only difference between my locally stored copy of BeebMaster and the online version is that there are additional items in the online directory "Downloads". This has two purposes. The first is for files I make available for people to download for their own use, such as a couple of disc images and utility routines etc. The second purpose is as a storage area for some files which aren't part of the main website as such, but which I want to send to people or post on a forum, such as a screenshot of something going wrong or an exciting discovery.
The Downloads directory isn't directly accessible by navigating around BeebMaster, but I have set the permissions so that anyone can obtain a directory listing of its contents and access any of the files if they are needed.
I try my best to keep any broken links to a minimum, but they do crop up from time to time. In the past I have had to rely on the kindness of visitors in reporting them to me, but in December 2011, I installed a utility called KLinkStatus which will check all links on a website. It can operate on filing systems as well as online, so I can check the local copy of my website for problems before uploading any changes. KLinkStatus has now been discontinued, but since about February 2015 I have been using Linkchecker GUI to the same effect.