I created my first personal web site in the 1990’s. When I created that first site I decided to use static HTML for the site for a number of reasons
- I had my hands full learning HTML and CSS without having to learn a server side technology.
- I was unsure which server side technology was going to be most useful to learn
- I was cautious about adopting a technology that would make it hard to migrate to a different provide for my web space.
Time moves onThese pages were fine and I had no real requirement to add anything for a while. Then around 2003 / 2004 I started to work on a shareware project called worldolio. It turned out that I needed to move my web space to a new hosting provider as I needed to be able to host ASP.NET web sites. I started to think about other things that I could do with my web site, given the nature of my work it seamed reasonable that I should have some method of publishing my CV and that led me to thinking about how to publish content in general. Most information held on a PC is held in Microsoft Office format, Word, Excel and Access etc. I share my web space with Steph and I have always though that it would be good if she could publish her work to the web. I was still unsure about what server technology to use, when I had last considered the options ASP/VBScript had been all the rage now it was ASP.NET, WordPress had only just appeared in 2003. Steph’s requirements were slightly different from mine in that she needed to reach a number of people who did not have access to the internet, or at least did not routinely use the internet in their professional life (this was the NHS in 2003 after all) I opted for an offline compilation mechanism. I could write a number of tools that I ran locally and “compiled” DOC and MDB files into HTML. The first part of that process was to extract MS Office files as XML and for that I modified some example code from Microsoft to create a Conv2XML tool that would do this. online books catalog is compiled from an Access MDB file. The main advantages of this mechanism are
- Can be hosted on any web server capable of service static HTML
- The resultant HTML can be burnt to a CDROM and given to people with no internet access and viewed by just using IE to access to files with the need to a web server at all.
- The content is created in Microsoft Office, Word, Excel etc in an environment that is convenient and familiar to the user.
where to now?This year a number of things have conspired to mean that I have revisited my web site.
- I needed to update my CV as it has been too long since I did that.
- Microsoft Office now natively supports XML based formats such as DOCX
- I spent some time listening to the rissington podcast where I got to hear about what was happening with content management systems
- I felt that server side technologies had started to reach a level of maturity where I could reasonable expect to be able to find ASP.NET hosting easily and cheaply. I have been using webstrike solutions for 5 years and would not hesitate to recommend them, their performance has been flawless.
- I now had access (no pun intended) to mature inexpensive backend database technology in the form of MySQL and SQLite.
- There were some issues with the “compilation” mechanism that could be addressed.
- Changing the design of the web site was a nightmare. To say that the design was not WYSIWYG is an understatement. The HTML was originally written in notepad (or Interdev if I was feeling like colour coded syntax) and then chopped up and placed into XSLT the data XML was applied to produce HTML
- From the point of view of publishing a CV, the market has moved on. It is less of a priority to be able to produce a CDROM. In fact it would appear that what is really needed is the ability to download a PDF or DOC file.
- If the code is written carefully it should be possible to have the same code able to run on a desktop to support compilation to HTML and also run on a server to support a dynamic web site.
- The HTML was very old and needed to be updated. The HTML still had support in for Netscape 4 ILAYERs but as a result used TABLE to achieve its layout.
- The compilation process used a number of pieces of technology that were becoming obsolete, for instance VB6, Saxon 5 and Microsoft Java VM