IWeb vs Rapidweaver vs Wordpress

I want to create a website with a blog that has the ability to add comments and easily insert photos or video. I've been debating back and forth about using iWeb '09, Rapidweaver or Wordpress. Wordpress seems the most customizable but I'm somewhat intimidated how complicated it is to simply insert a video. Especially with iWeb's new features like custom domain name, simple insertion of pics and videos, plus Google Maps widget I'm seriously settling with iWeb, with the hopes that I don't outgrow it. I'm fairly computer savvy but know nothing about HTML hence my concern about user friendliness and convenience. Any advice would be most appreciated!
Thanks.

Alexander ~ Many here would probably agree that you should avoid using iWeb's often problematic blog. One easy-to-use alternative is the free, web-based Posterous:
http://posterous.com/faq
By the way, in iWeb there's a way to link to your external blog directly from iWeb's navigation bar.
Another thing to bear in mind is that iWeb is designed for personal websites, not commercial ones — so it lacks integrated Search Engine Optimization (SEO). If SEO is important to you, you may want to consider Sandvox Pro which has integrated SEO:
http://www.karelia.com/sandvox/getyour_site_noticed_andb.html

Similar Messages

Podcast RSS Feed - iWeb to Rapidweaver?

I currently have a podcast on a website that was created in iWeb and is hosted on MacHighway. The podcast is listed on iTunes. I'm transitioning my site from iWeb to Rapidweaver and need to update my RSS feed so that I don't loose any of my subscribers.
Would anyone know the steps to take for this process?

I am aware of the need to rebuild the podcasting webpages from scratch in RW--I actually look forward to it as RW offers much more flexibility and creativity in page layout than iWeb does.
Could you elaborate on the steps to do this?: "When you create the podcast in it just specify the URL and name for the rss file to be the same as before: then it will simply replace the previous file and iTunes will see it as before."
Do I need to somehow name the RW pages with the same naming scheme as the old iWeb pages? I hope not as the iWeb url was so convoluted and I want to streamline it.
Judging by what I'm reading on the forums, i'm afraid I'll just need to rebuild and resubmit a new url. This is by far the easiest. It just pains me to start my subscriptions from scratch -- I have two years of subscribers built up, and no way to communicate with them a new url for the podcast!
Thanks for your time and insights!

Move iWeb MobileMe Blog to Wordpress

I had to migrate my private Blog about my 2 years old little daughter from Apples mobileme servers to a wordpress account.
I wanted to keep all the comments too (Marlas birth..). So i wrote a perl script to do the job. It is far from beeing perfect, but it works for me. So it may work for you too. You have to adjust some things, that‘s for sure.
Features:
-Keep Comments
-Keep Images (hmm mostly)
-Sets email-adresses for comments by Name
-Sets Tags by text strings occured in title or body
-Free, but my daughter will get every euro you donate! THX!
Note: The script works only while the apple servers are up. After 30. June all your comments are gone!
http://iweb2wordpress.weinschenks.com/Website/iweb2wordpress.html

Cyclosauruswrote:
@MirkoW, would you like to wrap your pl script in an applescript app?
i can help you with that, so people like moopie can just double click and run your app without launching terminal.app.
sorry, i'm just can code some little perl. Applescript is completly new to me. I don't think it's worth the time since the mobileme servers are shut down in june.
moopie wrote:
Cyclosaurus, what an excellent idea! MirkoW, I gave it a try and got it to generate a file, but wasn't successful yet. I originally published my blog to a folder on my computer. The way my blog is set up, I have three separate sections, each with its own archive and RSS feed. Don't ask me why - it was the only way I could think to separate several different years of posts on my blog.
Hmm, we have to see if we can get the images right. The main problem is that iweb uses the same shapeimageXYZ.png shema for every post and wordpress need to have unique filenames. So my script is guessing the filenames wordpress makes out of them by importing. sorry my english is not as good it should for explaining in detail. Example
iWeb hat 2 posts both with
shapeimage_1.png
So the first post get's the filename shapeimage_1.png but the second post get's the filename shapeimage_11.png.
But what if you have later an image which has already the name shapeimage_11.png?
You got the problem?
For me it works with some tricks. so don't be afraid, i can look into it if you want.
moopie wrote:
Does the perl script need to be in the same folder as the posts I want to export?
No, the script does not use any local file, it get's all information directly from the mobileme servers.
Thanks for your patience - I do appreciate your help on this and I see the potential for your script. It's the closest thing to a solution I've seen so far. Worst case scenario, I'll get an engineer at work to help me figure out what to do!
can you give me the link to your blog? so i can look into the html code. I think that would be the fastest way to help you.

