Filed under: iLife, Software, Features, Reviews
TUAW review: iWeb '09
Along with the other changes to iLife '09, iWeb was quietly upgraded to version 3. While the changes aren't as dramatic as those seen in iPhoto and iMovie, they do move iWeb further down the path to being a good web design tool for beginning to intermediate users.I'm in the process of writing a new edition of an iWeb book, and I took a month to go through iWeb in detail during my research. Click the Read More link below to see what's new in iWeb '09.
Publishing
One of the major complaints in the past from iWeb users had been that publishing on any web hosting service except .Mac / MobileMe required a lot of work. With the first two versions of iWeb, publishing a site to a regular web server meant that you had to publish the site to a local folder, and then upload or sync the folder to the web server through an FTP application. Publishing to MobileMe, on the other hand, was as simple as pushing a button. If it was your first time publishing a site, all of the files and content were uploaded to the site, while subsequent updates just pushed changes to the MobileMe server and made the updates quite speedy.
There was another problem with the older versions of iWeb. If you wanted to publish one site to MobileMe, and several others to other web servers, you actually had to create separate iWeb "domain files" (the single file in which all of the site and content info is stored on your Mac).
Apple has finally resolved these problems with iWeb '09. Each individual site can now be published to any server you want, while still keeping all of the website info in one easy-to-backup domain file. There's a new Site Publishing Settings page for each site, with a pop-up to choose between publishing to MobileMe, an FTP server, or a local folder. When you're publishing to MobileMe, you still have the choice of publising to a MobileMe address (i.e., http://web.me.com/whatever) or to a personal domain hosted on MobileMe (i.e., http://mycustomdomainname.com).
Publishing your site via FTP is as fast and easy as pubishing to MobileMe now, thanks to Site Publishing Settings (see below) that take your FTP account information and use a built-in FTP client to publish the full website or just changes to your server.

During my research for the book, I found that a lot of iWeb users were having difficulties with FTP publishing. It appears that many iWeb users are taking the FTP server and directory/path information from their web hosting providers and entering it into the Site Publishing Settings as received:
Directory/Path: /myhostingfolder
When you click on the newly added "Test Connection" button, this usually checks out OK if you've entered your FTP user name and password correctly. However, when iWeb goes to publish your site, this generally results in an error message that doesn't provide enough detail to tell you what's happening.
Apple, on the other hand, thinks that people should enter in that info in a slightly easier format:
Directory/Path: myhostingfolder
The differences are slight, but enough to cause a lot of people a lot of grief. Making this simple change in the Site Publishing Settings fixed the publishing error for both me and my editor, and I hope it helps others who are having the same problem.
All issues aside, the FTP publishing capability and the ability to set up publishing for each iWeb site separately are a welcome addition to iWeb '09.
Widgets
iWeb '08 introduced the concept of Widgets to iWeb users, and now iWeb '09 takes them just a bit further.
Two of the four new widgets are designed to take advantage of the iSight camera built into most Macs. The iSight Photo widget lets the iWeb owner drop a graphics box into any page, then take an iSight photo that is immediately inserted into the box. The iSight Movie widget (below) does the same, but inserts a short movie that has been recorded by the iSight. The latter widget could be very useful for iWeb users who want to record a video podcast on a regular basis.

There's also a new RSS widget for dropping an RSS feed into an iWeb page. This can be handy if you want to add a news or Twitter feed to your site.

The last new widget adds a countdown timer (settings page below) to an iWeb page. This works very well for adding countdowns until a new movie opens at theaters, until a birthday or anniversary, or until your least favorite politician is out of office.

Facebook integration
OK, maybe that headline is a bit misleading. iWeb '09's integration with Facebook consists of one thing; the ability to have iWeb update your Facebook profile every time you publish the iWeb site. Since I'm apparently one of the few people in the universe who did not have a Facebook page until I started working on the book update -- I now have a Facebook page in the name of Joe Shlabotnik -- I'm not really sure I see why this feature is that important. Of course, I'm an old guy, so what do I know?
When setting up the Site Publishing Settings for either MobileMe or FTP, there's a checkbox to enable Facebook integration. Checking this box opens up a Facebook login page into which you enter your user name and password. After that, each and every time the iWeb site is published, your Facebook profile gets a single line entry telling all of your Facebook pals that the site has been updated (see below). That could get annoying for your Facebook friends if you're doing minor tweaking to the site and publishing repeatedly. If you're doing a blog via iWeb, however, it's probably just as easy (and more flexible) to have Facebook watch your RSS feed instead.

