Organizing in Iweb

Im working on a site that is going to have around 100 photo's on it.I will have 6 galleries with aprox 15 photo's per gallery is there any way in the side bar I could put these photo's with there respective galley in some type of a folder?
I have to scroll down pretty far to make all the links happen.
Thanks

Add a Photoalbum page and add 6 photopages with 15 photos each.
http://www.apple.com/ilife/tutorials/#iweb-photoalbum

Similar Messages

Organizing my iWeb site

I know I have to be missing something real simple but I am drawing a blank on how to solve it this morning. How do you get your pages to nest in iWeb. I can create sites & pages with no problem. I checked the help and it says just drag & drop them to nest them. I can't get that to work. I can re-order them but they won't drop on top of each other to nest. I looked for a folder type object but I couldn't find one.
Any help would be great. Thanks

Thanks. You could also create multiple sites, I suppose: one for movies, one for photos, etc. and then link to the sites and not just hidden pages. But those other sites are published in their own directory and don't show up in the nav bar. I have three different sites right now on .Mac, the family site and two podcast sites. The podcast sites really don't require that much flexibility, but I wish Apple would release an update SOON to allow nesting of pages.

Organizing pages in iWeb

I have created a custom photo gallery in iWeb and each thumbnail (30+) in the gallery will link to a separate page describing the item in the photo on the website. is there a way to group all these pages into one "folder" called gallery in my iWeb side bar?

You can create a new site for your photo pages.
You will then have the option to open them in a new window in the browser using this feature in the "link" inspector.
Choose to "hide" the navigation menu on this new site.

Organizing multiple websites created by iWeb

I could do what I'm about to suggest via any text editor and some HTML code, but I'd like to aks the cognoscenti here about the feasibility of doing all of this entirely via iWeb.
I have (will have more) multiple websites on the same theme. I would like to create a master web page which will access these other pages via objects attached to links that access them.
Each website would be under its own directory structure. The main page would have the familiar index.html >> home.html, utilizing my domain name's link to index.html. However, in the various directories, each index.html produced by iWeb would be removed as it appears redundant if the linkage to a domain name is not required. The links in the master web page would call home.html in each of the sub-directories. Only the master web page would link to the domain name via index.html.
Sound reasonable?

Hi Rusty Rat
My first site in iWeb is called
Alaskadream (It is the welcome page)
I have 4 more sites in iWeb called
-ita (italian version)
-de (german version)
-en (english version)
-fr (french version)
So a site for each language
Total 5 sites (all displaying in iWeb).
when you get to my website entering the url http://www.alyeska.altervista.org/ you get redirected to the first page. This page is an index page (master) like you want to build it as far as I understand. So from there you choose which language (thus which site) you want to visit. I skipped the index file of the other sites (link to 'One of my pages' and 'FirstPageOfTheSite') so it's getting directly into the site. All done within iWeb. No need for any html editor.
Regards,
Cédric

Duplicate user account OR migrate iPhoto/iWeb between users

I've seen this question asked several times before, but have not seen an answer!
So, with as many details as I can muster:
I have, on my computer, 4 user accounts: my admin account, my user account, my boyfriend's user account, and our business account... All separate, keeps things nice and tidy (sort of!).
I have a new and separate project that I'm starting to work on which involves lots of images, and new websites, and new and different stuff that's necessary for the project, but just clutter in any of the other accounts.
Because this project started out as something my man wanted to play around with, all of the beginnings of this are in his iPhoto and his iWeb, and they're well organized. I've not had luck so far moving the iPhoto and iWeb libraries to a new/blank user and maintaining the organization that I've spent time and attention making right.
He's not so great with technology, and gets very frustrated (and unproductive!) when anything on the computer doesn't work exactly like he expects it to. (When Lion came out and the scrolling went "the wrong direction" he was afraid to use the computer at all for a week, because "everything changed, I don't even know how to use it anymore" that's between us though, personal issure ). So I'd like to keep the user experience the same for him. I'd like to duplicate his settings, preferences, etc. into a new user for him, and take over his current account to isolate this project.
So, in summary:
I want to create a new account with the same user experience as a current account without having to find and reset all of his settings.
OR
I want an exact copy of the iPhoto and iWeb from this user account to another one, on the same machine.
I am currently running OSX 10.7.2, iPhoto '11 9.2.1 and iWeb 3.0.4
Thanks in advance for any help!

Kenzishly wrote:
I want to create a new account with the same user experience as a current account without having to find and reset all of his settings.
That's easy, if you have Time Machine or "bootable clone" backups. (If you don't, you should anyway. Post back if you need info on them.)
Use Migration Assistant to transfer just that user account from the backups; it will put up a screen saying it can't transfer it under the same name as the existing account, and allowing you to rename it.
Other than having a different name, the transferred account will be identical to the existing one. Then you can modifiy them separately as necessary.
EDIT: see Using Migration Assistant on Lion for detailed instructions. Be sure to un-check the boxes for eveything except that one user account.
Message was edited by: Pondini

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

