...
- 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
- "(side) note"/excursion: personas; about personas in general: should be a (relatively) simple to remember conclusion; "simple to identify with"
- the editor/author role
- typical tasks of this user-role
- creating and editing pages/contents
- organizing content (uploading, moving etc.)
- scope: website, documents, data
- not concerning about configuration, security, deployment etc.
- typical tasks of this user-role
- differentiate two different scenarios: call them "editor" (sporadic) and "author" (regularily)
- the role ultimately depends on size of company using Magnolia and business goal of website (e.g. a news site's editor frequently uses Magnolia, however a secretary of a little 10 people non-IT-company doesn't)
- explain the basic characteristics
- "editor": 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, no tabs available etc.; normally not concerned with distributed, concurrent working)
- usage intensity: low
- only make use of Magnolia's basic editing capabilities
- usage frequency: sporadically
- not dedicated person in a small company/department; website where content doesn't change much
- 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
- relationship to 7 principles: self-descriptiveness, expectation conformance, failure tolerance, learning support
- persona: "Edward, the EDitor"
- "author": medium experience
- usage frequency: high
- oftenly dedicated person in a company/department/team; this is the case when web content updates frequently, e.g. an author of a news site
- creates/edits a large amount of content
- usage intensity: medium/high
- uses Magnolia's editing features only, however, those intensively
- application domain knowledge****** company website: substantial knowledge of a certain set of pages and their contents (e.g. the departments part of the site) since he is daily working with it/communicating it
- CMS: knows editing capabilites only, however those intensively
- persona: "Antony 'Tony' the author"
- usage frequency: high
- "editor": layman, little experience;
- the publisher/manager role
- role comes up for its own only in bigger companies or at least companies with many editors (such as news sites with many authors)
- typical tasks
- reviewing, publishing/rejecting changes
- configures website sections / mappings between website <-> data module
- might even configure access restrictions (partly) => administrator
- explain the basic characteristic characteristi
- usage frequency: regularly
- usage intensity: medium experience;
- normally, managers have been shifted from some degree, thus it's very likely that they have been working as editors before for a longer time . Thus they aand have more experience using Magnolia
- use publishing capabilities (activation, deactivation, workflow, messaging/inbox)
- use search/filter functionalities
- bulk changes
- advanced tools (maybe not yet present) like versioning, deferred activation, diff tool
- persona: "Mark Paul the MAnagerPublisher"
- the administrator role
- persona: "Andy the ADmin"
- the developer role
- persona: "Daniel the DEveloper"
...