A List Apart

Issue № 349

Savor the content strategy sweetness. Dip into a double dose of Lovinger.

Tinker, Tailor, Content Strategist

by Rachel Lovinger5 Comments

What does content strategy mastery look like? As in any field, it comes down to having master skills and knowing when to apply them. While there are different styles of content strategy (from an editorial and messaging focus to a technical and structural focus), the master content strategist must work with content from all angles: messaging architecture and messaging platforms; content missions and content management. Above all, she must advocate for multiple constituents, including end users, business users, stakeholders, and the content vision itself. Rachel Lovinger shares the skills that go into achieving CS mastery.

Content Modelling: A Master Skill

by Rachel Lovinger11 Comments

The content model is one of the most important content strategy tools at your disposal. It allows you to represent content in a way that translates the intention, stakeholder needs, and functional requirements from the user experience design into something that can be built by developers implementing a CMS. A good content model helps ensure that your content vision will become a reality. Lovinger explains how to craft a strong content model and use it to foster communication and align efforts between the UX design, editorial, and technical team members on your project.

More from A List Apart

Columnists

Rachel Andrew on the Business of Web Dev

You Can’t Do Everything

In any given day I can find myself reading up on a new W3C proposal, fixing an issue with our tax return, coding an add-on for our product, writing a conference presentation, building a server, creating a video tutorial, and doing front end development for one of our sites. Without clients dictating my workload I’m in the enviable position of being able to choose where to focus my efforts. However, I can’t physically do everything.

From the Blog

Paul Irish on Chrome Moving to Blink

The dust has begun to settle after Google’s announcement that Chrome would soon be using their own divergent fork of WebKit as a rendering engine. Now that things have calmed down a bit, I’ve asked Paul Irish to share some of the Chrome team’s plans for the near future.