Comments and a question about iWeb

Hi all
I have recently created and posted my university web site using iWeb on the univerity server (using CaptainFTP). If you are interested you can look at it: http://host.uniroma3.it/linguisti/lcs-ingles/
I am quite happy with the end result. However, I am a bit disappointed at how slow the pages download on the university computers (no macs, unfortunately, and all using windows with IE). So I've put a banner for Firefox on my first page as it appears to work much better with iWeb-generated pages on Windows machines (at least the ones at the university).
I've also inserted comments on my newsblog using iComment (very easy to use!).
However, there is one thing I would like to be able to do, but not sure how possible it is. My students need to sign up for exams at the end of each semester (unfortunately, the university system is a total disaster!). Is there any way I could use some type of form for this? I realize that this is not possible in iWeb itself, but I thought there might be some way to integrate this capability. It would be great if this information arrived to me or the web page in an organized manner (so that I could easily pop it into an excel worksheet)... keep in mind that we have four different exams so I would also have to separate these entries (according to the exam that needs to be taken). I think that I'm asking too much.... especially since I have no experience with HTML programming (but I would be willing to learn some if any of you think it's possible to do this). If the students could sign up for their exams and then this information could be organized it would save me hours of headache (and it would also give me a clear idea as to how many people have signed up for an exam).
If anyone has any suggestions please let me know.
As always thank you all for your help.
Michael Boyd
Rome
iBook G4 12 Mac OS X (10.4.5)

I just did a quick search and all the posts I see are referring using a different editing program and a different host.
http://discussions.apple.com/thread.jspa?messageID=1675548&#1675548
You've already got the different host thing down since you're not using .Mac, but there's many different ways to do forms. I just did a Google search and found this presentation..
http://www.rochester.edu/its/web/briefings/webforms/sld001.htm
which gives some info into how it's done... the steps of which differ depending on the server you're using, the technologies available, and your level of skill. Looking at this, I'm not surprised Apple didn't implement it because it'd just be one more feature that only works on .Mac (since that's the only server where Apple KNOWS how it's set up).

How to use iWeb as your WYSIWIG editor for HTML

Yes, it can be done - and as such, it is the best 'free' html editor for the mac, by far.
design and publish your web page with iWeb. In the end, if you are going to paste the html in an email or some such thing, simpler is better. but don't be afraid to include graphics and colors . . . everything that probably doesn't require javascript (because the email clients are definitely not going to render that).
then . . . .
- download the source of the page. (here after referred to as FileName.html)
- replace any of the local links with the full http:// prefix - especially for images. (this can be done quickly with a simple find and replace)
- download the css for the page (naming convention is FileName_files/FileName.css in the same directory as the FileName.html file )
- use the emogirphy tool at pelago design to merge the css style sheet with the html to create inline style tags for the html http://www.pelagodesign.com/sidecar/emogrifier/
that's it, now you have perfectly useable html that doesn't require style sheets, which you can use for sending emails, or archiving on your own computer. . . whatever you need.
hope this is helpful - it was for me.

