Static HTML II: Electric Boogaloo

2017-05-21

A year ago, I wrote about about using static HTML to manage my web site. Long ago in the before-times far-far away, I loved doing so, mainly because it was a lot easier and took less server resources (and also: it is more secure) than running a content management system such as WordPress or MediaWiki, and a lot less resource-intensive than SharePoint in particular. As an example of what SharePoint needs to run, maron my internal-only SharePoint 2013 server has 12 gigabytes of memory, and I bet it wants more.

I really like my blog workflow. I've had it for a few years and I consider it to be a weird but neat aspect of how I work and what I do on my work computers. The workflow is one of the few things keeping me on Windows, although I don't know if I'd switch anyway.

There are some disadvantages, mainly relating to the fact that it can't be, or is very difficult to do without the desktop version of word.

As a refresher, here is my blog-writing workflow:

  1. Create a new document in Word for Windows 2010 or newer using the "Blog Entry" template.
  2. Save the document to SharePoint. Edit it on any device that can connect to SharePoint.
  3. When it's time to publish the article, open it on Word for Windows 2010 or newer and click Publish.
  4. The article appears on my blog.

It's got a few parts that are very rigid, the beginning and end of the workflow need to be done on Windows computers, but (presuming Word is agreeting that day) the rest can be done on anything that can open, edit, and save docx files faithfully. I've written on Macs, Word for Windows (Mobile) and my iPad and iPhone with no trouble before.

Granted, Dreamweaver really isn't much more forgiving than that, you need to have a Windows or Mac computer on which Dreamweaver runs. Plus, you can't easily buy Dreamweaver CS6 any more, so I would be stuck installing old versions (which, to be honest, should do the work fine) or subscribing to Dreamweaver CC. There is also the issue of what CS6 would look like on a newer computer with a display running at a scaling factor of other 100% (such as a Surface.)

The only real problem with this plan is that there's no real incentive to do it. As part of running my email and synchronizing my other documents I'm already running SharePoint anyway, and I have the old WordPress and wiki sites running on an internal only server for the purpose of pulling content off and putting it into SharePoint. I could move that content into this site instead, but I'd rather move forward into a single system, instead of sideways into a modern site and a legacy site that I need to build new anyway.

I still like hosting my own and SharePoint still lets me do that, and patching is still easier than on WordPress.