Opening iWeb in Rapidweaver

How do I open a iWeb files in RapidWeaver to upload FTP?
Thanks
Gary

hi timothylance
I upgraded from iweb06 to iweb08 within 24 hours of loading the website online (i use 1and1) to publish my website, I got a ton of complaints about the site crashing or hanging....
When iweb08 first came out, I had the problem and went back to iweb06, however I forgot about the issues of crashing/hanging for IE users and after 12 months redesigned the site in iweb08 again
again within 24 hours I got over 10 complaints, so I changed it back to the iweb06 and rang the clients that had complained and they said it was great no hanging or anything
I can only go by experience but each time I have tried to use iweb08, i get complaint, while using iweb06 I get no complaints....so it was a clear cut case
However I was getting fed up with having to add meta tags and other html after exporting, so I bought rapidweaver after reading the reports
I struggle thats its not wYSIWUG and doesnt look as good with ie as it does in safari
With iweb06 I dont see any difference with windows ie or safari
I need to be able to do what I do in iweb, but being able to have more functions, such as contact us pages, guestbooks and text flowing from one side to the other that seem so easy to do in rapidweaver

How to publish from iWeb to Wordpress

I want to take the advantage of those beautiful design sofware to create an amazing blog for my wordpress account. But I run into problem of not know how to do it and I do not want to live in the restriction of wordpress has for me on the web design.

There's no know method to conver an iWeb blog, design wise, to a wordpress blog. Rage software, however, has offered an application that can export the entries and comments of a current iWeb blog for use in an wordpress blog. Convert Your iWeb Blog to a WordPress Blog | iWeb to WordPress for Mac OS X But the design and layout must be created by wordpress.
OT

How do I move my blog posts from iWeb to Wordpress?

I want to move all my blog posts from iWeb to Wordpress. Is that possible and how?

Depending on how many posts you have, it may be best to copy and paste them into Wordpress. I don't know for sure, but I dought if there is any process that will do that automatically for you. I would have your iWeb blog (edit Mode) window open and then Create a new blog in Wordpress. Copy the iWeb title/paste into Wordpress - Copy the iWeb blog text/paste into Wordpress. It should go fast once you get the first one done because you'll do the same for all. Hope that helps.

IWeb, RapidWeaver, or GoLiveCS2?

If I ugrade to iLife06 from 05, I'll get iWeb, right?
Is RapidWeaver worth the extra money?
As an academic, I can get GoLiveCS2 from www.campustech.com for $75. This is a $399 retail program, and Adobe says it is "easy to use". Is this true? Will I get more than iWeb or RapidWeaver?
All I want is to publish family albums and videos, and produce an web newsletter for a club, but no e-commerce.

