Pagebuilder manages your web pages but it comes with its drawbacks. A clunky interface and technical jargon obscures a lot of the necessary features editors need to manage their pages.
In an effort to make Pagebuilder’s features more accessible, our team redesigned the UI. We achieved this by parsing editorial workflows and prioritizing the most relevant tasks.
Research & Journey Mapping
We started with interviewing editors and engineering teams about how they managed their pages. From documenting their workflows we found one major pattern: people lost a lot of time jumping between tools.
Wireflows
Our next challenge was figuring out how to minimize additional steps without impeding editors' day-to-day flow. We looked to other content creation tools that organized configurations by roles. We came up with the idea to organize the interface into ‘workspaces’. This allowed people to quickly get to the configurations that mattered the most to them.
Wireframes
'Workspaces' contextualized the many features and tools that Pagebuilder provided. The 'curation workspace' became the designated place where editors could manage the positioning of stories on their pages.
Final Product
The overall goal was to make better use of Pagebuilder’s features by making the interface more accessible to editors and developers as well. Open the prototype and walk through the experience of updating a story on The Washington Post homepage.
.svg)
.png)
.svg)
.svg)
