What resource should I use to make site public?
By resource do you mean web hosting service? This may be of help to you: Life After MobileMe.
Some of the hosting services offer domain name registering and it might be worth while to transfer the domain name to the new host to consolidate everything. In the link I provide check ou the link Tutorial iW16 - Using HostExcellence.com to see what I mean about having both in with the same provider.
You wrote: "I have a domain name through GoDaddy, What resource should I use to make site public?"
Why not host your domain at GoDaddy? You've got DNS there apparently, now just add a year, or two of hosting that supports FTP, then setup the iWeb to upload to your DomainName.xxx with your ftp name and password, then publish.
If you are still using iWeb '08 you need to publish your site to a local folder and upload it using an FTP app...
Which hosting plan you choose will depend on the number of sites you have, or will have in the future. Some info about choosing hosting...
Check out this video tutorial, it will explain everything you need to know to get your iWeb site up and running with your godaddy domain;
I recommend transferring to the above iweb hosting as they provide better customer support for iweb built sites over godaddy.
That might be so, but as the OP already has a domain name registered with GoDaddy, it makes more sense to purchase hosting from GoDaddy, so that you keep everything under one roof and GoDaddy is very easy to use - I have used it in the past and had no problems at all uploading my site.
Also, why would you need more support for iWeb built sites? I don't really understand this, as at the end of the day, when it comes to publishing it is the html and css files that are being published and it has absolutely nothing to do with iWeb in the end - simply the html and css files.
The OP is also still using iWeb 08, which does entail publishing to a local folder and then uploading using Cyberduck, which makes it even less an iWeb issue in the end. Still all boils down to the html and css files.
Judging by the questions asked here and the level of tech knowledge of most iWeb users I would say that going with a company that knows iweb is much better in the long run.
For example I was getting an error when trying to publish my site through iweb. Turns out it was a publishing bug with iweb. My original host couldn't help me since they hadn't even heard of iweb before. But rage provided a video tutorial, and a free tool, to work around that issue for me. I would say that is a good reason to go with a web host that really knows iweb, no?
The video I'm referring to here is this one;
I would agree that it helps the newcomer to FTP to have a hosting service whose tech support understand the unique structure of iWeb created sites. I have lost count of the number of users who have asked me to sort out problems created by tech support employed by numerous hosting services - including the mighty GoDaddy.
A lot of tech support people don't seem to bother to look at the form and function of the iWeb index.html files and advise users that they have to rename their home page to "index". While this holds true for most websites, it certainly doesn't apply to iWeb.
Its not "simply the html and css files". How many users come unstuck when they forget about the feed.xml?
People who hand out advice in this forum about uploading files via "Cyberduck" tend to miss out the part about the importance of maintaining the site structure by uploading the whole folder created by iWeb plus the external index.html.
They also may not have been around back when I first announced that I uploaded the contents of the iWeb folder to get rid of the site name in the URL. I was shot down in flames by the iWeb "experts" and told that this was impossible - even although I was obviously doing it!
Although this method of uploading the files has become accepted practice in the iWeb community I wouldn't recommend it to those who are new to FTP unless they have help from a tech support person who actually understands the problems involved and can point out the downside. Those who claim that it is "simple" and "easy" have obviously forgotten the first time that they tried it!
A lot of the people who come to this forum for help with FTP end up in a complete mess due to the conflicting and inadequate advice they get due to the fact that the "adviser" hasn't a clue about the hosting account structure and can't view the actual files. In many cases, I have had to go into the users hosting account and sort out the mess created by bad advice and ignorance. This should really be done by the hosting service's tech support but, in many cases, they helped create the problem in the first place.
The mere fact that an iWeb user has to come to this forum for help with FTP seems to suggest that their hosting service has inferior tech support.