Top Banner
Content Strategy for Developers
61

IPC 2016: Content Strategy for Developers

Jan 21, 2017

Download

Technology

Robert Lemke
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: IPC 2016: Content Strategy for Developers

Content Strategyfor Developers

Page 2: IPC 2016: Content Strategy for Developers

Robert Lemke

CEO FlownativeProject Founder [email protected]@robertlemke

Page 3: IPC 2016: Content Strategy for Developers
Page 4: IPC 2016: Content Strategy for Developers
Page 5: IPC 2016: Content Strategy for Developers
Page 6: IPC 2016: Content Strategy for Developers

“Content strategy is […]a repeatable system that governs t he management of content throughout the entire content lifecycle.

Rahel Anne BailieIntentionalDesign Inc.

Page 7: IPC 2016: Content Strategy for Developers

“Getting the right content to the right user at the right time through strategic planning of content creation, delivery, and governance.

Steven Grindlay et al.Content Strategy Alliance

Page 8: IPC 2016: Content Strategy for Developers

“Okay, content is important, sure, but we really have to get that website done now.

Joseph M. ManagerYour Average Web Agency Inc.

Page 9: IPC 2016: Content Strategy for Developers

just take the content from the old

website for now!

Page 10: IPC 2016: Content Strategy for Developers

HOW DID THAT

LOREM IPSUM END UP

ON THE LIVE SITE ?!!

Page 11: IPC 2016: Content Strategy for Developers

Let’s take a look at a little bit of this and that.

Content strategy is a broad topic.

Page 12: IPC 2016: Content Strategy for Developers

1. plan 2. assess 3. analyze 4. design 5. maintain

Page 13: IPC 2016: Content Strategy for Developers

1Purpose

Page 14: IPC 2016: Content Strategy for Developers

What are we creating this website for?** who eventually pays the bill?

Page 15: IPC 2016: Content Strategy for Developers

just take the content from the old

website for now!

Page 16: IPC 2016: Content Strategy for Developers

User-centric design means that the product must satisfy real human needs.

Content is King*

Page 17: IPC 2016: Content Strategy for Developers

Make sure that everyone in the team knows the purpose.

Page 18: IPC 2016: Content Strategy for Developers

“Our mission: Make everything hyper great.

Page 19: IPC 2016: Content Strategy for Developers
Page 20: IPC 2016: Content Strategy for Developers

Sell our products.

> vague and meaningless

Page 21: IPC 2016: Content Strategy for Developers

Sell this one cool product.

> too big> too many steps

Page 22: IPC 2016: Content Strategy for Developers

List and explain advantages of this one cool product.> maybe achievable> but lacking target audience

Page 23: IPC 2016: Content Strategy for Developers

Show how this one cool product can help young physicians.> you know your audience > content can be very specific

Page 24: IPC 2016: Content Strategy for Developers

A website without meaningful contentis not worth your code.

Page 25: IPC 2016: Content Strategy for Developers

2Structure

Page 26: IPC 2016: Content Strategy for Developers

Many websitesare no better than PDFs convertedto HTML.

Page 27: IPC 2016: Content Strategy for Developers
Page 28: IPC 2016: Content Strategy for Developers

WEB PAGES!😱

Page 29: IPC 2016: Content Strategy for Developers
Page 30: IPC 2016: Content Strategy for Developers

What’s so bad about unstructuredcontent?

Page 31: IPC 2016: Content Strategy for Developers

Robots don’t understand unstructured content.

Page 32: IPC 2016: Content Strategy for Developers

If robots can’t understand your content they can’t help you orchestrating it.

Page 33: IPC 2016: Content Strategy for Developers

Screenshot: Karen Mc Grane

Page 34: IPC 2016: Content Strategy for Developers
Page 35: IPC 2016: Content Strategy for Developers
Page 36: IPC 2016: Content Strategy for Developers
Page 37: IPC 2016: Content Strategy for Developers
Page 38: IPC 2016: Content Strategy for Developers
Page 39: IPC 2016: Content Strategy for Developers

Don’t write for justone channel

Page 40: IPC 2016: Content Strategy for Developers

Don’t write for justone channel *

* okay, got ya, we’ll create a website for mobile, too

Page 41: IPC 2016: Content Strategy for Developers

RWD FTW!

Page 42: IPC 2016: Content Strategy for Developers

Content needs to be adaptive.

Page 43: IPC 2016: Content Strategy for Developers

Start creatingcontent models.

Page 44: IPC 2016: Content Strategy for Developers

Create project-specific content types.Neos allows you to do that just with configuration,no programming required.

ContentTypes

Page 45: IPC 2016: Content Strategy for Developers

Twitter teaser?Apple Watch headline?

If you create channel-specific content types,you’re probably doing it wrong.

Page 46: IPC 2016: Content Strategy for Developers

Twitter teaser?Apple Watch headline?

Short teaser. Medium teaser. Super short abstract.

Page 47: IPC 2016: Content Strategy for Developers

Separation of content and presentation.This time for real.

Page 48: IPC 2016: Content Strategy for Developers

Add metadata!

[x] show on front page[x] hide in iOS app

[x] breaking news[x] top story

Page 49: IPC 2016: Content Strategy for Developers
Page 50: IPC 2016: Content Strategy for Developers
Page 51: IPC 2016: Content Strategy for Developers

Automate content orchestration.

Page 52: IPC 2016: Content Strategy for Developers

3Quality

Page 53: IPC 2016: Content Strategy for Developers
Page 54: IPC 2016: Content Strategy for Developers
Page 55: IPC 2016: Content Strategy for Developers
Page 56: IPC 2016: Content Strategy for Developers
Page 57: IPC 2016: Content Strategy for Developers
Page 58: IPC 2016: Content Strategy for Developers
Page 59: IPC 2016: Content Strategy for Developers

Make content thecentral aspect of your website project.

Invest intoplanning, analysis& design.

Page 60: IPC 2016: Content Strategy for Developers
Page 61: IPC 2016: Content Strategy for Developers

[email protected] www.flownative.com

@robertlemke

your thoughts?