What's still broken
With these features and capabilities, you'd think that Apple probably fixed some of the big annoyances with iWeb as well. Unfortunately, that's not the case. For instance, adding ALT tags to images in iWeb is still impossible unless you publish a site to a folder, then open and edit the individual html files. ALT tags are used by many screen reader applications to help the sight-impaired to navigate websites. A simple way to do this would be to have a way to take the descriptions or file name from any photo in iPhoto and use those as an ALT tag. On the other hand, putting a text title next to the photo can be just as useful as having an actual ALT tag.
As mentioned earlier, many people are still having problems with FTP publishing, so that needs to be updated or fixed.
Some people who are using iWeb for business sites have complained that they can't enter keywords for Search Engine Optimization tools. Easy workarounds for this would be to simply use key words and phrases in the descriptive text on the web page, or to use the HTML snippets widget to add keywords to a page.
A lot of the issues that people seem to have with iWeb '09 are due to the fact that they're trying to push it beyond what it's intended to be; a simple tool for creating a single website that's hosted on MobileMe or another web server. When I talk to people who are getting frustrated with trying to something that is beyond the scope of iWeb, I try to talk them into using an alternative tool.
Alternatives
Of course, for the audience that iWeb is targeting, there are a number of good alternatives. When friends and clients ask me what tool they should use to create a website, my first response usually isn't iWeb -- it's WordPress. It's a powerful, extensible, cross-platform, and free content management system that is constantly improving, and most web hosts now install WordPress upon request. Since it only requires a web browser to configure and edit your site, WordPress doesn't add any extra software to your computer.
Google Sites is another free alternative. While it's not as extensible as WordPress, Google Sites also offers one-click page creation, themes to change the look and feel of a site with a click, and a number of plugins to add other Google content (calendars, spreadsheets, Picasa albums, etc...) easily.
In the Mac world, RapidWeaver from RealMac Software is another of my favorites applications to recommend to website wannabes. This US$79 program is quite similar to iWeb in terms of how easy it is to initially set up a website, but it provides much more control over coding minutiae for those who prefer to tweak their pages.
Sandvox from Karelia Software comes in both regular and pro editions, with raw HTML editing and Google integration built into the pro version. The regular edition is US$49, while the pro edition costs US$79. Unfortunately, the prices just went up on March 1st.
If you want a path from a relatively easy-to-use web design app to one that has incredible power, then Softpress Freeway Express (US$79) is the way to go. When you have used Freeway Express to quickly design a site and expand on it, you can always upgrade to Freeway Pro (US$249) later to get all of the CSS layout and styling control you need for more professional design.
Conclusion
The new publishing options available in iWeb '09 are really the big improvement in iWeb '09, and for the first time it's actually quite easy to publish your iWeb site to some place other than MobileMe. While the changes in iWeb '09 are more evolutionary than revolutionary, it's good to see that Apple appears to be listening to the needs of iLife users and adding desired functionality (albeit slowly).
Of course, any short online review can't cover all of the features or issues of an updated application. If you have been using iWeb '09 over the last month and have discovered any undocumented features or workarounds, please let other TUAW readers know by leaving a comment below.

