Difference between revisions of "Common Look & Feel (CLF) - WEB"

From SFU_Public
Jump to: navigation, search
m
m
Line 29: Line 29:
 
= Look and Feel<br>  =
 
= Look and Feel<br>  =
  
Can further be broken down into; Graphics, Photography, Branding, Page layou, etc.&nbsp;<br>  
+
Can further be broken down into; Graphics, Photography, Branding, Page layout, etc.&nbsp;<br>  
  
*Search improvements - BRANDING - Can the search results page LOOK like an SFU page? (ie include CLF)<br>  
+
*Search improvements - BRANDING - Can the search results page LOOK like an SFU page? (ie, include CLF)<br>  
*Labelling for department name in top banner. TYPOGRAPHY (related to navigation issues, a larger font size could improve a users sense of "where" they are<br>  
+
*Labelling for department name in top banner. TYPOGRAPHY (related to navigation issues, a larger font size could improve a users sense of where they are<br>  
 
*Right column width needs to be larger (for why?)  
 
*Right column width needs to be larger (for why?)  
 
*SFU LOGO - does it even look like a link?  
 
*SFU LOGO - does it even look like a link?  
 
*<br>
 
*<br>
  
<br>  
+
<br>
  
 
= Technical implementation  =
 
= Technical implementation  =

Revision as of 21:11, 29 September 2011

SFU's common look and feel (CLF) standards for web design are found here http://www.sfu.ca/clf/web.html


CALL FOR INPUT

There are no plans officially to update the CLF, but we would like to gather up the issues and make some reccomendations to be carried forward to the CMS steering committee.

The information below is taken from (but not limited to) internal discussions and emails from sfu webmasters.  It is being recorded on this wiki to encourage discussion and contributions from all in the SFU community. Please feel free to add your issues, complaints, suggestions below, or make comments and ask questions on the discussion page.  Sept 28 2011.



Navigation

The navigational elements of a website are mostly concerned with the menu system, its organization and placement. Also, it may include problems with the SFU search, and key navigation or "landing" pages. (eg, A-Z)

  • Search improvements - USABILITY - How to deal with SFU search vs. sub domain search and search the web options.
  • Left hand menu for sub pages - Colors and typographic states could be re-thought. Indentation reduces menu width. Animated menus may be a solution.
  • SFU logo link - Where should the SFU logo in the top left corner link to? (SFU HOME? Sub Domain home?)
  • Resolve usability issues with Burnaby, Surrey, and Vancouver "home" sites. Do campus home pages add more confusion? What do users think? How do we resolve Faculty and program sites that have services on multiple campuses.
  • A-Z list  - should it be contextual to the sub domain you are on?
  • The A-Z list is an old 'stop-gap' solution from before there was a CLF.  Does it make any sense to promote it at such a high level? it is essentially the site map page, which is common on most websites, but usually not made such a big deal of (drop down menus etc.).


Look and Feel

Can further be broken down into; Graphics, Photography, Branding, Page layout, etc. 

  • Search improvements - BRANDING - Can the search results page LOOK like an SFU page? (ie, include CLF)
  • Labelling for department name in top banner. TYPOGRAPHY (related to navigation issues, a larger font size could improve a users sense of where they are
  • Right column width needs to be larger (for why?)
  • SFU LOGO - does it even look like a link?


Technical implementation

The stuff you dont't see. The technologies used to build the banner and its navigation system. The CLF project will have the most impact on the CQ5 content management system and its templates.

  • Search improvements - RESULTS - How is search implented can a new infrastructure make it as good as an actual google search?
  • Fix 404 error on searches made from search page




Possible actions:

  • Include SFU search page in the CLF. Run new project to improve results and the searching experience in general.
  • Review page stats, identify most common pages and user paths - where are users going? what are they looking for?