Microsoft FrontPage: The Good, The Bad, The Ugly
FrontPage was one of my early forays into web design. I started with cobbling together basic HTML, but my skills in the late 90s/early 2000s were pretty weak. I then discovered Netscape Navigator’s editor. I can’t remember if they stopped supporting the WYSIWYG tool, or if I outgrew it, but the next tool I used was FrontPage.
When I created the website for Christ Episcopal Church (in Seattle’s University District), this was the tool I used. One of our members was on staff at Microsoft, so was able to donate a copy to us. And so I was able to bring the church into the 21st century.
I knew enough HTML to edit the code that FrontPage crafted, and I remember tweaking things from time-to-time. But I don’t really remember much in the way of detail. Reading this article taught me several FrontPage features that I was oblivious to, key amongst them: tasks. It’s pretty cool how the tool was built with a project management focus.
The article goes into the acquisition of Vermeer (the creators of FrontPage), and ensuing issues with hyper-proprietary technology. (Side note: I had no idea that FrontPage was created outside of Microsoft and then brought in by acquisition). And also looks at the other WYSIWG competing editors, and what all of them lack.
It was fun looking back at this clunky tool. It was almost great. That, and a Starbucks gift card, will get you a cup of coffee.
[…] mostly with WordPress, but I’ve also used HTML as well as tools like Netscape Navigator and FrontPage. So, I’m disappointed I’ve never even heard of Joomla (or Drupal, for that matter). […]