1 / 10

Help BOF Vancouver Conference, May 2006

Help BOF Vancouver Conference, May 2006. Previously led by IU (which is still involved) UCT agreed to take on project leadership (Apr 06) Created as a Sakai Project Top-level svn folder https://source.sakaiproject.org/svn/help/ Collab email list help@collab.sakaiproject.org )

ann
Download Presentation

Help BOF Vancouver Conference, May 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Help BOFVancouver Conference, May 2006

  2. Previously led by IU (which is still involved) UCT agreed to take on project leadership (Apr 06) Created as a Sakai Project Top-level svn folder https://source.sakaiproject.org/svn/help/ Collab email list help@collab.sakaiproject.org) Confluence space http://bugs.sakaiproject.org/confluence/display/HELP/ Help needs your help! The Help Project

  3. Broad: Help users achieve what they want to achieve when using the application Narrow: Evolve the online Help tool Ensure that Help content in Sakai releases is useful, accurate and up to date Ensure that information about how to configure and use the Help tool is accurate and up to date Help Scope

  4. Portal Popup window is resizable display.help.menu, display.help.icon options Tool help.welcomepage setting Some minor HTML and rendering changes (e.g. removed unnecessary scrollbars Menubar/tool access and searchers are now logged as events Content Use consistent set of styles helpBody div for margins Relative links to documents Updates from IU KB for 2.1 help content (xml > xhtml conversion with updated .xsl file) Help changes in 2.2

  5. Localization dynamic language selection (including support for language-specific indexes) supporting local changes (for example tool names, local terms, site types, roles, images) Versioning updates within a version (e.g. corrections) updates across versions (minor/major releases) Content formats User interface Help Big Issues

  6. We need to gather more requirements & wishlists before implementing significant changes Supporting different institutional contexts, for example: IU: REST from IU KB Michigan: external help docs UCT: OOTB (with edited content) Some sites: disabled. How are you using help?

  7. Help Content IU Knowledge Base(KBML / XML) Standalone tool content (HTML) REST Help Consumer (XML, via XSL to HTML) OOTB Help (HTML)

  8. XML / XSL changes to support localization requirements Native XML format for help content (in parallel to KBML/XML format) Help content changes

  9. Redesign the layout (replace left-hand-side stacked panels with tabs) Role-specific views Capturing user feedback Dynamic responses (e.g. most popular documents, recommendations) ` Help UI

  10. Context-sensitive rather than tool-sensitive (dependent on how the tool title is rendered) Other ways of presenting help information (e.g. wiki) Help, the portal and tools

More Related