I thought it might be useful to others to understand the rational for how I do things here at the gopher/web server. As a start, I tend to produce files that can be read unrendered with a simple text editor, because I hand-code all the pages that you see on (wait for it) a simple text editor!
In accordance with the Berne Convention, all of my documents are automatically copyrighted in my name at the time they are produced. As I do not specify any particular exceptions, you must suppose that you have no rights to their use. By my placing these documents on a public network server, you can only imply that it is allowable for you to read them and make a copy for your personal use. All other rights are reserved by convention and myself and can be had only on a case-by-case basis.
In my HTML production, I choose to work as simply and easily as possible.
I use, as much as is practical, the primitive, pre-standard HTML specified by Tim Berners-Lee back in 1992, as it is concise and clear and is parse-able by even the most antique and simple web browsers. When tempted by a newer HTML tag or CSS or a Javascipt fragment that would make things "cool", I tend to eschew such.
I use links heavily in my documents, both for reference and server navigation. I tend to use titles to point back to higher levels in the structure of the document store rather than menus and breadcrumbs that require dynamic tracking. All documents are static and tend to stay where they are put and their URLs rarely change as this would tend to complicate my life.
My HTML editor of choice is the version of Cooledit that is embedded in Midnight Commander. I use an older version packaged for Debian "Woody", as this is my server OS of choice. I tend to follow the highlighting conventions of HTML in Cooledit so that I can take advantage of its facilities for syntax checking. I do deviate from my primitive HTML style when highlighting made for more modern tags proves more useful from an editing standpoint.
The organization of my server is sloppily designed to create a vaguely logical hierarchy while making for short yet humane URLs. When I do make a change that affects a document's URL, it is usually to create more order rather than producing shorter URLs. Chaos soon becomes unmanagable.