phrakture wrote:
Dusty wrote:phrakture is the everything guru. X11, CLI, VIM, ssh, network, lovemaking, organized crime, kernel hacking, etc.
arooaroo wrote:Am I the only one wondering how you know this fact?
You weren't supposed to tell, schnookums!
AHAHAHAHAHA, that has TOTALLY made my day

State of iWeb replacement options...other ideas?

Like many others, I've been searching for an iWeb replacement. Here's my next findings:
Sandvox - way too dumbed down (can't even set page widith).
RapidWeaver - not WYSIWYG (editing is separate from layout), can't modify templates easily.
Muse - best candidate, but still in beta (and that subscription model....)
Freeway Pro/Express - WYSIWYG but not free layout (i.e. can't put an image where you want it - it flows with the text) - still requires knowledge of HTML, tables, etc.
Dreamweaver - heavy duty, not remotely free layout, requires HTML knowledge.
Flux - Dreamweaver done right, but still requires knowledge of HTML layout, and doesn't do free layout.
In other words, there's no decent iWeb replacement out there right now that I can find. Here's what 'decent' means in my mind:
1) Able to publish to any server
2) True WYSIWYG (edit and preview together)
3) Able to do basic site formatting (like page width) without hand-editing CSS (or breaking open app bundles)
4) Able to do drag/drop placement of images and text without futzing with tables, etc (i.e. free layout).
Maybe in sum, what I'm looking for is an iWeb that generates good code :-).
Have I missed any options?

I have played with a bunch of different iWeb replacement programs. I have a product brochure that I am transferring to a web page and I have tried it in just about all of the packages you mentioned (just not dreamweaver or Muse). In Sandvox and Rapidweaver, I gave up; I could not get the programs to display what I wanted. Kind of a shame because the interface seems very nice otherwise. I was pretty convinced that Flux was the best I was going to get. Flux is overall good and gives a lot of flexibility. It is not as difficult to learn to be productive as it might seem given its easy access to the HTML code being generated. As discussed above, putting stuff in div elements and walking them around the site is pretty easy to do. I have tried to get fancy with a few things, but each time, I got twisted to the point that my project became un-workable. I can accept that this is because I am not a code guy, but then again, I am also looking for something that helps me avoid code as much as possible. I was disappointed that after I got my site organized in Flux the way I wanted it, I could not get it to display correctly in either Firefox or Safari. Not sure what I did wrong, but was not about to start over. I am sure I can get there with Flux, but I think they still have some work to do before the program is really a viable option for non-developer / weekend designer types like me.
I was very surprised how much I like Freeway. I think this is the way to go. I have been playing with the pro version and I can drag photos directly in and place them anywhere without any trouble. I can mask (or crop) easily with drag and drop simplicity too. It is not too bad getting into the tables when I need to to modify page sizes or HTML text details. Right now, I am pretty enamored by Freeway as a replacement. I think it is very well done and I was able to generate my brochure very quickly without ever using the program before. I should give credit to Flux for some of that. After the time I put in with it, I picked up a little bit about styles and site organization that helped me understand better what I was doing in Freeway.
As a benchmark, it took me about 3 hrs to create my page in Flux (but again, it did not publish well in the two browsers) and about 45 min in Freeway from a cold start (and the page published fine). Sandvox and Rapidweaver Did Not Finish because I could not get the layout I wanted. I will try Muse as well as the standard version of Freeway to see how those compare.
For reference, I created my page in iWeb in 20 min. I have no idea what the code looked like, but it published as expected and seemed fine for my purposes. I too will miss that program.

IWeb and galleries - Why cant I make a gallery-page??

Hello! I'm new to Mac (Just bought an MacBook) as well as iWeb. I have pictures from 6 different holidays which I would like to post on the iWeb-site I'm creating at the moment. Is the only solution to make 6 gallery pages right along side the main pages, such as "Welcome", "CV", "blog" and so on? I'm looking for something like a "Gallery page" where you click on a holiday (Icon or picture), which takes you to a page where you can check the photos or watch a slideshow. I've tried a bunch of times, but it won't work, which is why I'm asking out here!
I hope somebody can help me
Thanks either way
Anders
MacBook Mac OS X (10.4.8)
MacBook Mac OS X (10.4.8)

