Outline:
- Intro
- article explains user roles working with the Magnolia Admin Central
- scope of this article: interface design trail, analysis
- motivation for this article
- users have different expectations, requirements and skills: "simple-to-use" vs. "available advanced configuration options"
- the GUI should address those expectations accordingly, rating the realized features by the most important requirements of the appropriate user
- outcome/goal of this article
- the developers need to keep the user group and their skills in mind when designing and implementing a feature; this article should sensiblize the developer for the users' characteristics ("know the user")
- definitive personas are developed to remember user roles
- User Roles And Their Characteristics
- the four roles: editor, manager, administrator, developer
- basic characteristics: the user-roles matrix
- factors: usage intensity, usage frequency, application domain knowledge
- "(side) note"/excursion: the 7 principles of interaction design => pointer to next article
- relationship to basic principles of interaction design
- note that usage frequency of course depends on update frequency of web content (up-to-dateness of web site)
- application domain knowledge: actually separate two different things: knowledge about Magnolia (CMSs) and company/commercial websites
- factors: usage intensity, usage frequency, application domain knowledge
- Details about each role
- the editor role
- explain the basic characteristic
- usage intensity: layman, little experience;
- layman in developing websites (programming, technical details about the web); little experience in using web-based software especially web content management systems (web based systems have their characteristics, e.g. server delay/response times; no desktop software regarding e.g. keyboard behavior, you have to "upload" stuff; normally not concerned with distributed, concurrent working)
- usage frequency: regularly;
- oftenly dedicated person in a company/department/team; depends on update frequency of web content, ultimately on size of company using Magnolia and business goal of website (e.g. a news site's editor frequently uses Magnolia)
- application domain knowledge
- company website: substantial knowledge of pages and their contents at least of the departments part of the site, since daily working with/communicating it
- CMS (e.g. knowledge about the range of the CMS' feature-set): none, e.g. virtual URIs etc. likely won't be a word in the editors's vocabulary; whereas basic web vocabularies like "link" are
- typical tasks of this user
- creating and editing pages/contents
- organizing content (uploading, moving etc.)
- scope: website, documents, data
- not concerning about configuration, security, deployment etc.
- persona: "Edward, the EDitor"
- "(side) note"/excursion: personas; about personas in general: should be a (relatively) simple to remember conclusion; "simple to identify with"
- the manager role
- persona: "Mark the MAnager"
- the administrator role
- persona: "Andy the ADmin"
- the developer role
- persona: "Daniel the DEveloper"
- the editor role
- What's next?
- next article(s) will discuss principles of interaction design and their consequences as well as general usability and business goals
- invitation to the developers: print the personas and never forget them
