It’s time to get strategic and organized with the latest release. These chapters dive into developing a strategy for your content and creating a system for keeping it organized.
I’m Corey Vilhauer.
I’m a user experience strategist at Blend Interactive, a small shop in the heart of the Midwest, where I specialize in content strategy, information architecture, and editor/end user quality assurance.
Where last month we talked about knowing our people and their motivations, this month our planned chapter releases are focused on knowing your content and its connections to your users. That’s right, it’s time to talk content inventories and analytics.
Blend likes to begin all of our web projects – especially those that include strategy, design, or technical planning – with our “Audiences and Outcomes” workshop, which is simply an audience and expectation-focused discovery workshop that nails down the who and what of a site. This month’s chapter release focuses on those two directions: your audiences, and your outcomes/expectations.
Two more chapters are going up, and this time we focus on better understanding who your web team is – who is going to help make these decisions for the larger project – and what that plan will look like as your ideas take shape.
The Web Project Guide is here! To start, read our Introduction. From there, you can check out the first two chapters, which are dedicated to those very early and formative stages at the start of a web project.
Things will be a little slow on Eating Elephant over the next few months, as we (Deane and I) are embarking on a new writing project: The Web Project Guide.
I was a guest on the Design By Committee podcast with Matt Grocki and Justin Davis, where we talked about editorial accessibility, content modeling for content management systems, and picklebacks.
Post 6 of 6 on editorial accessibility: in which we give you some parting words on how everything is okay and you will do great.
Post 5 of 6 on editorial accessibility: in which we go into headings and links — both the writing part and the structure part.
Post 4 of 6 on editorial accessibility: in which we discuss plain language, readability, writing as design, and an attempt at an HTML table.