If I ugrade to iLife06 from 05, I'll get iWeb,
right?
Yes.
Is RapidWeaver worth the extra money?
Not if you have already purchase iLife with iWeb.
As an academic, I can get GoLiveCS2 from
www.campustech.com for $75. This is a $399 retail
program, and Adobe says it is "easy to use". Is this
true? Will I get more than iWeb or RapidWeaver?
The "easy to use" is all relative. GoLive is not as easy as RapidWeaver or (from what I can tell from Job's keynote) iWeb. It's in fact an application largely designed for professional web designers. For those with no experience making websites, it can be difficult to use. $75 is a great price for a product like that and it is certainly considerably more powerful than iWeb and RapidWeaver; but for your purposes, it seems overkill.

Allow comments. Wordpress no long offers iWeb to wp.

Old Toad Toad Hall, Temecula CA
In support of Ethmoid's suggestion of moving to a new host, etc. if you want to keep your blog's comments intact you can use Rage Software's iWeb to WordPress application to covnert your existing iWeb blog to an WordPress blog which can be hosted on your new server along with the rest of your iWeb website: Convert Your iWeb Blog to a WordPress Blog | iWeb to WordPress for Mac OS X
Too bad. MM is gone. I moved from MM to GoDaddy. NowWordpress no long offers iWeb to wp. Is there another way to allow comments on my iWeb blogs?

NowWordpress no long offers iWeb to wp
There's this: Migrate iWeb blog to WordPress - Mac OS X Hints. And MobileMe is not gone yet so you can try using the free scrpt provided to migrate youir blog to WordPress.
If you don't have a lot of comments to lose you can continue with an iWeb blog and add one of the commenting sites to you blog. Some are:
Disqus (an example is here: Disqus Comment in a Scrolling iFrame)
http://www.iwebformusicians.com/iWebMusicWebsite/Comment.htmlIntenseDebate comments enhance and encourage conversation on your blog or website
Echo - Products
OT

IWeb versus WordPress for blogging

Just seeking advice - I need to create professional blog which points to my registered URL (eg registered on GoDaddy - eg. www.robenzo.com/blog).
I am Ok with iWeb - but I find it rather clunky for everyday blogging. I don't want to have to migrate from one site to another in the future.
Anyone out there with experience with both iWeb 09 and Wordpress? Would you recommend simply starting with WordPress and not iWeb? Ultimately, I want my own URL not, the WordPress one. So just want to know which was to go.
Thanks

Robenzo ~ I've experimented with both iWeb's blog and WordPress's and I would recommend WordPress rather than iWeb. To use your own URL (Domain), see this doc:
http://support.wordpress.com/domain-mapping/
If you'd prefer something simpler than WordPress, there is this new, free web-based service which also allows domain names:
http://www.posterous.com/faq

Most needed new features in iWeb

I have been using iWeb since the beginning of it and I really didn't know a whole lot about SEO back then, etc...But now I do...I also use Rapidweaver and Wordpress.
Knowing that, going back to iWeb, it can still make some very original and nice looking sites if you start from a blank page, one can basically do what you want. It does its own graphic design, very easy drag and drop.
However since people LOVE blogs and make them alot, Rapidweaver and Wordpress are much better for search engines and SEO. Even sites like Blogger and Posterous are better blogging platforms than iWeb...that being said, iWeb blogs can be very nice looking. But are almost invisable to be indexed.
Heres why...first, the main blog page in iWeb (the summary part) is in javascript _*without .xml text*_.
This results in a search engine not seeing the actual blog entrees and therefore cannot follow the link.
The actual page where the post is written is still in java but the text is in .xml, which is readable to search engines. One has to a massive work around to get this done for indexing.
There are no categories, no tags, _no readable archives._ It is java also. What is readable by search engines is your RSS feed. Thats good.
Back to my title of the topic, what is needed in iWeb for its blog is catagories, tags, indexing archive links.
What is also needed is to re-do the html snippets to *not be an iframe*. Its not really a huge deal but has an interesting effect when building sites....I have two examples here for you.
First I built a little search engine in iWeb and also added it to a test site in Rapidweaver for the same search which Rapiweaver site is published on Mobileme.
When I add the code in iWeb I have to make the snippet window huge in order for the search to work on a published site, or you will just see the search box.
In Rapidweaver or Wordpress I add the code and thats it...when a search is typed in the box the results window automatically expand or the webpage itself expands to accompany the results. It is not an iframe like iWeb.
Also needed in iWeb are an adjustment in its URL publishing without having to go to an alternative FTP client, which takes a bit of extra time, but works. But for some can be confusing as apposed to just clicking the publish button.
I just love iWeb...but wish it would get its internet standards up...hope its not too late.
Alan
"I may receive some form of compensation, financial or otherwise, from my recommendation or link from clicking Google Adsense"
Message was edited by: bearkat

Heres why...first, the main blog page in iWeb (the summary part) is in javascript *_without .xml text_*
this is incorrect, iweb has blog-main.xml for blog summary page, ajax widget fetch data from the xml files and populate summary page.
The actual page where the post is written is still in java but the text is in .xml
this is incorrect, the text is on the entry page.
Back to my title of the topic, what is needed in iWeb for its blog is catagories, tags, indexing archive links.
that can be done, but you need to know iweb widgets, google 'iweb blog tag cloud' and look for my blog.
as for indexing, submit a site map to search engines and include iweb blog's xml files and your blog will be indexed.
What is also needed is to re-do the html snippets to not be an iframe
that can be done too, here is my example:
http://home.cyclosaurus.com/CyclosaurusBlog/Entries/2011/2/12Dynamically_ResizeiFrame.html

I've Made the Switch (from iWeb) & Lived to Tell About It.

I've gotten a lot of help and useful information from this forum over the years and I will certainly miss it. I've just completed a 2 month transition where I've migrated my site from iWeb/Mobile Me to a new site made in RapidWeaver and hosted by Host Excellence. I figured I'd write a little (or a lot) about my experience, to give some others an idea of what they've got to look forward too. Hopefully it will arm you with some things to do and look out for. While I am describing RapidWeaver here, a lot of this process will be the same no matter what new software you use. I started off being pretty happy with what I had going in iWeb and not being thrilled at all about making the switch. Now I am so glad I made the switch and I am far happier about the new site than I was with the old one. BTW: the new sites address is: http://grillinsmokin.net . Feel free to visit. I think you'll quickly notice some things you simple can't do in iWeb. This isn't a knock against iWeb. I was very happy with iWeb and had no plans to switch. Where it hasn't been developed actively for four years now, it has been left behind somewhat.
To begin at the beginning: I've had a site made with iWeb since January of 2006 called Grillin' & Smokin' that combined my love of outdoor cooking and photography. Over the years it had grown rather large, with 375 photo entry pages and 230 blog pages. The Domain file was around 1.4 GB. This was not something I ever wanted to have to recreate from scratch. However losing MobileMe as a host was taking away Value Added features like the Hit Counter, Slide Show, Blog Comments, Blog Search etc. The handwriting is on the wall for iWeb too. I might have gone on using iWeb, but between losing key features and the fact iWeb was starting to show it's age, it was time for me to move on. Just before the iCloud announcement this Spring, I began researching website building software. I looked at their features, working methodology, themes, plug-ins and extensions. I download trial versions of the software where it was available as well as some of the themes or plugins I might be using. I gotta tell you, at first I was very frustrated and upset, because I was not finding anything that had the ease of use of iWeb and looked like it was going to be able to recreate the appearance of my original site. It appeared to be a series of compromises. I'd like the features of one package but I hated the themes available for that software. Another looked promising but isn't being upgraded regularly. My biggest frustration was some of the iWeb page types just don't exist in other packages. For example the Album Pages where multiple Photo Pages can be grouped and displayed, don't have a direct equivalent in any other package I saw. As part of my discovery process I read reviews of the various packages, including head to head comparisons of some of them. I also visited their discussion forums. After doing this for 3 weeks I "settled" on RapidWeaver. It was under active development; had a thriving developer community turning out a wide variety of add ons, plug-ins and themes; had an active user community & had lots of help resources available. The web pages it produced were standards compliant and you could get nice effects without resorting to Flash. I think the biggest selling point was all of the add-ons-kind of the same advantage the iPhone has with it's App Store.
Once I bought RapidWeaver & a 3rd Party theme, I tried the demo versions of some of the plug-ins and made sample versions of my page types from iWeb in RapidWeaver. I wanted to have a process in place, before I started mass production on the site. You really do need to do some of this homework in advance to avoid unpleasant surprises. The biggest minus I'd turned up about RapidWeaver (RW from this point on) is it didn't handle big sites well at all. The equivalent of the iWeb Domain file is the RapidWeaver Sandwich file or RWSW file. Once the RWSW file reaches 100MB or so you can get crashes or hangs uploading your site. Now 100 MB doesn't sound like much particularly when I was talking about a 1.4GB iWeb Domain File for my site, but RW doesn't include the photos in the RWSW file. Still I knew I was going to have to divide my site across several RWSW files. Initially the plan was to divide it into 3 sites: The main landing pages was one RWSW file and is the site reached by the url for the site. I was going to have a second RWSW file for my blogs and a third for my photos. Ultimately I ended up dividing the photos into 3 RWSW files. These extra files are hosted on sub-domians whose name goes in front of the main domain (http://sub-domain.main-domain.com). This meant some extra setup for me with my web-host, although they made the setup for the 4 sub-domains very easy and they were free. If you have a huge site and will need to split it, you'll want to check with your prospective web host if they charge extra for hosting additional sub-domains. For small iWebs sites this is not an issue-you have one RWSW file and one web address, just like you do now. My having sub-domains also meant more work linking files together across sites. RapidWeaver has something called an Offsite Page which helped with some of this, but having to split my sites up was the biggest PITA for me about the whole process. But knowing about this going in was better than finding out at the end when I tried to upload a single massive site. If you have a small site, the setup for uploading it is as straight forward as iWeb. RW has a built in FTP uploader or you can publish to file and use an FTP client like CyberDuck.
Once I had my site organization in place and had experimented with best practices for recreating each iWeb page type in RW, it was time to begin. I've gotta tell you when I started out I was not a happy camper. I liked the iWeb way of doing things about 70 percent of the time vs 30 percent for RW. At the end of the first week I told myself I have to move on and give up on the past. I was no longer going to be using iWeb and the sooner I embraced the RW way of doing things, the better off I'd be. At this early point it was still hard to see down the road to the end results. No matter what new package you buy, you should try to go with the flow and learn a new way of working. You'll be happier and less frustrated in the end. In my case after having gone through the entire process now, I've ended up changing my opinion. Now that I've gone through the entire process, I like the RapidWeaver way of doing things about 95 percent of the time and 5% for iWeb. That 5 percent is mostly the large site issue I've described. As I began working I was able to reuse much of the text from my iWeb blog in RW. I did have to paste it in as unformatted and reformat it in RW. My pictures were well organized in Aperture which also helped speed the process. One of the things I did is automate some of the tedious repetitious tasks. I created Quickeys macros to do things for me when ever possible. For example I could go to a particular photo page in iWeb and select the first caption. I would then trigger a macro that asked how many captions are on this page. It would then select the caption in iWeb, copy it, switch to RW and paste it in place and repeat XX times. If you know Quickeys or Applescript (I am guessing) there are plenty of opportunities to put it to good use.
RW present a different way of working than you are used to in iWeb and you'll just need to get used to it. What I am describing here would be true of any of the other packages I looked at too. First off it isn't WYSIWYG while you are editing. You are working with fairly basic looking text with few clues as to what the real page looks like. You switch to a preview mode to see what the page looks like in a browser. At first blush iWeb seems to win here. But what I soon realized is RW allows you to mix regular text and pictures together with html snippets right in the same text box. This makes adding counters or badges easy. Plus you can use HTML formatting for things like Titles occurring through your page. Instead of increasing the font size, making the text bold and changing its color, you can simply say this is Heading style 2 or 5 and this happens automatically per the predefined style. Better yet if you change a style everything on that one page or the entire site (your choice) inherits that change. So by working in a non-WYSIWYG mode you gain some long term. advantages over how iWeb works. The same is true with positioning. In iWeb it is fast and easy to place things on a page right down to the pixel. RW just doesn't give you that type of precision and next to splitting my site, layout was my biggest frustration with RW. At least to start. But there is a good reason for this "lack of precision" that may not be apparent until you view the site in a browser. When iWeb came out, you really didn't zoom your browser. iWeb uses Absolute Positioning where it uses anchored boxes for everything, whereas RW uses Relative Positioning. Objects with anchored text or picture boxes like iWeb start having problems if you zoom in or out more than one step. Text starts over flowing other text because the text boxes are anchored by one point. Pages just start looking scary if you try to zoom in or out too much. RW is looking at items relative positions and their relationships with one another. So initially you aren't placing the objects in the same way, it is more like eyeballing things in a way. But when viewed in a web browser you can zoom in or out to your heart's content. So what seems at first like a big disadvantage at first for RW, is actually a HUGE advantage.
This is why you need to go with the flow and try to embrace the new way of working. I mentioned earlier that I wasn't able to find a page type that was equivalent to the iWeb album page. I was able to use a very flexible plug-in for RW called stacks, which allows you to create various single and multi-column or multi-row layouts using empty stacks. You then populate the empty stacks with content, pictures text etc. These pages were not like iWeb albums where you nest the Photo Album Pages in the Album page and they create a skimmable preview and an automatic link to the album. Once I actually started making these new "Album" Pages in RW I realized I was gaining as much or more than I was loosing. The skimmable preview pictures was eyecandy I could live without. Nice touch, not essential. I never liked the way the preview picture shown on the Album page was the first photo in the Photo album. You couldn't change this. Now that I am placing my own photo on the Album page, I could use any picture and make it any size I wanted too. In iWeb the Album Caption was the name of the Photo Page. If this name was too long the caption didn't go to a second line, it got cut off. Any link in RW can have a description added to the link which is what you see in the yellow box when you hover your mouse over the item being linked. I used to hide text boxes links under the pictures on the Albums page for SEO and navigation help. So yes now I have to manually link the Album picture to the Photo Page, but I am no longer creating a hidden text box with a link that I have to remember to move when I add pages to the album. So once again my first impression was wrong. Advantage RW.
Another advantage to RW is any page type can have a sidebar. You can easily add favicons and site logos. You can easily add metadata to any page and customized the names of the path to your pages. The Themes can be more powerful and customizable too. About one week into the process I was begining to really go with the flow and see this new way of working had far more advantages for me than disadvantages.
By the time I finished my new RW site, my iWeb site was looking tired and dated. My biggest and most pleasant surprises were saved until the end. Any kind of SEO was a PITA with iWeb. You had to embed snippets on each page with a code from HaloScan or Google Analytics. Problem was, iWeb erased any such HTML code while you were uploading. So you then had to use a regular expression in the text box ("HaloScan goes here"), upload your site and replace the regular expression with the actual code using a 3rd party tool. Oh and don't do that on any blog page where you are using the built in Apple commenting system because the comments will disappear. I also had problems where the new comment badge would not show up for weeks or months after a comment was made. It was getting so the things I had to do AFTER I uploaded my site to MobileMe were taking longer than uploading the site. Once the site was recreated, it was time to add blog comments, a guestbook, a contact form, Google Analytics, and publish a site map. In my iWeb-influenced mind, I was saving the fussy PITA things for last. I was dead wrong. Unlike what you go through with iWeb, it couldn't have been been easier in RW:
-Blog Comments: Set up an account with the provider. Then I had to go into the page setup in RW for my blog page and click on a popup menu of comment providers & select Discus. If your provider isn't listed you paste some HTML code from the provider into a dialogue box provided by RW for the blog page. In my case it was simpler, just set Discus in the popup menu. Now instead of the iWeb badge showing me new posts (and only when it was in the mood), I now get an email.
-Google Analytics: Set up an account with Google. Go to the Stats area in the RW side bar, click on Configure, paste in your code from Google and you are good to go. You can monitor your Google analytics stats right from within RapidWeaver. (Also works this way for GoSquared Live Stats).
-Guestbook: Same as iWeb. You add a page with an HTML snippet from your Guestbook provider in an iFrame.
-Contact Form: This is a RW page type which masks your email address from the spambots by transferring the information to an invisible and inaccessible page within your site. This page then emails you the information.
-Full Site Search: This doesn't exist in iWeb. You can search your blogs right now, but this is one of the features you lose when MobileMe shuts down. By adding an inexpensive Plug in called RapidSearch Pro I enable full site search. You set up a MySQL server for your site. Host Excellence walked me through the 4-Step Process via a well written Help File. You then control what pages are indexed via your sitemap.xml file. You let RapidSearch Pro index your site and you are good to go.
-SiteMap: There is a simple SiteMap generation feature built into RW 5. There are third party tools for doing this for iWeb. I purchased an inexpensive RW plug in called SiteMap plus that not only generates the sitemap.xml file, it allows you to customize what pages get searched and at what frequency. This ties into what is searched via RapidSearch Pro. This plug-in also generates a visible and customizable sitemap page to help your site's users find their way around. Another bonus of being hosted off Mobile Me is when I went to add my sites to my Google account they had already been indexed. It seemed like they never crawled MobileMe unless you told them you wanted them to look at your site.
Link Checking: This doesn't exist in iWeb. I bought another inexpensive plug-in called Link Inspector for RW. It checks all of your internal and external links and generates a report showing the status of all links. This was just what the doctor ordered for my large site. I will run it periodically to make sure external links are still working and that I haven't broken any internal links.
My site was pretty much wrapped up on Monday August 8th. I just had to add in Blog Comments, Google Analytics, the Guestbook, Full Site Search and the Site Map. I figured I would go public on Tuesday or Wednesday. To my great pleasure these 5 items took all of 2 hours to get set up and working. This was a nice touch after 2 months of hard work.
So there you have it. This is the process I went through converting my site over to RapidWeaver. Your mileage may vary. I am not pushing RapidWeaver for everyone. You have to find what program is the right fit for you. You may find staying with iWeb on a new host is the right fit for you. You need to decide if you can live with the features you lose once you aren't hosted on Mobile Me. For me there was great pain, but in the end there was a lot of gain too. I do like my new site and I feel it will serve me well for years to come. Good luck to all of you in whatever path you choose. Lastly thanks one last time to the helpful folks around here
Jim
http://grillinsmokin.net
Message was edited by: Jim Mahoney

Thanks Roddy. I agree with your take on some of the other software you mentioned, at least from the perspective of having dabbled with demo versions of some of the others. I will add that with Sandvox I felt a little nervous about it. Kind of almost like the software was a "hobby" effort a la the first gen Apple TV.
I also agree with some of your points regarding RapidWeaver. But now that I've built my rather large (for a hobbyist site) website with it I will have to respectfully disagree about it being at the same level as iWeb, or as you put it: a sideways move. While iWeb can be made to do things it was never originally meant to do, there are many places it simply can't go that RapidWeaver can. I was often hitting the limits of what you could do in iWeb, whereas with RapidWeaver, with one exception, I didn't feel like I was running up against any limits yet. The exception is it's lack of ability to handle large sites well. That was almost the deal breaker for me. I find it unexplainable that a software package with all kinds of add-ons helping you make more ambitious sites, can't handle those same sites in a single file. This was almost a deal-breaker for me. For folks who have small to medium sized iWeb sites this isn't a concern. There are also ways to warehouse images on the server to keep file size down, but this gets more complex than many folks coming from iWeb would want to do. Me splitting my site up the way I did was more work than I wanted to do.I almost bagged the whole thing and was close to just taking the old site down.
Now if we were to fantasize for a minute I can think of a way where I could also say iWeb to RapiWeaver is a sideways move: While I don't think iWeb '09 is the equal to RapidWeaver 5, I'd bet that iWeb 11 or the oft rumored iWeb Pro might have been. I kept hoping that Apple would keep pushing the limits of what iWeb could do and add in some missing features and head down the HTML 5 road.
I will conditionally agree on your saying that the shopping list for RapidWeaver can be substantial. I will qualify that by saying: Depending on what you are doing with it, your shopping list for RapidWeaver can be substantial. With one exception, I do think the base package of RapidWeaver is fairly priced. I think the basic Stacks functionality and a few basic stacks should be part of RapidWeaver. The more esoteric stacks can be pay as you go. When iLife 11 was announced without a an update to iWeb, I did some preliminary pricing and I was rather discouraged at the total. This spring I got more serious about things and repriced RapidWeaver and add-ons. After trying out various themes and plug-ins, I was able to sharpen my pencil and reduce the cost of entry considerably. One of the things that helped is the theme I bought had a couple features built into it. It had a nice lightbox type slideshow for photo pages and animated banners/headers capabilities built in. This saved me the expense of several additional plug-ins. Also while I have a blog, I don't consider myself a blogger. I was able to use the built in blog page and I don't feel limited by it at all. Some of the other ad-ons I bought: such as the link checker, site wide search and a more sophisticated sitemap generator were items I added because I could tell I would want to keep the site going long term. Those 3 plug-ins did that a a low price. I didn't think they needed to be built in.
But everyone's mileage may vary. RapidWeaver or any other web design program isn't right for every iWeb user. It all depends on personal needs, abilities and budgets. I'm just glad I can get back to posting to the site and not recreating it.
Jim

Iweb Blog ftp or mobile me?

I have just designed a website in iweb that I ftp through godaddy. Took a while to make that decision, but at least I have complete design control! I am doing pretty well and now at the search rankings stage and realize that iweb isn't great at that. Read some of the articles here on search rankings and downloaded the SEO guide and going to take actions with that, and also bought the godaddy search optimisation pack and intend to place the metatags/descriptions etc on my pages.
BUT, I now want to design a second site which is just a blog, which obviously isn't showing up through godaddy, so need to mobileme it. But, with a blog, how do you add the metatags etc to the pages, and are their individual pages for each blog posting? Does mobile me make it easy to go into each file and make the blog searchable? Just not sure whether to just design blog pages myself in iweb rather than their formatted ones, and use godaddy instead?
So, in short - mobile me with formatted iweb blog? or design own blog and ftp with godaddy - which makes the pages more searchable?

Welcome to the discussions. You'll probably have better luck making your blog pages more searchable if you use a dedicated blogging platform — most of them allow tags to be specified.
MobileMe is slow and problems with iWeb's blog are a recurring theme on these forums. For a success story with a non-iWeb blog hosted on WordPress, see this old thread:
To blog or not to blog
And to link to an external blog from iWeb's navbar:
Create a blank internal page titled "Blog" (Actually you can name the page whatever you want.) Then in that Blog page add an HTML Snippet with the following code:
<script type="text/javascript">
parent.window.location = "http://www.yourblogname.com"; // change this to your own URL
</script>
...Once published, clicking on "Blog" in the navbar will immediately redirect to your external Blog page. (Thanks to Cyclosaurus for the code).
SEO is important to you, but iWeb is designed for personal sites and, as such, Apple apparently thinks there's no need for Google. Web-design apps for business sites tend to integrate SEO — Sandvox Pro is an example:
http://www.karelia.com/sandvox/getyour_site_noticed_andb.html

TS2570 doesn't work, still the same problem when using Rapidweaver software. NOT with other software.

i tried everything in this article, but still have the same problem when using Rapidweaver software. NOT with other software. I am converting my iWeb site to Rapidweaver, whenever there is a calmer period in my office. I have 16 Gb RAM on my NEW iMac and have Parallels desktop, mail, safari, iWeb and Rapidweaver running simultanious.
I never have the problem if i don't use Rapidweaver, but after i have added several pages to Rapidweaver, the problem begins. my iMac won't start up. the only thing that works is re-installing Macos OS X 10.8. i tried even whiping the completeharddrive, and reinstalling with a complete new user, the same problem.
I had it on my previous iMac also, and bought a new one because i thought the problem was in the iMac first. i hadn't noticed it only happens with using rapidweaver.
i sent my complete rapidweaver project to the programmers from rapidweaver at Realmacsoftware, but they couldnt reproduce my problem, there macs started up without any problem.
i deleted all the rapidweaver addons and extra stacks, and started a complete new project.
saterday i had the problem again, after adding about 5 new pages to my rapidweaver site.
i think i have reinstalled Macos OS X 10.8.2 20 or 30 times by now
does anyone have a sollution?

Type '''about:support''' in the URL bar and hit Enter.
Scroll down almost to the bottom of that listing and see if you have '''user.js Preferences''' just above the '''''Graphics''''' category.
If you do have that, click on '''user.js file''' in this sentence. <br />
''Your profile folder contains a user.js file, which includes preferences that were not created by Firefox.''
Does that "different homepage" appear in that user.js file?

What is the best replacement for iWeb?

I have been using iWeb for a very long time. I need to move on to something that is being updated. What is the best replacement for iWeb? I see Wordpress needs special software to work on a Mac.
Thanks!
Pat

I have used HostExcellence in the past and they support all the CMS's including WordPress, so you should have no problems there.
The top CMS's that most have heard about and use are Drupal, Joomla and WordPress.
There is probably no best one, but you need to look at them all and use the one that best fits your needs.
I have used all of them in the past, but most recently Joomla and Drupal. Drupal has a reputation for being quite hard and Drupal 6 was, but with the advent of Drupal 7, things got a lot easier. There are a lot more themes that you can use and if you want increased functionality in Drupal, then you can download Modules and install them. You can have a membership site if you want it and this is easy to do - people can sign up for an account and you can restrict their access to certain parts of the site and then limit what they can do. You can allow people to complete forms on the site itself and the results to be sent to you. There is a Blog module that you can enable and that comes in Drupal Core with no need to download an extra module.
Joomla is good also and you can have a Blog with it too and there are lots of themes to choose from, but sometimes you have to pay for extras with Joomla - you can download Extensions and Plugins, but they may not always be free.
WordPress was always just thought of as a blogging platform, but it has evolved in to much more than that and you can now create stunning looking websites with blogs - there are a good range of free templates to choose from and if you want your blog on the front page of your site you can have this, or you can change it to another part of your site if you want a static front page. To extend functionality you can download plugins from inside WordPress itself, most of which are free. This might be the easiest one for you to use if you just want a website with a built in blog that is relatively easy.
Check out the others though at Drupal.org, Joomla.org and then WordPress.org.

How to publish iWeb online but not through iCloud but someone else?

How to publish iWeb online but not through iCloud but someone else?
Mybe Google or woodpress,
Or publish iWeb online with iCloud WITHOUT upgrading Lion?

iWeb will still be around but as Jeff pointed out if you want a blog with visitors comments you should consider converting your iWeb blog to WordPress. Rage Software has created an applicaiton that will convert your current iWeb blog w/visitor comments to a Wordpress blog. You can get the application here: Convert Your iWeb Blog to a WordPress Blog.
If you don't have visitor comments then the iWeb blog will continue to work for you on a 3rd party FTP server.
If you have photo pages in your website with the accompanying slideshow you'll need to read the following:
It's now confirmed that iWeb and iDVD have been discontinued by Apple. This is evidenced by the fact that new Macs are shipping with iLife 11 installed but without iWeb and iDVD.
On June 30, 2012 MobileMe will be shutdown. HOWEVER, iWeb will still continue to work but without the following:
Features No Longer Available Once MobileMe is Discontinued:
◼ Password protection
◼ Blog and photo comments
◼ Blog search
◼ Hit counter
◼ MobileMe Gallery
All of these features can be replaced with 3rd party options.
I found that if I published my site to a folder on my hard drive and then uploaded with a 3rd party FTP client subscriptions to slideshows and the RSS feed were broken. If I published directly from iWeb to the FPT server those two features continued to work correctly.
There's another problem and that's with iWeb's popup slideshows. Once the MMe servers are no longer online the popup slideshow buttons will not display their images.
Click to view full size
However, Roddy McKay and I have figured out a way to modify existing sites with those slideshows and iWeb itself so that those images will display as expected once MobileMe servers are gone. How to is described in this tutorial: #26 - How to Modify iWeb So Popup Slideshows Will Work After MobileMe is Discontinued.
In addition the iLife suite of applications offered on disc is now a discontinued product and the remaining supported iApps will only be available thru the App Store from now on.
HOWEVER, the iLife 11 boxed version that is still currently available at the online Apple Store (Store button at the top of the page) and those copies still on the shelves of retailers will include iWeb and iDVD.
OT

IWeb vs Rapidweaver vs Wordpress

Similar Messages

Maybe you are looking for