CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions »
  • Usability Improvements (Moderator: Dave Greenberg) »
  • More uniform help
Pages: [1]

Author Topic: More uniform help  (Read 2146 times)

sawjer

  • Guest
More uniform help
December 11, 2008, 05:12:16 pm
The version 2.2 looks nice and has many improvements. For 2.3 I would like to propose a streamlining of help

In the upcoming 2.2 I can see
- Overview information (e.g. see custom data) that leads the user to a wiki that explains the overall concept concerning this page
- At some place a ?-button to call up context help for fields to enter
  alternatively on some pages (e.g. new mailings) the context help is added as always visible text between the fields
- On same pages the ?-button with access shortcust, mostly at the bottom

I would like to see in 2.3 the following streamlining of already available functions:

On every page top a button  to call up general help to this page, linking to a wiki, that contains the user online documentation. To unclutter, remove any lead text to the wiki as in custom data configuration.
Allow to link to the wiki be either the standard one or a link to either an other language or a custom made wiki. (This may be of importance as some applications will have to cater for ordinary people who would be lost with most of the present documentation).

For every field the user can enter a ?-button with short context help. To unclutter, a fieldset could be used with a single ?-button in the title of the fieldset that responds to all fields of that set. Also, instead of a clumsy button used now, a simple '?' image could be used.
I would like to emphasise: have context help for every field and replace additional explanatory text (as in new mailing) by a ?-button.

Move the access key button to some menu page for user GUI where the user is instructed on shortcuts and can possibly change some behaviour of the GUI.

Give is a slik look and feel: These proposed changes would markedly improve the look and feel of civicrm: Less information on a page but consistent access to more information if needed.

I have used this approach in my CMS with very good result.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: More uniform help
December 12, 2008, 09:54:39 am
I think these are good suggestions. I've posted a note to our i18n folks to think about how to manage different sets of wiki (overview doc) links for different languages / contexts. I'll talk to the team about migrating in the direction of ?-buttons replacing most / all inline text (we've been doing this pretty consistently on newer forms).

Regarding the ?-button look and feel ... We will be moving to jQuery as our Ajax library in 2.3+. If you can submit a patch for 2.3 that replaces the existing dojo button - graphics and behavior - which a jQuery based mechanism with a cleaner look - that would help move this along.
Protect your investment in CiviCRM by  becoming a Member!

sawjer

  • Guest
Re: More uniform help
December 12, 2008, 11:11:48 am
Thank you for your help, I really lappreciate it.

I will try to provide a sample, once I come round.

About look and feel: From my customers I get admiration for the possibilities of civicrm but they all complain about overloaded and too technical interfaces, ordinary people find daunting.  I know, custom forms can do much to improve. Good look and feel weighs heavily on me.

Piotr Szotkowski

  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: More uniform help
December 18, 2008, 09:07:48 am
Quote from: Dave Greenberg on December 12, 2008, 09:54:39 am
I've posted a note to our i18n folks to think about how to manage different sets of wiki (overview doc) links for different languages / contexts.

…and CRM-3941 has been filed for CiviCRM 2.3. :)
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions »
  • Usability Improvements (Moderator: Dave Greenberg) »
  • More uniform help

This forum was archived on 2017-11-26.