Create and maintain Acquia DAM (Widen) product documentation
Problems
-
Customers could did not have a central location to go when they had questions about Acquia DAM (formerly, Widen Collective).
-
Content was scattered across various resources (e.g., sales advisor emails, white papers from product managers, release notes, Jira cases, Confluence pages, and other sources).
-
Content was repeated in varying ways in resources.
-
There were no writing styles and standards in existence.
Project goals
-
Set forth a content strategy and framework for Acquia DAM product documentation.
-
Align existing documentation from different sources under the content strategy.
-
Maintain and update documentation as products, features, and enhancements were released.
-
Edit documentation to align with the style guide. (And create writing a style guide.)
-
Create processes for requests for documentation updates.
-
Audit annually and make any changes.
-
Create new documentation based on audits and from feedback from customers via the Support team and UX researchers.
-
Be the SME and point of contact and decision maker for documentation.
Where I came in
Draft new content - including bi-weekly and monthly release notes and new help articles - and update existing documentation for each product release.
Collaborators
For Acquia DAM product documentation, I would collaborate with the the following:
-
Product managers
-
Engineers (front- and back-end, QA)
-
Product designers
-
Product marketing managers
-
Support team
The output: DAM product content
Here's a link to product documentation that I worked on in our DAM community site.
An image of the categories of content available in Acquia DAM product documentation.
An image of the "What does each permission mean?" article in Acquia DAM's product documentation.
An image of the list of some available articles about Entries, an app in Acquia DAM. These articles are available in Acquia DAM product documentation.
An image of the categories of content available in Acquia DAM product documentation.