iLife 06 Review Part 3: iWeb

Discussion in 'MacBytes.com News Discussion' started by MacBytes, Jan 19, 2006.

  1. macrumors bot

    Joined:
    Jul 5, 2003
    #1
  2. macrumors 65816

    doucy2

    Joined:
    Jul 7, 2005
    #2
    i was playing around with iweb last night
    very nice, i really like the intergration with .mac
    super user friendly, apple did well with iweb
     
  3. macrumors 6502a

    AtHomeBoy_2000

    Joined:
    Feb 3, 2005
    #3
    He hit that one right on the head.
     
  4. macrumors member

    jaesk8er

    Joined:
    Jan 30, 2003
    Location:
    Bay Area
    #4
  5. macrumors Core

    Joined:
    Jan 6, 2004
    #5
    i like iWeb right now. but there are some annoying things about it.
    such as the splash screen that comes up when you open it asking about .mac. i said no once, isn't that enough?
    and there is no blank template.

    i might have to give Rapidweaver a try.

    edit. here is what i have done with iWeb so far, i have a bit of work to do still though: www.tmklein.com
     
  6. macrumors member

    manosira

    Joined:
    Jun 22, 2004
    Location:
    SOMA - S.F. - Cali
    #6
    iWeb is alright, I'm still trying to figure out how much customizing one is able to do from the templates, or if it's pretty much set as it is.
     
  7. macrumors 601

    Yvan256

    Joined:
    Jul 5, 2004
    Location:
    Canada
    #7
  8. macrumors 603

    Stella

    Joined:
    Apr 21, 2003
    Location:
    Canada
    #8
    iWeb is good for only the most basic of tasks. Its of course good for people who do not know / not willing to learn HTML - or just knocking up a very quick but nice looking webpage.

    Anything else and iWeb is a toy.

    Apple could have changed this by allowing end users to create their own templates.

    I installed iLife, messed with iWeb for 10 minutes and promptly removed it from my hard disc.

    As Yvan256, above, pointed out, well done for Apple for creating XHTML and CSS compliant web pages. The web is for all browsers / OS and not dependant on one platform ( or browser ). All web developers ( AND Apple!!) should follow W3C standards.

    edit: the page above linked ( http://www.tmklein.com/Blog/Blog.html - iWeb creation ) passes XHTML w3c validation, unfortunately the CSS does not ( only because font names are quoted - which is incorrect ).
     

Share This Page