Not necessarily a BETTER mousetrap
Well, it's about time I do something besides gripe about Best Buy.
The project to get all of the blogs online, as well as the web site a bit more up-to-date, was brought on by the upcoming season of Upward Basketball. I spent a lot of time on my web site last year, with the emphasis on A LOT. And worst of all, I didn't get everything I want to do done, because there simply was not enough time. I wanted the upcoming year to use some of the stuff I had built upon, but I'm hoping it will be significantly more complete.
So, in essence, my quest was to solve a few technical issues that have always handicapped some of the things I've wanted to do with my web site.
First on the list was the issue of pictures. Since we filmed all of the games with my camcorder (a Sony DCR-TRV38), using Pinnacle's Studio, it's easy to get some great pictures for each game. At least, from the standpoint of web-available pictures, they're great. I can select a few moments from the play of each kid, and then export those as .jpg images. This part of everything worked fine, and I intend to do it again this coming year.
The problem, however, became publishing the pictures once I had them. Last year, I simply used Microsoft FrontPage, created a page indexing the pictures, and then created a separate page for each picture, containing the appropriate linking. Talk about time-consuming. Surely there had to be an easier way.
This problem was solved (thanks to advice of my co-worker, Melissa Plunkett) by finding a good picture publishing software. That software, in my case, is NeoPhoto.
NeoPhoto let me organize my photos, and then create web pages on a separate server, using my in-home network to publish the pictures, rather than having to upload all the pages to another server. It's even a free package. All seemed well-and-good.
That was when I checked what the pages looked like. They looked reasonably well, although I was a bit annoyed by the advertisements. But I figured, "No big deal" as I was looking through the pictures. "I don't mind if someone puts up a few ads for their trouble of putting together this...." I came to a dead stop as I viewed a picture, and the advertisment text caught my eye. Apparently, some of the advertising being done isn't exactly the kind of thing I'd want to post on a system being viewed by kids from a church basketball league. Or their parents. Or *MY* parents. Or anyone from the church reviewing my site. In fact, I'm now no longer in a tolerant mood at all. These ads have to go - or the software does.
Fortunately, NeoPhoto lets you build and modify your own style sheets. While I don't know anything about building them, I can certainly look through one and remove the stuff I don't want. A bit bothersome, but all in all, not a big problem. And much, much faster than the way I had been doing things. It took me a little time, but I re-organized all of the photo pages on my site - many of which I had removed when I changed formats several years back.
My next issue to address was communication back to me. Of course, I have e-mail; I'm using Microsoft Exchange 2003, along with a Linux front end, in hope of fixing the spam problem I've had. More to come on that part of the solution, and a big thanks to my co-worker Rick Buford on the Linux expertise needed to do this. But, in my opinion, there needs to be a PUBLIC discussion area - one to allow for multiple people to sound in on the subject rather than me being continually in defense posture with only, "Well, it's going to go how I decide" to fall back on. And I'm not willing to try to do a public discussion area in Exchange. I've always been a sucker for old bulletin boards, and I figured that would be a good way of doing things.
Years ago, I set up a small internet BBS on my site using Ceilidh from Lilikoi Software. I love the format of Ceilidh, and I think it's a fantastic package. I figured I'd break it out again.
The biggest problem with Ceilidh is that it wants you to use your initial configuration in a specific layout - a layout which I did not want to follow. And Ceilidh's documentation for CHANGING that layout is sadly lacking. It took a lot of experimenting, moving things, and sometimes, trying to figure out whether the path used was meant to be a Unix path, a Windows path, or a web path. That tends to be the biggest area of confusion - and also ended up being the biggest confusion point in the blogging software as well.
I had to open up a few things on IIS in order to make Ceilidh work. Thanks to my co-worker Steve Lottes for helping me get it running. And it required a lot of time working and re-working the paths in order to get things working the way they should. But all in all, it was reasonable to set up a forum.
Then came the idea of a blog. I started out reading a review, which recommended a package called WordPress. I had a lot of stuff that I needed to install to get going. The stopping point came when I ran across a package called PHP. It wouldn't install properly on my test machine. It wouldn't install properly on my home machine. It just plain wouldn't install properly for me. I went to Steve again; he's the IIS-savvy guy. I asked him if he was familiar with PHP, and he said, "Yes; I've got it installed so I can run a blog." He then showed me his blog - which used Movable Type. He said the set-up of Movable Type was easy - and I thought his blog looked very nice. So I got Movable Type, and started messing with it.
PHP is an optional component in Movable Type, so my problem installing PHP was no longer relevant.
The Movable Type install faced one major obstacle: me. I decided to set it up on what was going to eventually become my production server. Invariably, I kept running across things here and there that just didn't work. Finally, it hit me: I was configuring a server that WOULD BE the production server, but was configuring it as if it WAS in production. Once I made that change, I really didn't have much trouble.
The most difficult part was taken care of by an article which walked me step-by-step through the install. There were a few configuration changes to make, and in one place, I managed to confuse a path which was actually a Unix path as a web path. Once I figured out that it was a Unix path, and once I substituted the appropriate Windows path, everything worked.
The one problem I haven't gotten resolved is the configuration of the Wheels portion for my friend John Crane, which doesn't use my domain of www.joev.com, but instead uses John's www.biglizard.org. Other than that one problem, Movable Type is working great.
Comment if you want information on the articles I used or links to the software pages. Once I get back in Columbia, I'll probably post the links here.
I've still got e-mail issues to resolve. More on that as that information becomes available.