the Pain
Those who update and manage website content typically find the content management system (CMS) unintuitive and too hard to use.
the Cause
The web development process focuses on the technology supporting the site and on the user experience of those visiting the site. That process has ignored the perspective and workflow for the nontechnical staff that uses the CMS to manage content.
the Solution
Web development needs to embrace a new discipline – one that tailors the CMS with a focus upon the CMS end users, their business perspective, their workflow, and "backend" usability. The iCue Project explores this new discipline with the goal of articulating principles and best practices, developing patterns and products, and demonstrating improvements.
User-Centric: standard interface features
Rely on standard interface features (menu bar, dropdowns, radio buttons, etc) instead of creating new and clever ones.
Insulate: from admin roles
If a user has significantly differing types of roles (in particular: admin vs content management), give that user a unique login for each role type. Typically, disjointed roles are performed at different frequencies and in significantly different contexts/needs.
Insulate: from formatting and needless decisions
Insulate the user from
all formatting and structural details that he should not change.
and from decisions he does not need to consider.
Insulate: from mistakes
Reduce the likelihood (and consequences) of the user making a mistake (that causes harm or must be undone, or distracts from the objective).
User-Centric: task-based interface
Provide a clear starting point and successive steps for performing a task. Avoid generic solutions in favor of a task-specific interface.
User-Centric: mental model
Tie into the user's mental model: the visual front-end. This is the natural and intuitive way of how a person percieves a website.
Tailor: segment users
Segment users to deliver tailored user experiences, base upon...
the user's capabilities,
the user's level of responsibilities, and
the resources to be managed
Simplify: single path per task
Provide a single, clear path to accomplish a task. Don't confuse the user with multiple options for doing the exact same thing.
Simplify: lean and effective workflows
As much as possible...
model the workflow after the business decisions and options a user needs to make
automate/hide the mechanics and steps that implement the workflow
Simplify: scope
Provide the user only what he/she needs and is capable/willing to use.
Simplify: terms
Replace technical terms with those that are commonly understood by user.
subscribe to update notices
Articles and Presentations
Presentation: Making Joomal Sites Easier for Our Clients to Manage
Joomla World Conference (EBay/San Jose, November 2012)
Presentation: Real Life ACL
Joomla World Conference (EBay/San Jose, November 2012)
Presentation: Role-Based ACL
Microsoft offices, Manhattan (NYC, Sept 2012)
Joomla Day (Chicago, August 2012)
Article: Implementing Role-Base ACL
(September 2012)
Article: A Case for Role-Based ACL
(August 2012)
Presentation: Improving the Client's User Experience
J and Beyond (Germany, May 2012)
Article: Customizing the Admin Menu
Joomla!® Community Magazine, April 2012
Article: Customing an Extension's Edit Screen
Joomla!® Community Magazine, February 2012
Article: Leveraging Joomla's ACL in Mission Control, Part 1
RocketTheme Magazine, January 2012
Part 2, March 2012
Presentation: Improving Joomla's Backend User Experience
Joomla! Day Midwest, November 12, 2011