Content versus configuration

Context: see TGSoc discussion (updated 10/11/21)

03/27/2019 -- Might go with Emacs (on the PC). Using Wordpad, for the most part, so no help for the old eyes. And, matching up the 'tags' can be a problem (Emacs would mark them). Case of configuration concerns that clash with content. Now, the ease of edit with some website creator is weighed against what they stuff in (remnants of frameworks, and such) when writing the HTML.CSS is a huge parametric system that is continually being extended. Some trashed it early on (before 2008), but now we see something quite remarkable. 

03/20/2019 -- At home page, there is a link to a page with a text scroll that is from the timeline published in The Gardner Annals, Volume I, Number 1. This is a beginning of several changes that are pending. ... One thrust is to clean up the HTML. I have been using Sea Monkey's Composer, but, of late, it has brought in junk much like I used to see with MS's editor. So, I'll be doing HTML by hand until I find a good editor. Other changes relate to interaction by groups and ecommerce.

01/20/2019 -- Look at the footer handling. The other day, we put the 'search' button on that brings up a Google service. This search, now, goes against with the purpose of building an index to our publications. Then, we got registered with Google non-profit. Bringing in snippets changes the game. To now, the pages were like an interactive book. That meme will continue in part. We will have some things dynamic in order to support our activities. However, the major configuration will be HTML/CSS/Javascript until we have converted away static coded. This portal will be our initial tryout and release framework. Later, we'll have a sandbox to allow others to contribute to the coding and administration effort (again, Linux and NoSQL - naturally, now, the 'No' means 'no' until we bring in SQL - which we did momentarily, before). So, the footer has been changed from 'document.write' to using elements and 'innerHTML' (until we see some clear choice between that and the modify method). Next up will be releasing the 'image index' code that uses JavaScript. Then, we will be changing the menu bar (left) to use JavaScript. See next note about the images (these old trials left here so that we can write about the approaches looked at).

01/03/2019 -- See Home (main page) for example of using JavaScript (NoSQL, sense) to build the image list. We will use that as the new basis and change the below.