Update the information architecture for Acquia Docs
Problem
The site structure of Acquia Docs, our product documentation site available to 4,000+ customers, was confusing to customers and internal staff. The homepage was overloaded with content, including lengthy dropdowns, all software Acquia created as products, and more.
The branding also did not align to Acquia.com, so the experience between the two sites felt disjointed and did not give users confidence in the Acquia brand. Last, it wasn't accessible.
Project goals
These were the stakeholder goals for the project:
-
Determine a new information architecture for Acquia Docs.
-
Show the value of content design post-acquisition.
-
Show how research can be used to inform content decisions.
Where I came in
First steps:
-
Learn about the process for creating and updating Docs content.
-
Develop relationships with Learning Services team members who maintain documentation. (Widen, the company I worked for, was newly acquired by Acquia when this project was assigned.)
-
Gain an understanding of the current site structure, content itself, and content strategy through a content audit.
-
Determine who uses Acquia Docs, why they're using it, and how they find product information.
Second steps:
-
Analyze site performance after release and recommend changes based on data gathered.
-
Collaborate with product designers to create new site designs with Acquia branding and the updated IA.
Roadblocks
So many. I recall feeling like I was floundering at some points due to:
-
Project ambiguity.
-
Keeping it moving and figuring out what to do next when things were ambiguous.
-
Getting information about existing site problems from the Director of Learning Services and other internal resources. People knew they didn't like it, but not why.
-
Getting a product designer involved.
-
Finding time to develop relationships with Director of Learning Services, technical writers, technical architect, community manager, and others from Acquia who I hadn't yet worked with due to the acquisition.
Collaborators
To make this project happen, there was much collaboration across Acquia. During the course of this project, I connected with:
-
Learning Services
-
Product design
-
Product research
-
Community manager
-
Technical architect
-
Director of content strategy
-
Product marketing
-
Marketing
-
Service design manager
Results
Increased user adoption of the site.
Happy stakeholders.
The output: A new (and old) information architecture!
Note that the page content design and content included has been updated further based on data I've gathered from Google Analytics and Microsoft Clarity after site launch in February 2024. See the most current Acquia Docs site.
Click the image to enlarge and scroll through the carousel.
An image of the old Acquia Docs home page. This site is for users to find answers to questions for Acquia products.
An image of the former information architecture of the Acquia Docs homepage.
An image of the new information architecture of of a help articles in Acquia Docs.
An image of the old Acquia Docs home page. This site is for users to find answers to questions for Acquia products.