iWeb
Now for iWeb. Some of you may have noticed I took this blog down and replaced my page with a new iWeb created page that looked awesome. iWeb makes it SO easy to create cool looking webpages that within about 10 minutes I had what I thought was going to be a pretty bitchin web page going (although Mckell gave me shit for just about every word on it). Well, after spending an hour or so adding photos and customizing it just the way I liked it I started to realize some pretty big holes in the program. Enough, in fact, to force me to stop trying to build a web page using iWeb and just go back to my regular old blog. Here were the features that I felt were critical that iWeb doesn't support (yet).
- No way to create photo albums. Sure it has an unbelievably nice system for importing photos from iPhoto and creating photo pages, but it offers no way to create an album page where people can then click on albums and go to the respecitve photo sets. I can't believe they didn't add this feature and I'm sure they'll be adding it soon.
- No way to publish the site to your server. The only way iWeb will automatically publish your site is if you have a .mac account. Otherwise it only allows you to export your site to a folder on your computer. You then have to manually upload that folder to your server via a 3rd party FTP client. This might not sound like that big of a deal, but once you get your page designed and finished, you are forced to publish your entire site to a folder (which can take quite awhile) and then upload it to your server (which can take quite awhile as well) every time you want to publish a new blog post. In other words, if you have a large site it can take upwards of 4 - 6 minutes just to simply update your blog. Big, big, big problem in my opinion.
- Way too much .mac integration. Want photo albums? Gotta have .mac. Wanna have a page counter? Gotta have .mac. Wanna do a bunch of other things? Gotta have .mac. .Mac is a ripoff in my opinion and I think it's REALLY annoying to keep trying to push users into using it. It's fine if they want to offer .mac integration, but don't design the entire program around .mac and then leave all the regular server users out of the loop.
- Inability to view the HTML code. This was another issue that I thought was really annoying. There is NO way to view or edit any of the HTML iWeb creates. Here's a real world example of how annoying this can be. I recorded a little intro for my web site and wanted it to auto-play whenever anyone went to my page. iWeb makes it all too easy to add the audio to my page, but doesn't have an option to enable any kind of auto-play. If I had access to the HTML it would have been as easy as changing the value in the AUTOPLAY="never" command to "always" but there is no way to do so, and so it makes it a huge pain in the ass to get it done.
There are a few more little gripes I have but for the most part those are the biggies. Overall the program is really, really cool and it does make creating a really good looking web page about as easy as it could get. It is, however, blatantly obvious that this is a 1.0 application and still needs a lot of work. Luckily Apple seems to listen when people complain so I've done my part in getting things changed. Now do yours.




