Platforms that we work with
Drupal 6/7
Adobe Experience Manager
Open edX
others?
Med School recently went through a change from Drupal to reevaluate and go with AEM because of the compelling authoring experience. Went through redesign, replatform, and content migration at the same time. Med has had a Liaison that works with different communities on addressing their concerns.
What are the most challenging tasks that the author has to face?
Components and/modules that are worked with that help/hinder the process?
What kind of experience are people coming from?
How do descriptions and/or help text help authors/users?
Proposed topics:
Cynthia (SWS) - What are people looking for, and what interest is there?
Jason - How do you address the need?
Greg (VPOL) - Interface with faculty, etc. How do you get training and get people to adopt it.
Frank (Law school): Mix of WP, other systems. 300+ content editors.
Anne (Center for Intl. development) -
Christopher (CDE) - Coming up with strategies for using various systems together.
Adam Moore - GSB.
Rochelle (EE, content manager) - Use box for content. Events, gathering and presenting information.
Peter Chen (school of Engineering) - what kinds of experiences can we relate to from other CMS that they use every day (FB, twitter, amazon, etc.)
Discussion:
Value in building experiences that people want to come back to and build more and more content.
Out of the box, AEM has a minimal way of providing authors ways to create what they want to build on top of. Things like dragable UI components. People like visual and graphical pieces that help them visualize the product. Build a responsive layout into the panel builder. Not allowing the author to think about responsive design. Permissions based administration. Did not want authors to think about code. Segregating the code from the authoring experience. Medicine has managed to achieve a fair amount of balance to give end users a fair amount of flexibility.
How to address Architecture? Who owns these decisions? Agile approach where business owner makes a decision on what gets built. Propose a development story, and a project owner. Having a change advisory board (IT) that helps guide the process address things including security, design, other initiatives. Having a scrum manager.
There is a help button that goes to documentation. Help desk tickets. If there is good inline information, training, self-help information. Video training that is created in advance.
At the end of a sprit cycle, a presentation is given to stakeholders, including help desk so everyone can be familiar with the changes and how to support it.
ways to address training: Video, online help, help desk tickets, open help sessions (Q&A), in class (prepared) training.
Dev team should have responsibility so that the author can get things out there with minimal training.
"There isn't a silver bullet"
Ease of use is a big part of what makes it work.
How to create a compelling authoring experience in a CMS
Proposed by Koorosh
Notes
