EVOLVE'14 | Enhance | Anshul Chhabra & Akhil Aggrawal | Cisco - AEM High Availability
EVOLVE'15 | Maximize | Mark Trenchard | Top 10 AEM Mistakes
-
Upload
evolve-the-aem-community-conference -
Category
Technology
-
view
274 -
download
0
Transcript of EVOLVE'15 | Maximize | Mark Trenchard | Top 10 AEM Mistakes
AUGUST 17, 2015
TOP 10 AEM M ISTAKES MADE WITH PUBL ISHERSRisking the investment
Mark TrenchardDir, Digital Experience
Stanford Medicine
2
rai·son d'ê·treSpeed, ease, and quality of publishing
3
AEM @ Stanford2 Years live
2 Author instances3 Publish/dispatchers
3 Design themes40 components
200 Sites700 users
20000 pages40000 assets
5.6.1 SP16.1 by Thanksgiving
4
#10 Slacking on the sidekick
5
What we learned
• The term sidekick didn’t have meaning to our authors
• The icons provided no meaning
• Default groups were not meaningful
• Semantic name
• Groups that make sense
• Icons that make sense
• Flatter, modern style
• Upgraded perfectly to 6.x
Still to do: rich tool tips that describe component, favorites group
6
GoalsReduce search time
Increase clarityImprove access to help
How about the Granite sidebar? Better, but can use some
love.
7
#9 Dialog nonconformities
8
What we learned
• UI patterns in AX matter like everywhere else
• The kitchen sink in a tab can be overwhelming
• Need options, but UX can help limit author
• Authors will adopt to patterns
Tab Patterns
Edit Menus
9
#8 Mystery properties
10
What we learned
• Visual options are hard to describe and use in simple selector fields
• Authors are visual
Make visual options visual
file:///.file/id=6571367.5895753
11
#7 Refreshing your way to eternity
12
What we learned
• Latency kills the AX and becomes a primary blocker
• Authors don’t understand the need
• Parsys volume has a large overhead
Attack from multiple angles
Invest in server powerAudit all refresh events
Develop component refreshes
Test under stressed pagesOptimize parsys loads
AJ
13
#6 Find your own content
14
What we learned
• Authors dislike and avoid browsing around for content
• Embedding from third party sources is a hassle (code/ID pasting, etc)
• Authors don’t always think about content in #cf
Fill the content finderAdded primary content sources
People, multimedia sourcesPass through authorization to
maintain permissions
From #Twitter: Make CF easier to close and open
15
#5 The great help hunt
16
• Authors forget easily unless they use something constantly
• People need help in the moment of authoring
• Adobe hard-coded help links are not helpful and misleading
What we learnedHelp in context
In component
In landing page
17
#4 Using dialogs for everything
18
What we learned
• Visual layout edits are very abstract when forced into forms
• Authors naturally interact with layout tools and are disgusted if you make them leave the visual space.
Accordion
Tabs
Navigation
19
#3 Provisioning as an art and blank canvas
20
What we learned
• Authors despise waiting for something they perceive as a push-button event.
• Large numbers of groups and nodes make permission setting frightful
Create a jigStarter site with sample layouts
Create simply utility Site, asset, tag nodes
GroupsPermissions
User assignment to groups
STEP 3Add groups and users
STEP 2Setup Options
STEP 1Theme
What about the Granite UI?
22
#2 More is better
23
What we learned
• The more we offer authors, the more they forget and get confused
• Flexibility without volume of options is desired and hard to do
• Clutter and choice are not positives
Natural combinations
Panels: columns, boxes, rows
Feature box: all teaser layouts
24
#1Not paying someone to advocate for publishers
25
What we learned
Created a role that still exists:• Write and approve stories to
optimize AX• Test against real-life cases• Train the publishers
• The implementation team was focused on design, features, and content development.
• AX was being sub optimized at best.
Hired this guy!
26
facebook.com/stanfordmedicine@trenchard
linkedin.com/company/stanford-university-school-of-medicine
#me/#us