![TUAW [Cafepress]](http://www.blogsmithmedia.com/www.tuaw.com/media/tuaw-cafepress-promo.png)


Reader Comments (Page 1 of 2)
asisone said 7:45AM on 3-02-2009
But how the hell do you get an anchor point inserted????
That's a no brainer for building an FAQ page.
Argh.
Reply
Brian Allen said 7:53AM on 3-02-2009
One of the common complaints is the lack of multiple MobileMe accounts.
Another bad shortcoming in iWeb is the heavy usage of scripts to make the site work. This mean many browsers have problems displaying the correctly, but Apple is able to fix some of the scripting without upgrade iWeb, because the MobileMe scripting is on the back-end.
The scripting also means that many features are very slow. For example "My Albums" and "Photo" pages are completely driven by scripts. For a photo album, the scripts will have to read the complete photo subdirectories on the server prior to displaying them within the web page. This method is used for the blog, too.
The "My Album" page feature of scanning through the pictures requires all of the thumbnail image of the every photo album to be loaded prior to correctly displaying. It is simple math here: 40 pictures per photo page X 9 photo pages per album = 360 pictures plus overhead which is very high.
Sample Sites: http://www.brianallen.com/ or http://www.katiebeth.info/
Reply
John T said 8:01AM on 3-02-2009
I used the first version of iWeb and hated it beyond words. Now, I've done exactly what you've suggested and just used wordpress. I wish there was a front runner with this kind of stuff, because it would definitely prevail.
Here's the site
http://www.johnthrasher.net
Marc Mitchell said 7:58AM on 3-02-2009
ive always believed iweb can grow in to something very special .. i think the addition of the widget bar is a good sign, in the same way developers can make apps for your ipod, i believe web widgets will soon be another addition to the revenue stream.
from media players to guestbook, there are some simple things we would all like to see in iweb, wouldn't it be great to search a store for extras to make tweaking your site that little bit easier :)
MM
www.marcmitchell.net
Reply
Brian Allen said 7:59AM on 3-02-2009
Also, I firmly believe this version of iWeb was just an initial release to get something out the door.
The widgets are really a repackaging of an existing capability, but I can now see this is where future growth will be in the form of widgets.
Reply
Greg MacDonald said 8:32AM on 3-02-2009
If simply removing the ftp really works I will be ecstatic. I have been wrestling (without success) with publishing since I upgraded. In fact the built in easy ftp was the entire reason for me buying the suite. I thought to myself - finally Apple have done it, and being Apple they will have done it simply and well. That's what I get for trusting in horses or man's strength...
I am attempting to republish now. But its a big site and takes about 6 hours for the whole thing. Very much looking forward to incremental uploads after this. Doesn't look like much is happening so far.
Reply
semdigital said 8:52AM on 3-02-2009
I also went sans 'ftp.' and it worked just fine. Its just a really easy way to get your site made, and off the ground. When '09 came out, i had my site done in another program, i tore it all down and redesigned and posted the new one in an afternoon. great stuff. and to be able to "post changes" without publishing the whole site, takes no time at all.
Reply
Dan Wood said 8:53AM on 3-02-2009
Thanks for the mention of Sandvox. Actually we are delaying the (minor) price increase for a few days due to our internet host having our website offline all weekend. :-(
Reply
semdigital said 8:54AM on 3-02-2009
The only complaint...is font formatting. when you use a " ' " or extra space, a font error seems to appear. in the blog...or the main site just weird.
Reply
Zcott said 9:02AM on 3-02-2009
One of the things that irks me about iWeb (and not just iWeb '09) is the addition of random directories. For example, my site is located at zcott.com, but when I publish my website, it's all hosted at zcott.com/zcott/index.html, which is a bit silly.
The "site name" box in the publishing field should be entirely optional.
Reply
aaron said 1:23PM on 3-02-2009
Agreed. I tried iWeb once and got around this by bringing the whole site directory into dreamweaver and then doing a search&replace for all instances of the (annoying) sub-domain. A hack for sure but it works.
EMoShunz said 10:37AM on 3-02-2009
damb you, i'm trying really hard to wait to upgrade for 10.6 so i can get the package price, but those first 2 features you mentioned... i have to have them!
Reply
Jorn said 10:44AM on 3-02-2009
My dream is the best of both worlds: a slick, client-based editor/creator like iWeb, but the edit-it-via-a-browser joy of a CMS like WP.
I'd love to use iWeb to publish our family's site, but I'm afraid of this scenario:
WIfe: "I want to add some photos and news to our website during my lunch break. How do I do that?"
Me: "Well, you're computer at work is WIndows. You'll have to come home, fire up iWeb, and then republish your changes."
Wife: "Oh, well that sucks."
Reply
Mark B said 12:44PM on 3-02-2009
I like the way iWeb '09 is layed out. I have had serious issues with color resolution after publishing. My images "red" are blurry...someone mentioned RGB vs HEX vs other color option in iWeb '08. Do you know of anyone else having issues like this? This is when I publish a site that has images imported from other sources....Photoshop etc. doesn't matter if it's jpg, gif, png, tiff etc...all the same result...blurry color faded etc. Really weird.
I like iWeb's ease of use as I'm a visual builder and not a code guy...
Reply
David B said 3:05PM on 3-02-2009
The directory structure and file naming scheme is the biggest annoyance for me. At first I was really excited about the ability to publish to other servers via ftp, but now I have to publish to a folder just so I can re-code by hand all the silly links to sub folders (not to mention adding keywords and correcting some of the strange coding errors it generated). Very annoying, and almost defeats the purpose of iWeb for me - making quick, simple sites with no coding. I've also found that pages with a semi-transparent colour in the 'page background' do not display properly in IE6 or earlier (though I suppose it's not really fair... it is IE6 afterall).
I do still love it, though, for how intuitive and quick it is to make nice looking sites with enough polish to please the masses.
One feature I'd love to see - unless I'm missing it - is the ability in the colours panel to enter in hex values (though maybe that falls under the category of "not the market they're aiming for").
Anyhow, thanks for the review.
Reply
Ralph said 3:36PM on 3-02-2009
Two things I want in a future version of iWeb:
(1) support for multiple user/passwords for a password protected page.
(2) that damn icon to stop bouncing in the dock after it's done publishing.
Reply
Hubert Halkin said 5:21PM on 3-02-2009
Steven:
You mention WordPress as possible web builder. That is very interesting to me. I have used WordPress to easily build several blogs, but I do not know how to use WordPress to build standard web pages. Could you give the links to web pages created with WordPress?
Thank you.
Hubert
Reply
Howmanoid said 3:17AM on 3-03-2009
Thanks for a great post.! I've been looking for a good overview of what's new in iWeb since it shipped.
The server name thing is just plain wrong. Why would they assume that your FTP server name has to begin ftp. I'm not being sarcastic, that just seems like a ridiculous limitation..
The directory/path convention I kind of agree with. To reference "/directory" implies that the directory is off the root of the filesystem. Removing the "/" makes it relative to where your host configures your FTP space, which makes sense. Would be nice though if iWeb tried the obvious variations when it got an FTP error to see if it was a simple mistake. At least then it could offer a suggested correction and give you the chance to proceed.
Still. I'm starting to think my RapidWeaver days are numbered.
Reply
James Churchman said 8:46AM on 3-03-2009
maybe not aimed at iweb users, more proper webdesigners looking for a graphical tool but Flux is amazing, really love it
http://www.theescapers.com/flux/index.html
james
Reply
Buzz said 11:59AM on 3-13-2009
"Click the Read More link below to see what's new in iWeb '09."
Wha?
Reply