Keynote theme as iweb template??

I think I read somewhere that keynote pages could be used as an iweb page.
Anyone heard of this or have examples?

You can output a Keynote file AS html (which you'd publish manually and point an iWeb link to it), but as far as using it "directly" as an iWeb page, I don't think so.
BUT, since the graphics can be copy/pasted from one to the other, I could see using Keynote to layout a website and copying images shapes and everything into an appropriate width (to match the presentation) page.

Similar Messages

Importing Templates/Themes into iWeb

Hey Folks,
How do I go about importing templates/themes into iWeb? I have a few I downloaded but I'm at a loss as to how to include them in iWeb so that I can use them. Thanks for the info!

Just any theme download from a site is not enough. The 3rd party themes must be designed specifically for iWeb and, as such, should have an installer included.
Otherwise, start with either the white, black, or formal themes and use graphic files from those themes to create a custom design.
OT

IWeb templates/themes

Can you change the theme of your website/webpages without having to type and drag and drop everything again? I don't want to lose all of my blogs, but would like to change the theme or the look of the page.

Sorry — my oversight: Theme switching was introduced in iWeb '08. See here.
Jonelle wrote:
I don't mind doing it manually (...) how do I save all the blogs and then paste them in the reconfigured webpage?
I doubt anyone has bothered to write up a methodology to manually switch themes in iWeb '06. So you'll probably have to experiment with copy & paste yourself.
I just don't want to lose what I have up there now...
See this Apple doc on _How to back up MobileMe data_. It says:
iWeb: Any websites you have published with iWeb should still be available within iWeb. iWeb stores everything in a Domain file, normally located in the ~/Library/Application Support/iWeb folder (although it can be moved). (...) You can manually back up the Domain file, or use Backup to back it up.
And although the following doc talks about iWeb '08, I believe it also applies to iWeb '06: _iWeb ’08: Backing up your Domain file_.
...So basically, if something goes wrong with your manual theme switching, you would double-click on the backup copy of your old Domain file and it will open in iWeb.

More iWeb Templates

Hello,
I am curious as to if anyone knows where I could find some more good iWeb templates, whether there free or not. Just looking for a more professional but simple template to use for a site that I am working on. If anyon ehas any ideas, please let me know. I would prefer not to spend too much on a theme or templete I dont have to.
Thanks for your help.

I got tired of looking for free templates as what I found were pretty weak. I went ahead and bought the iWeb Suite from http://ipresentee.com/iPresentee/iPresentee-_iWebSuite.html
They have smaller sets that sell for $25 and individual templates go for $10. The Suite is everything they have for $60 and it also included a bunch of iWeb animations, and some files for Keynote (which I don't use, but I'll take alook).

Deciphering Aperture Web Themes: the html templates v3

version 3 of my Aperture Web Theme html template reference. enjoy
the html templates.
rkid attributes:
Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
  <ul id="nav" rkid="navbar">
These are the rkid values that I've identified so far:
  "navbar"
    a <ul> element containing all of the navigation elements.
  "active" and "inactive"
    rkid attributes to enable the coder to place different formatting on
    current and non-current page numbers in the navbar.
    eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
      <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
  "content"
    a <div> containing all of the album images and their metadata.
  "pictureblock"
    a mandatory <table> in which the images are placed, one image per <td>.
    the <table> must even be used on the Detail page where only one image is
    displayed.
    the metadata will be within the "pictureblock" table if more than one
    image is displayed so that the metadata can be tied to the image. if
    only one image is displayed; i.e., the Detail page; the metadata may be
    in a <td> outside of the table that the image is in but still within the
    "content" div, usually in the following format:
      <div rkid="content">
        <table>
          <td>metadata
          <td><table rkid="pictureblock">
  "image"
    the rkid for the <img> elements containing the album images, frequently
    placed in <dt> elements within the table's cells.
  "metadata" (added in Decipher v3)
    all metadata for the respective image is specified within this element.
    everything within the element is repeated for every metadata value.
    the Aperture themes use the <ul> element but <div> also works:
      <div rkid="metadata"><p>metaname: metavalue</p></div>
  "titleblock"
    a <div> containing the title text; usually <h3>; for Journals. the <h3>
    element within this element must be given the attribute rkid="text" or
    Aperture will ignore it.
  "textblock"
    a <div> containing the description text for Journals. as with the
    titleblock, the <p> element/s within this div must be given the
    attribute rkid="text".
  "text"
    the rkid given to the text data within the titleblock and textblock
    elements.
Place holders:
  PageTitle
    used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
  IndexPageURL
    the gallery page/s URLs; may be more than one.
  ThumbImageURL
    the href links for the images, whether thumbnails or detail full size.
  DetailPageURL
  used within navbar:
    PageCount
    PageNumber
    PreviousPageNumber
    PreviousPageURL
    NextPageNumber
    NextPageURL
    PageCount the total number of pages
    PageNumber includes all of the page numbers listed in the navbar, one
      occurrence for each page.
    _Previous and _Next are more specific and are currently used to draw the
      prev/next arrows in the navbar.
  ImageName
  ImageNameSpace
  PlateNameSpace
  PlateNumberSpaceSlash
    *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
      chosen.
    used to represent an index of the image in the album. the first image
      shown gets the index 1, the second 2 and so on.
    for the Image placeholders, the word 'Image' is used.
    for the Plate placeholders, the word 'Plate' is used.
    space indicates an extra space after the index, probably for html
      formatting purposes because it's only used within <dt> elements.
    slash indicates an extra / character after the index.
    examples:
      ImageName > 'Image 1'.
      ImageNameSpace > 'Image 1 '.
      PlateNameSpace > 'Plate 1 '.
      PlateNumberSpaceSlash > '1 / '.
  metaname
  metavalue
    the placeholders for all of the metadata names/values in the selected
    metadata set.
  PageWidth
    not sure if Aperture calculates it based on the width and number of
    images being displayed in both gallery and detail pages.
    don't know why it's only used in the Special Occasion theme.
  CellWidth
    the width of the table cells containing the album images. not
    necessarily the width of the images. may include margins as specified in
    the albuminfo.plist files.
  ImageWidth
    the width of the image.
  TableWidth
    the width of the pictureblock table. it can probably be applied to other
    elements too but it's length is almost certainly calculated from the
    pictureblock table.
Operative attributes:
  removeonfirstpage="yes"
    used in the navbar to remove the Prev link from the first page.
    because it's applied to the <a> element, the <a> element is removed
      while leaving an empty <li> in place.
  removeonlastpage="yes"
    used in the navbar to remove the Next link from the last page.
    because it's applied to the <a> element, the <a> element is removed
      while leaving an empty <li> in place.
  removeonsinglepage="yes"
    used in the navbar to remove elements when there's only one page.
    used in a <div> in the Art Collection to remove the whole navbar on
    single pages.
  contenteditable="yes"
    used in text elements to indicate that the user can customise the text.
    not necessary in titleblock and textblock rkid="text" elements.
    in elements outside of the titleblock and textblock elements, content
    will not be truly editable unless a textid is assigned to the text
    elements. unfortunately, all text elements with textids are always
    'common' and can not be specific to any one image.
  common="yes"
    the element is seen on all pages.
Other attributes:
  metaseparator="|"
    used in metadata formatting, within the metadata lists.
    you can add additional characters. for example, the metaseparator
    in the Stock Black theme is " | "; ie, a | bar with a space on both
    sides. (Decipher v3)
    if the metaseparator is specified and the html template places the
    metadata into <li> elements as it does in most of the current themes,
    then it produces non-standard html code with the metaseparator between
    concurrent <li> elements.
  metalayout="paragraph"
    used in metadata formatting, within the metadata lists.
    if not specified, the metadata will not be exported. (Decipher v3)
  singlenesting="yes"
    used in metadata formatting. not sure what it does yet.
  textid="x"
    used to id text elements outside of the titleblock and textblock
    elements.
    possibly no limit to the number and id names used.
    examples used:
      textid="copyright"
      textid="header1"
  picturename="x"
  pictureimage="true"
    picturename gives the image an id.
    pictureimage="true" tells Aperture that the image is a static image
    which can be designated by the user during setup of the album. they show
    up in Aperture as grey blank rectangles with cross-eyes in the middle.
    they do not need to be inside the "content" element
    with picturename and pictureimage, we can place as many static images on
    the page as we wish.
Assertions:
  Aperture uses the rkid values to identify the areas of the html to be
  repeated for the respective objects.
  standard id and class attributes are only used by the css for formatting and
  not by Aperture to write the html data.
Notes:
  Aperture is hardcoded to expect and require that the album images are always
  within a <table rkid="pictureblock"> element. it is not possible to place
  album images outside of the table. all album images must be placed within
  <td> cells within the table. the <td> code is repeated for each image.
  image metadata is also normally within the rkid="content" element although
  it can be outside of the rkid="pictureblock" element.
  by default, the textblock rkid="text" element is added when the T+ button is
  pressed within Aperture. the textblock element is switched with the
  titleblock element when the Title/Text toggle button is clicked.
  width and height attributes of <img> elements are rewritten by Aperture
  based on the inserted images. placeholders aren't necessary within <img>
  elements.
  comments are stripped from the html before export some but some
  Aperture-proprietary attributes are forgotten and left behind.
  some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
  doctype.
  all markup is converted and exported in UPPER-CASE. personally, I prefer
  lower-case.
  high-ascii characters entered by the user are not converted to their html
  entities when available. eg, the © character.
  multiple <p> elements can be inserted into the titleblock and textblock
  <div> elements but each of them must have the rkid="text" attribute. any
  element without this attribute will be ommitted by Aperture.
  the reason there are Smart Galleries but no Smart Journals is because you
  need to write text between each row of images.
  titleblock and textblock elements will not be applied to Galleries or Detail
  templates; only to Journals.
  if there are more than one titleblock or more than one textblock, only the
  first will be used by Aperture.
  upon export, Aperture will remove everything from within the rkid="content"
  element which is not the pictureblock, titleblock or textblock elements.
  (Decipher v3)
  some of the Aperture templates have xhtml doctypes but are exported from
  Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
  that UPPER-CASE element names is not permitted with xhtml which is
  case-sensitive. (Decipher v3)
Questions:
  are there variable scopes with each rkid? eg, within the "content" rkid, can
  every variable/placeholder be accessed?
  why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
  the images and related metadata in the table? easier css formatting?
JavaScript: (Decipher v3)
  you can include JavaScript in the html code but cannot wrap it in html
  comments because Aperture will remove everything within comments.
  Aperture variables such as PageNumber will not be replaced within
  attributes such as <body onload="dialog(PageNumber);">.
  it is very difficult to use document.write anywhere within the html <body>.
  Aperture seems to be using JavaScript to export the html and its code is not
  able to cope with more than one instance of document.write in the html
  templates. after hours of trial and error, I found that the most stable way
  to use JavaScript within the html <body> was to only use one <script>
  element and place everything within it. using document.write within a second
  <script> element would almost certainly lead to unpredictable exported html,
  and instability and crashes in Aperture.
iMac Duo Core 2GHz 2GB Mac OS X (10.4.6)

It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
1) one large image per thumbnail page (like a photo essay or photo blog style)
2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
This is great because I hate javascript but sometimes like the immediate visual effects it allows.
This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today.

