arm developer - amazon s3 · 2019-04-24 · •architectures vs. processors? • no organization to...
TRANSCRIPT
Chris RoystonLinaro Connect BKK19
Arm DeveloperWhat we learned about you,
and the changes we are making
2 © 2018 Arm Limited
Who am I?
• Chris Royston• Senior Manager, Content Services in Arm’s Sales and Partner Enablement Group
• Content Services responsible for:• Researching, defining, and delivering changes to Arm’s technical content platforms• Producing technical and e-learning content for Arm• Making Arm Developer the place to learn, develop, and collaborate on Arm
What we learned about you
4 © 2018 Arm Limited
What we learned about you
Less than 1 year 1-10 years 10+ years
Where you came from What you do Experience on Arm
Software Hardware Firmware OtherAsia Europe Americas Other
Key findings
6 © 2018 Arm Limited
Competitor researchThe best user experiences:
• Stick to a ‘single site’ model• create a unified user experience
• Pick a clear taxonomy and stick with it• keep the structure simple and consistent
• Provide ‘getting started’ resources • Call out key tasks/scenarios• Teach by example(s)
7 © 2018 Arm Limited
Top areas of concern “the easiest way ... is outside of Arm with the Search engine”
• Rely on stackoverflow for
answers to development
questions
• Often top Google search result
• Appreciate the site
moderation, AKA quality of
content
• Little awareness of
Arm Community
• Unable to relocate previous
helpful search result(s)
Search Navigation Community
• Tend to arrive deep in site
from Google
• Inconsistent pathways to the
same types of content
• Unclear which is the primary
site for them:
• (Arm.com, Arm Developer,
Community, Infocenter, etc.)
• Getting started information
missing
• Users unable to find content
• Tend to use Google over site
search
• Inconsistent quality/
presentation of results
• Unable to relocate previous
helpful search result(s)
8 © 2018 Arm Limited
Page-level observations
”more on how to get started … and additional examples”
• Unclear where to find their
product
• Architectures vs. Processors?
• No organization to tree
• Infocenter still preferred
• Preferred but still not ideal
• Many arrived there after
giving up on Arm Developer
Finding information Unmet content needs Documentation pages
• Users need ‘getting started’
content
• How to vs. reference
• More real-life examples
needed
• Language is confusing
• Lack of consistency in pages
• Deeper level of information
needed
• Benchmark data
• More graphics, less words
• Duplicated, or inconsistent
navigation
• More direct links to related
content/documentation
• More consistency of search
results
• Plus search filtering required
• Google search more likely to
yield required result
What have we changed?
10 © 2018 Arm Limited
Information architectureWe moved from:
Home
Products Solutions Technologies Support Embedded SW development Education Research Graphics &
multimedia SoC design HPC
11 © 2018 Arm Limited
Information architectureTo:
Home
IP Products Tools & Software Architectures IoT Community Support Documentation Downloads User activity Key tasks Solutions
12 © 2018 Arm Limited
Information architectureMultiple pathways to content
User activity
Design an SoC Work with hardware
Develop software
Key tasks
Optimize software Etc. Etc.
Solutions
Gaming & App development Infrastructure Etc.
Gaming software optimization
content
Tools & Software Community
Documentation
Etc.
What’s coming next?
14 © 2018 Arm Limited
New Documentation hubMore robust back-end infrastructure, new front-end and UX
• ETA Q3 2019• Confidential docs
15 © 2018 Arm Limited
Move to Arm 2.0 brand
• ETA Q4 2019• New look & feel
Q&A … of sorts
17 © 2018 Arm Limited
We’re going to use Mentimeter
Go to www.menti.com and use code 25 46 40
Got feedback after Linaro Connect?
https://developer.arm.com/BKK19
Thank YouDankeMerci��
�����Gracias
Kiitos감사합니다
ध"यवाद رکشت
© 2019 Arm Limited
The Arm trademarks featured in this presentation are registered trademarks or trademarks of Arm Limited (or its subsidiaries) in
the US and/or elsewhere. All rights reserved. All other marks featured may be trademarks of their respective owners.
www.arm.com/company/policies/trademarks