I have a few years of experience coding basic HTML-related stuff on webservers, whether writing basic static webpages or perl/javascript reports, always basic reports, always oriented to "bite size" single pages that are easy to link to from a "link farm" index page. However I'm becoming interested in longer web documents.
I recently started a project to digitize a large collection of film negatives. The images will be automatically uploaded to my webserver, and I want to be able to browse through the pictures on the web. Sure there are probably web frameworks or CMS's that automagically do slideshows etc., but for pedagogical and stubbornness reasons I'm specifically interested in how to do this with plain-Jane HTML. I'm going to have a script to automatically upload the pictures as I scan them; I have freedom to create any filenames that I want, generating thumbnails is no big deal, and it's no problem to generate HTML pages to go with them, but I need to have some idea of a sane navigation structure in mind first. I would like this archive to be something I can add to for years to come.
I look at websites like this one, and I like how they have a main index page that links to each topic, while each topic itself has "next", "previous", "home" links on it, so it's almost like paging through a slideshow. This appeals to me in being simple and fast.
http://www.tldp.org/LDP/abs/html/regexp.html
I could do something like this in my film digitization project by generating and uploading an html document with every picture or every group of N pictures. I can have an incrementing number in the image filenames, so that I can populate the "next" and "previous" links correctly etc. Creating N static html pages for N images will be easy to do, but if I'm overlooking an opportunity to do this a smarter way I would like input. Does this make sense? This will form something like a linked list of html pages which COULD become a maintenance nightmare if I delete an image or something. PHP can do directory listing, for example, and then I could maybe have only one PHP page that would act as a slideshow providing, as in the static html case, I impose a sensible filename convention.
I prefer to avoid using any frameworks or CMS's, or databases if possible, because I just like to run as bare-bones as possible.
