CLF Definition Subgroup October 24, 2007 meeting

Meeting

Date: Oct 24, 2007, Time: 10:00-11:30, Location: MC 1058

Attendees: Isaac Morland, Andrew Smith, Guillermo Fuentes, WebOps team (Glenn Anderson, Jason Greatrex, Kelley Teahen, Megan McDermott, Kevin Paxman, Heather Wey, Alan Kirker, Pat Lafranier) Regrets: Matt Regehr, Paul Snyder

Opening discussion

  • Welcome Megan McDermott and Guillermo Fuentes to the group!
  • Approval of minutes of Oct.11th meeting.

Discussion

  • We continued discussion and reviewed previous comments of Kevin Paxman's document "What is the Common Look and Feel (CLF)?", which wasn't completed at the last meeting. Although, some discussion ensued that is not part of our mandate, we feel it is necessary to document these items in the minutes. Please see the section labeled Communication in this document.
  • Use transitional XHTML than strict XHTML.
    • Parallel investigation - contact departmental webmasters to inquire why web sites code is not compliant?
    • Future recommendation: HTML, XHTML transitional, strict XHTML, etc
  • Screen width issue
    • Discussion over fixed width versus variable/liquid design recommendations.
    • Suggestions:
      • Web page must be viewable and function/operate under a set page size.
      • Top level pages should be fixed width (an example Adobe) and allow lower level pages to have the option to be a liquid design.
      • University of Waterloo home page screen resolution stats show the 800 x 600 screen size is approximately 2%.
      • A limitation noted; certain text sizes may appear distorted in viewing fixed web pages.
      • Future recommendation: future design fixed, liquid or a combination.
  • Provide toolkit or provide defaults tables with CSS
    • Future recommendation: default mobile specific css version

Mandatory Features of the CLF

  1. Title:
    • Graphics provides a script for campus use; Graphics will also produce a title on request.
    • Clarify title font and size.
  2. Banner:
    • Suggest seasonal? If seasonal, required to change seasonally.
    • Is a banner mandatory on first level web pages?
    • Static banner preferred over flash banner, but is a flash banner acceptable?
    • Can a banner be composed with multiple images (3 or 4) rather than 1 single image?
    • Determine correct dimensions.
    • Toolkit option? Rotational quote over banner (an example Faculty of Arts homepage).
  3. RightNav Area:
    • Right hand “navigation area” suggested name change to right sidebar, to avoid confusion and promote its versatility.
  4. Footer:
    1. Department logo - position in the footer.
      • Can departmental logo be larger than University of Waterloo's logo?
      • Unit/departmental logo allowed, but should be left aligned.
      • Where should unit/departmental logo link back to? Home page, departmental home page, faculty home page?
      • Future recommendation: positioning and flexibility to use and change departmental campaign logos.
  5. Copyright:
    • Megan and Kevin will consult Secretariat regarding copywrite ownership.
  6. Campaign logo:
    • Kelley made an inquiry but has not yet heard of a response.
  7. Contact us and feedback links:
    • Remove mandatory wording to optional.
    • Should contact us link be directed to a web page listing its organizational group.
    • What about a feedback email link?
    • Examples were shared amongst the group.
  8. Exceptions are allowed:
    • Areas encouraged but not mandatory to follow CLF guidelines:
      • Small research groups.
      • Individual academic websites.
      • Corporate applications whereby their interface is unable to adapt.
      • Church Colleges.
    • Glenn and Isaac to determine what defines a top level website and when does it apply?
  9. Custom 404 web page - determine a campus standard.
    • Extend investigation to other other common error messages displayed, such as 500 Internet Server Error, 400 Bad Request and 403 Forbidden message, etc.
    • Set on per server or site basis?
    • Megan and Kevin to investigate options, please send any prior research to them.

Communication and navigation

  • Although not our mandate, we felt it was necessary to document the following discussion in the minutes.
  1. Possibly establish an "ask the expert" central contact point, a web service hotline, a place to answer questions beyond "basic" CLF topics.
  2. Existing and suggested tools discussed:
    • Forums: Graphics had previously implemented a forum but received little traffic.
    • Mailing lists: consolidate and extend mailing lists to announce CLF events, CLF changes, Web Advisory Committee items, etc.
    • CPA's webdev blog.
    • Departmental help web pages: an example David R. Cheriton School of Computer Science.
    • Meetings: Andrew suggested per term meeting with web personnel to share ideas and discuss what's new.
  3. Navigational issues will be reserved for navigational sub-group but the following comments are documented for the navigational sub-group
    • Create a possible toolkit to allow users the option to customize the left navigational which would highlight the users current navigation location (know where you are positioning).
    • Future recommendation: use of a standard top navigation menu, breadcrumbs, (Faculty of Arts demo).
    • Future recommendation: investigate several navigation options "after" navigation is defined.

-- JasonGreatrex - 29 Oct 2007