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

From SFU_Public
Jump to: navigation, search
Line 1: Line 1:
 
SFU's common look and feel ([[Common Look & Feel|CLF]]) standards for web design are found here [http://www.sfu.ca/clf/web.html http://www.sfu.ca/clf/web.html]<br>  
 
SFU's common look and feel ([[Common Look & Feel|CLF]]) standards for web design are found here [http://www.sfu.ca/clf/web.html http://www.sfu.ca/clf/web.html]<br>  
  
The standards have gone relatively unchanged since their inception in 2006. The SFU web design community is collaborating on, and gathering information that may inform decisions about the future direction of the guidelines.
+
<br>
 
+
Please feel free to add your issues, complaints, suggestions below, or make comments and ask questions on the [https://wiki.sfu.ca/public/index.php?title=Talk:Common_Look_%26_Feel_%28CLF%29_-_WEB&action=edit discussion page].&nbsp; Sept 28 2011.
+
 
+
<br>  
+
  
 
'''Current issues for the CMS Steering committee'''<br>  
 
'''Current issues for the CMS Steering committee'''<br>  
  
The information below taken from (but not limited to) internal discussions and emails from sfu webmasters.&nbsp; It is being recorded on this wiki to encourage discussion and contributions from all in the SFU community.  
+
The information below is taken from (but not limited to) internal discussions and emails from sfu webmasters.&nbsp; 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 [https://wiki.sfu.ca/public/index.php?title=Talk:Common_Look_%26_Feel_%28CLF%29_-_WEB&action=edit discussion page].&nbsp; Sept 28 2011.  
  
The issues of concern may pertain to one or more of the following areas; Navigation, Graphics, Information, Technical. Feel free to add as needed.<br>  
+
<br>  
  
 
<br>  
 
<br>  
Line 19: Line 15:
 
The naviagtional elements of a website mostly are concerned with the menu system, its organization and placement. Also, it may include problems with the SFU search, and key navigation or "landing" pages. (ie A-Z)<br>  
 
The naviagtional elements of a website mostly are concerned with the menu system, its organization and placement. Also, it may include problems with the SFU search, and key navigation or "landing" pages. (ie A-Z)<br>  
  
*Search improvements - USABILITY - How to deal with SFU search vs. '''sub domain search '''and search the web options<br>  
+
*Search improvements - USABILITY - How to deal with SFU search vs. '''sub domain search '''and search the web options.<br>  
 
*Left hand menu for sub pages - Colors and typographic states could be re-thought. Indentation reduces menu width. Animated menus may be a solution.<br>  
 
*Left hand menu for sub pages - Colors and typographic states could be re-thought. Indentation reduces menu width. Animated menus may be a solution.<br>  
*SFU logo link - Where should the SFU logo in the top left corner link to? (SFU HOME? Sub Domain home?)
+
*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.<br>
 +
*A-Z list&nbsp; - should it be contextual to the sub domain you are on?<br>
 +
*The A-Z list is an old 'stop-gap' solution before there was a CLF.&nbsp; 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 website, but usually not made such a big deal of. (drop dpwn menus etc.)<br>
 +
*<br>
  
 
<br>  
 
<br>  
Line 34: Line 33:
 
*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>  
Line 39: Line 39:
 
= Technical implementation  =
 
= 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. As such, it will serve as the future framework for building all new SFU websites.
+
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.<br>
  
 
*Search improvements - RESULTS - How is search implented can a new infrastructure make it as good as an actual google search?<br>  
 
*Search improvements - RESULTS - How is search implented can a new infrastructure make it as good as an actual google search?<br>  
*Fix 404 error on searches mad from search page<br>  
+
*Fix 404 error on searches made from search page<br>  
*
+
*<br>
 +
 
 +
<br> <br>
 +
 
 +
'''<br>'''
 +
 
 +
'''Possible actions:'''<br>
  
<br> Possible actions:<br>  
+
*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?<br>
 +
*<br>
  
Include SFU search page in the CLF. Run new project to improve results andthe searching experience in general.
+
<br>

Revision as of 20:26, 29 September 2011

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


Current issues for 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 naviagtional elements of a website mostly are concerned with the menu system, its organization and placement. Also, it may include problems with the SFU search, and key navigation or "landing" pages. (ie 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 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 website, but usually not made such a big deal of. (drop dpwn menus etc.)


Look and Feel

Can further be broken down into; Graphics, Photography, Branding, Page layou, 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?