What I don't like about Google Sites

• No tags (or facets) on pages
• I can't create a page in a manner comperable to using CamelCase in a traditional wiki.
• For some reason, this makes pages much less representative of concepts.

Google Apps for Libraries

• Notes:
  
• Ellsworth Public Library 5/14/08
• Mark Arnold
• Deer Isle/Stonington School
• Google Apps
• Sites - when to attach a .doc file and when to have the doc in Docs
• What about Google's right to use anything on your site.
• How to do specific things with Google Apps?
• How to transition from disks to Apps?
• Don't call it an email account, since that can cause problems

Why Google Sites & Blogger over proprietary system?

• Goals?
• Who updates?
  
• Email posts to blogger.com
• Categorize posts via tags
• Relatively infinite design, programming and hosting resources
• Easier to maintain (?)
• I don't like the way the proprietary system paints the page with every link.
• The proprietary sites I've seen are very rough.
• How many people in the proprietary organization?
• If the proprietary organization doesn't work out, we can't can't someone else to work on the site for us because it's a proprietary system. We'd have to rebuild the site.
• Here are a couple sites:
• Saint Andrew and Saint John
• Saint Andrew's Newcastle
• Example
• Dr. Mel Levine in Bangor - April 30, 2008
  
• The pages are slow to load.
• Caveats:
• I am not a designer
• I am not a copy writer
• I understand function
  
• Spencer suggested that we look at the Acadia Senior College web site here.
• Top Ten Mistakes in Web Design
• Service times should be first and formost - that's mostly what people want to see
• No fluff language.
• Money