Can iWeb templates be modified?

I last used iWeb to set up a travelogue in 2006. I have 3.0.4 ('09, I think).
I may be remembering why I didn't use a template before--because I wanted something I couldn't get with the templates.
Am I correct that I can't change a background or text color, or choose to center text which is flush left on an iWeb template?
Karen

Jeff, you're a prince. I've printed out your last posts & dragged & dropped the 2 samples to my desktop, from which I can then use them I was able to do the web browser background instructions. It worked! Cool.
I'm sure this will turn out to be embarrassingly self-evident, but how did you 'copy the page background image and paste it into preview'? It has no 'handles' allowing it to be selected. Nor could I locate 'Preview'.
Now trying the paper maneuver you explained, I'm a bit stuck. What do I select for 'Page Background? I now have removed the Formal Theme text boxes, have changed footer pixels to '0', and have a horizontal rectangle of the ivory paper there. How do I make it disappear so I can then replace it with the size-able box as you describe?
By the way, I noticed right off in your video was how you changed the width of the page immediately. How did you choose 900--and I forget the vertical pixels you chose but will check again. I hate how small the page content size is. Is there a 'standard' size these days for website width & height?
Again, thanks.
Karen

Free iWeb Templates and other goodies?

Hey, it's me again!
I was looking for FREE iWeb templates but I haven't been able to any find free ones or great ones.
Do you know where to get them?
I was also looking for other free goodies that are on iweb, such as little doodles and pieces of paper. You know what I mean?
Do you know where to get them?
You're always appreciated :)

Hello MissMacintosh,
MissMacintosh wrote:
Hey, it's me again!
Always nice to hear from you.
As you, I did an extensive search (3 months ago) on Google and Ask, only to find out that there is a poor choice of great / free templates for iWeb '08.
There are 1 or 2 "user understandable" manuals on how to make your own templates, but I found it less time consuming to choose the "blank" template from a theme, adapt it myself with the tools provided in iWeb and then copy this "custom adapted" template.
I know this is not the answer you are looking for but it is the best I can provide.
Hopefully, someone else has found the gold somewhere...
Kind regards,
Leo

I have added photos to a portfolio website I'm building and a lot of them look VERY grainy when you click on them. They are nice clean large files and can print bat high res way over 16" x 20" so whats happened to them in iWeb?

I have added photos to a portfolio website I'm building and a lot of them look VERY grainy when you click on them. They are nice clean large files and can print bat high res way over 16" x 20" so whats happened to them in iWeb?

When you are dealing with websites, image file size is a trade off between quality and download speed. There's not a lot of point to having high quality images if they take too long to download in the browser.
Nowadays we also have to consider the device that the end user is viewing the images on. An image that is optimized for viewing on a large screen is total overkill and unsuitable for those using mobile devices.
Really we should be supplying different versions of media files for different devices using @media rules in the stylesheet but this is rather outside of the scope of iWeb. If you use the built in image optimizer and the iWeb Photo template with slideshow, the application will optimize the images according to the way in which you set this function in preferences and the slideshow size will be automatically reduced for those viewing it on smaller screens.
If you want to give your viewers the opportunity to view large, high quality images, you can supply them as a download.

Using iWeb Templates

I have found not only iWeb templates difficult to deal with, but also iPhotos.
Whenever I try to delete a certain saved area - a most important one - I cannot. If I select to utilize a photo template I cannot delete the photo area and when
I login to the website the slideshow puts up the template photos. This is very disturbing.
Also in iPhoto I cannot create a new folder or copy to an existing folder except the Library. If this is the case then why cannot I move photos to a newly created directory or folder after copying them to the library,
I am extremely new to MAC but totally competent with UNIX, LINUX, DOS, and all versions of WINDOWS, ( SADLY )!!
Any help will be greatly appreciated.
Thanks,
Ron

Ron:
Can you give us some information about what you're using: iPhoto an iWeb version, Quicktime version, the theme and page layout in iWeb, etc.
As far as dragging a photo into an album, where are you dragging from? If you're creating "folders" in the Source pane then yes, you can't drag a photo into them. Then will only take albums, slideshows, books, calendars, cards and other albums.
So instead of creating folders in the Source pane, create an album and put the photos into it. You can use folders to further organize the albums. But albums are the primary photo container (except for rolls of course).
What saved area are you referring to? If you've selected a photo page then yes, you can't delete the section that is used to house the photos for the slideshow. If you don't want that, create a new page with a different layout, Welcome, About me, or blank. Whichever works best for you. The blank lets you completely customize the page, background, etc.
Do you Twango?

IWeb template file locations, ect.

Where are the iWeb templates and other iWeb trinkets located on the HD? I checked the iWeb file in my library but it was empty. Some help would be appriciated, I think I might have accidently deleted them, and I don't want to go through with re-intalling OS X tiger for the third time. Thanks guys!

Where are the iWeb templates and other iWeb trinkets
located on the HD? I checked the iWeb file in my
library but it was empty. Some help would be
appriciated, I think I might have accidently deleted
them, and I don't want to go through with
re-intalling OS X tiger for the third time. Thanks
guys!
I'm not sure what has happened to your iWeb installation, but it sounds like a reinstall of iWeb might be in order. I don't think you would have accidentally deleted the templates on your own. Though, I have actually heard of people losing their templates after updates, especially from iWeb 1.1 to 1.1.1.
The straightforward, no-nonsense recommendation from me would be to do a reinstall of the iWeb application itself. You DO NOT need to reinstall the whole OS X system. If you have the iLife'06 disc, then use that. If iWeb came preinstalled on your computer, then use your OS X install/recovery disk. But don't select to reinstall the whole system...just select "Install Bundled Software Only" and then customize for iWeb only. This will reinstall iWeb 1.0 in all likelihood.
Then download the iWeb 1.1.1 update dmg directly from Apple and apply it immediately after installation of iWeb...
http://www.apple.com/support/downloads/iweb111.html
Hopefully after this process, your iWeb templates will reappear.

Iweb template options

I would like more choices for templates. Specifically something related to poker, cards, etc. Is there somewhere I could get such a template that is compatible with iweb 09? Thanks.

Welcome to the Apple Discussions. Do a Google search for iWeb themes and you'll get several sites that offer themes for iWeb. I created an iWeb photo page with a poker theme by starting out with the black theme and adding a large poker table graphic for the background and set the page contents background to transparent. Worked like a charm.
OT

Rotating Photo on Photo iWeb Template Page

I have selected a photo that I'd like to ROTATE on an iWeb Photo Template page.
Go to the "ruler" in the Inspector.
The Rotate wheel is not operational, nor is the ability to Add a New Value, nor is the "handle" on the photo as the Help menu also suggests will happen.
Suggestions?

Unfortunately, there isn't a way to rotate photos on the Photo Template page. Strange, isn't it? Hopefully this is something else that will be changed in iWeb 2.0. Haha.
Anyhow, you have to have your photos oriented the right direction before bringing them into iWeb. And sometimes when the photo has been rotated inside iPhoto, the orientation property will not "stick" and the photo will be turned the wrong way when brought into iWeb. Try this....drag the photo that you are using from iPhoto to the desktop. Then open it with Preview and then "Save" it or do a "Save As." Then drag it into iWeb.
I don't think you'll have to do this with every photo you want turned...just the pesky ones that don't keep their orientation. It's a bug of sorts with iPhoto and the Media Browser....and it would all be fixed if Apple would just let us rotate the photos in iWeb!
Best of luck!

Import non-iWeb template

My wife is trying to build a website using iWeb for her business. She's not crazy about any of the templates that came with iWeb, or with any of the iWeb-specific templates that she's been able to find.
She has found some templates that she likes that are XHTML compliant (e.g., http://www.oswd.org/design/preview/id/2448). Is there a way to open them in iWeb, or to somehow convert them into an iWeb-compatible file? Thanks.

Is there a way to open them in iWeb
No.
or to somehow convert them into an iWeb-compatible file?
Drag-n-drop and/or copy/paste the objects is the only way.

Installing Custom iweb templates?

I have downloaded some iWeb templates, but I don't know where to put them so that they appear in iWeb. Any help would be greatly appreciated, thank.

RB if you got the templates from my site, then the instructions are here:
http://web.mac.com/sboben/iWeb/11Mystics/Documentationfiles/Install_NewTemplates-1.pdf
If you did not get them from my site, be sure what you have is actually a template and not just a domain.sites file.

Installing Iweb templates

Hi,
I have Iweb on an Apple Ibook G4 1.33Ghz 512MB RAM laptop. It came with ILife installed and I'm guessing it's version 6. Can anyone please guide me as to how to install the Iweb templates please?
Thanks Much,
Napster16

You guessed wrong. The latest version is 3.0.4
You can see it in the iWeb menu > About iWeb. Or select iWeb and do Command-I (Info).
The iWeb themes are stored inside iWeb. To go there, copy the line below :
/Applications/iWeb.app/Contents/Resources/Themes/
In the Finder, do Command-Shift-G and paste the line. Hit Return.
Right-click any theme and choose Show Package content. Open the Shared folder.
You can buy themes, or get them for free :
http://www.iwebthemespark.com/Gifts.html
Or search for it : http://www.google.com/search?q=free+iWeb+themes
And here's a dated explanation how to make them yourself :
http://11mystics.com/2007/12/13/customize-iweb-20-themes-and-edit-xml/

Keynote theme as iweb template??

Similar Messages

Maybe you are looking for