Check out this idea from the .Mac Blog...I think it will suit your purposes perfectly and AUTOMATICALLY via iPhoto and iWeb!
http://www.mac.com/web/en/Tips/013C4180-4787-4847-BAAB-319222AFC652.html
Please note, you must have your photos organized into your desired albums in iPhoto. Otherwise, this will create everthing for you! And it won't clutter up your navigation menu!

Apple PLEASE FIX THIS in iWeb!!!

We need to be able to create several different domain files, that are in no way linked together, yet can be open in iWeb at the same time!!! Please hook us up with a quick update, very important for some of us.
I have 2 websites, one is hosted elsewhere, and one is hosted on .mac. I have both of them in the single iWeb domain file at the moment, but would prefer to have it organized like this;
Domain A
Domain B
so that when I open each file, just one site comes up, which ever one is linked to that domain file. The main reason why I would love this is because I do not want to have to keep switching my sites around, as to which should appear first, when I export to my FTP or upload to .mac, secondly I don't want to upload the site that is hosted elsewhere to .mac, we should have this option, and it makes it very unpleasant and not user-friendly, which is what we are used to with the iLife apps.
Please respond to this by simply updating iWeb so that we have this option, sooner rather than later!!!
Thanks!

Here is a non-Apple solution that should work (I haven't tested it specifically with iLife, but that's because I don't use iLife for anything but goofing around. This does work with Dreamweaver, however.)
Go to the macfuse page and download MacFUSE-Core-(version num).dmg and sshfs-(version num).dmg. I replaced the version numbers with version num in case they update... get the ones on this page:
http://code.google.com/p/macfuse/
Macfuse might sound complicated, because most of the pages are written in developer jargon, but it's basically a system that allows you to use network resources as if they were a hard drive on your system. The sshfs file is the plugin that allows Macfuse to use web servers as a drive.
The Macfuse core package comes with a standard Apple installer, so it should be painless. The sshfs.dmg contains sshfs.app, which is a normal app that basically acts as the connector to your website. That gets dragged to your applications folder, or wherever.
Note: Macfuse is not launched by itself. It's basically a framework for writing applications that mount network resources (or hitherto unsupported-on-the-mac disk formats) as normal disks.
Make sure you install the Macfuse core first, because sshfs won't work without it. After both are installed, launch sshfs.
You'll be prompted for your server address, username and (optionally) the sub-directory you want to connect to. You are prompted for your password after the connection is made, and if everything you entered its correct, your website should mount as a drive.
From there, I think you know what to do - publish your iLife website that's not on .Mac to a folder, in thiscase the folder would be /Volumes/yourwebsite, where yourwebsite is whatever sshfs calls your remote web directory.
(warning: if you are completely non-technical, this may be intimidating, but it wasn't hard to set up at all if you follow the instructions. warning: this is non apple software, and if it doesn't work, I probably won't be able to tell you why, but there is a wiki & faq on the download site that details how to recover from most problems it seems)

IWeb link to folder and enclosed files

I have several student projects that they published to a folder using iWeb, and saved to folders using other HTML editors(BBEdit, NVu). These are now on my local drive. What I want to do is to make a link from my iWeb page to their work. I need to know what directory to upload these folders to, and then what the link would be. I've tried several .Mac folders, but nothing seems to work.
Any help would be appreciated.
http://web.mac.com/penobscotriver/iWeb/Site/Welcome.html
MacBook Pro Mac OS X (10.4.9)

More explanations:
If the folder were made by "publishing" from iWeb the "root" (upper level) also includes an index.html file.
That index.html is merely a page refresh to the "real" .html file and that page loads it. If you open it with a plain text editor you'll see the simple code.
You appear to be a teacher (instructor) so I'm sure you remember the "index card" trick for organizing.
In the "old days" we would pin index cards onto a board and then connect them with different color strings so we had a visual of the structure. When you moved a card you also needed to detach the string and then re-attach it.
Properly organized the "folders" would reside in your iDisk Sites folder and the "links" (the string) would attach to a page (or pages) stored in the iDisk/Web/Sites/iWeb/foldername
You can then use some simple URL's (posted above) to aid in navigation.
Did you know that you can "drag" a URL from a browser window address bar into iWeb?
Takes work and patience. Trial and error. And these Discussions for help.

Newbie question - iweb into "iphoto" site?

I am just opening iweb for the first time on my new macbook. I really like some of the things that appear to be possible with it.
However, for a number of years now I have been keeping a collection of photos tracking the birth and growth of my son for the benefit of far away friends and relatives. I have built it though iPhoto and my .mac homepage space.
I have a beautiful new daughter for whom I want to do the same, but iPhoto no longer allows that. My question then is - can I post "iweb pages" into my exisiting .mac site without destroying all the other photos that I have collected and posted over the years.
Power Book 12 Mac OS X (10.4.1)
MacBook Mac OS X (10.4.1)

Apnewbie is right.... your Homepages created with previous versions of iPhoto are indeed safe. They are not in any danger of being overwritten by iWeb, as far as we've all been led to believe so far. But iWeb is definitely the way of the future in terms of how Apple wants us to think of it...as you mention, the easy Homepage function is no longer available in iPhoto 6. Instead of Homepages, now Apple wants you to use iWeb to create your photo pages. You can do so using the iWeb icon in the bottom of the iPhoto window and selecting "Photo Page". This is the closest equivalent of the old Homepages function.
But iWeb is infinitely more functional and customizable than the old Homepages system. There is actually a "hidden" function for creating photo gallery pages easily, especially since it sounds like you already have your photos organized into albums in iPhoto. The process is detailed here in this .Mac blog entry...
http://www.mac.com/web/en/Tips/013C4180-4787-4847-BAAB-319222AFC652.html
iWeb has a little bit of a learning curve, but I think once you get the hang of using it, you will not miss the old Homepages function. Of course, if you run into any showstoppers, please don't hesitate to post your questions here in this forum....It's filled with lots of helpful people eager to lend you a hand.

Photos not appearing in Screensaver or iWeb

I have several thousand photos in my iPhoto 9 library, all organized in folders. When I go into System Preferences and try to designate my photos as the screensaver, none of the iPhoto folders appears on the list of options. Furthermore, when I open iWeb (ver. 3), none of my iPhoto pictures load into the viewing pane (I just get the spinning cursor icon). Not sure whether these are two completely separate problems or are related. Anybody have any ideas? I'm on a Mac mini running OS-X 10.6.8.

Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Look there for a Files called 'AlbumData.xml' and 'AlbumData2.xml'
Drag them to the Desktop. *Make no other changes*.
Re-start yor Mac. And try again.
Regards
TD

Exort to iWeb or drag & drop?

Hi,
when doing a photo page in iWeb, what is the difference between export to iWeb function in iPhoto and drag & drop between iPhoto album (or Finder) and iWeb? It turned out that when I draged and dropped from an iPhoto folder I didn't get all photos into iWeb, some was missing (the ones I hadn't edited i iPhoto, I figured after a while...). I guess export function is to be preferred then, but what is the difference?
TIA
Mans
iMac G5, iMac 450 DV, iBook 300 Mac OS X (10.4.8)

There shouldn't be any real difference. Some people find it difficult to drag and drop photos into the Photo Template. There's also a 99 photo limit for the photo grouping on a photo template, so if you try to drag and drop more than that iWeb will randomly pick 99 for you and leave the others out (without telling you which ones).
Also, if you already have your photos organized into albums in iPhoto and you want an easy way to make gallery index pages and photo albums automatically, try the method in this link...
http://www.mac.com/web/en/Tips/013C4180-4787-4847-BAAB-319222AFC652.html

Organizing in Iweb

Similar Messages

Maybe you are looking for