ADOBE CONTENT MANAGEMENT
Project purpose: To create a unified content library for use by all Adobe Experience Cloud products.
Target users: Marketing professionals who plan create and or deliver marketing initiatives that require digital assets.
Duration: 6 months, with 50% of my devoted to it.
My Role: Lead designer throughout the project.
Team Members: Matthew Deutsch: project manager. Youjin Choi: supporting design team member. Ross Phaler, Danielle Robinson, Devon Govett: Engineering.
Project Advisors: Jordan Kretchmer: executive sponsor. Andreas Kuefer, design management. Lindsay Browne: design systems. Andy Welfle: content strategy.
Initial designs assumed the the tool would exist only as a single web destination but after speaking to users and stakeholders it was determined that an SDK was necessary for existing solutions to incorporate it into their products and workflows. This required 2 additional expressions for the solution, a modal and rail version where each solution could determine how and when to use each variants.
I began by creating wireframes of how content could be viewed, arranged, added, navigated and searched. Patterns for multi-select and filter pills persisted to the final product.
Social Search Wireframe
During the project Adobe acquired Livefyre a company that focused on searching and managing user generated social content, so we aligned efforts with them and incorporated their technology.
Final Design: WEBPage
There are three versions of the solution, a full page view that is accessed from the solution switcher in the black bar as well as a modal and rail version that solutions can incorporate into their existing and future workflows as they see fit. The following screens show some of the final designs for the web version of this content management UI.
A filters rail is toggleable and any filter selections show up as pills on top of the content.
Final design for social search UI, users can browse, search, save and repost any asset or activity found on most social networks.
CONTENT SDK: Modal
Throughout the design process we wanted to ensure consistency across all 3 expression of the product (webpage, modal and rail) and provide a similar feature set as well as UI consistency in appearance and operation. One way we did this was have the asset detail and edit pages be identical whether they were triggered from inside the modal view or from the rail.
Browsing + Filtering
Folders appear as cards with previews in the modal version, due to real estate constraints and also as this expression was less about content management and more about selecting and finding assets quickly from inside a workflow.
All Header States
This page shows all header states for webpage and modal versions of the SDK. This was done to ensure the patterns and call to actions were consistent. It also helped in ensuring we accounted for all use cases.
CONTENT SDK: Rail
The rail version of the content SDK was required for solutions that create activities such as Campaign and Target. The rail is used as an asset browser alongside their corresponding editing and creation UIs, be it for emails, or website A/B tests. I gathered requirements from these teams to understand their users and workflows and to ensure my design proposal would improve those products. I partnered with the designers on these teams to ensure we maintained similar patterns throughout all our work.
The entire product relied on expressions of different types of assets in different sizes so a wide range of card designs needed to be defined, I designed and maintained them from one art-board to maintain visibility of features for engineering and product management as well for design to maintaining style and UI pattern consistency.
Adding more formats such as 4k video, VR content, 3D model formats as well as code snippets for websites and email templates as well as more light asset editing features. We planned for adding the ability to request content from creators from inside the solution, and tie that into a panel in our Creative Suite of tools. The ability to add more storage providers such as Google Drive, Box and the ability to link to combines on premises CMS would benefit it.
I pitched this content management project as potentially being part of a much bigger initiative where it could become the foundation for a brand new product centered around marketers focused on content and a unique means of leveraging Adobes existing strength in content creation. This sitemap shows how this content management project could be part of a bigger solution that incorporated a means of planning, monitoring and creating marketing activities. It was the impetus for new project: a marketing calendar which I Ied the design for.