Working with content structure — an overview with GDS
Slide 2
Rik Williams Senior Content Strategist Government Digital Service (GDS) @Rik_Williams
Slide 3
I’m a new Content Strategist (back-end) at GOV.UK
GDS
Slide 4
Core takeaway
Slide 5
“Perhaps because polish is so visible […] many people erroneously believe it to be the most important part of writing. But polish is merely the plaster on the walls of structure.” Jack Hart
GDS
Lead Image Place name Structural design (channel agnostic)
Rating score Place type Call to Action GDS
Slide 15
Session structure
Slide 16
Part A — talk Structured content — recap Content structuring — primer
GDS
Slide 17
Part B — mini workshops Pieces — deconstructing Atlas Obscura Reuse — remixing pieces of structure Going deeper — complexity hidden in C2As
GDS
Slide 18
Part A — talk
Slide 19
Part A — talk Structured content — recap Content structuring — primer
GDS
Slide 20
“Content that is divided into the smallest reasonable pieces and explicitly organised and classified in order to be understood and used by computers and humans.” Mike Atherton
GDS
Slide 21
“Structuring content within a well-defined content model makes content scalable, reusable, adaptable, and measurable.” Maxwell Hoffman
GDS
Slide 22
“In a nutshell, structured content matters because you can get so much more out of your content with a lot less work — and get better analytics for tracking effectiveness.” Rahel Bailie
GDS
Slide 23
“Well defined leads to well designed” Lindsay Sutton
GDS
Slide 24
Source: Sophia Prater
Slide 25
“People don’t care about the containers, they care about the things they contain.” Carrie Hane
GDS
…content extracted from a mainstream guide and presented in a ‘People also ask’ featured snippet GDS
Slide 34
Goals: 📰 🔍 ♼
Content structured for syndication
GDS
Slide 35
Source: Sakib Supple, The Guardian
Slide 36
“Reuse: The practice of using existing content components to develop new documents.” Ann Rockley
GDS
Slide 37
Goals: ♼
Content structured for localisation
GDS
Slide 38
GDS
Slide 39
Part A — talk Structured content — recap Content structuring — primer
GDS
Slide 40
“A content model breaks content […] down into its component parts, describes them in detail, and maps out how they relate to one another.” Lauren Pope
GDS
Slide 41
“Content models* enable us to store, process and publish content as granular units instead of whole documents.” Cleve Gibbon
*+ maps (and other documentation) GDS
Slide 42
Source: Michael Andrews, Story Needle
Slide 43
Content Model
The available pieces of content and metadata and their relationships to each other.
GDS
Slide 44
Content Type
The required pieces of content and metadata assembled to meet a goal.
GDS
Slide 45
Source: Brent Heslop, ContentStack
Slide 46
Source: Brent Heslop, ContentStack
Slide 47
Source: Brent Heslop, ContentStack
Slide 48
Slide 49
Slide 50
Slide 51
Source: Sophia Prater
Slide 52
Content-first (or bottom-up) design means…
GDS
Slide 53
Thinking of the system, then the detail.
GDS
Slide 54
Alignment with authentic mental models.
GDS
Slide 55
Making the right thing the first time.
GDS
Slide 56
Inclusive/accessible via consistent and predictable wayfinding across content.
GDS
User Researcher-friendly — synthesising research insights into structure will expose high-risk assumptions/questions early.
GDS
Slide 61
Source: Sophia Prater
Slide 62
Content Designer-friendly — gives early engagement and enables visibility to the types and scale of content that might need creating and governing.
GDS
Slide 63
Content Strategist-friendly — breaking data into its fundamental components helps sensemaking by wrangling complexity into understanding.
GDS
Slide 64
Interaction Designer-friendly — provides the pieces they have to work with and a methodology for identifying things that will need patterns in any design system.
GDS
Slide 65
Stakeholder-friendly — mapping and modelling content creates opportunities for subject matter experts to contribute from the outset and at their level of expertise.
GDS
Slide 66
“…pieces…” 🧐🤔
GDS
Slide 67
Things The fundamental units of content in the users mental model of the domain.
GDS
Slide 68
“A content model should honour and respect the users mental model.”
GDS
Slide 69
Slide 70
Relationships
How the Things relate to each other.
GDS
Slide 71
Calls-To-Action The affordances that the content Things offer users on the front and the back-end.
GDS
Slide 72
Attributes The specific pieces of core content and metadata that build instances of content Things.
GDS
Slide 73
Slide 74
Slide 75
Recipe
Name
Stars
Rate
Chef
Image
Reviews
Save
Show
Lede
Size
Print
Ingred.
Quant.
Time(s)
Share Add GDS
Slide 76
Part B — mini workshops
Slide 77
Part B — mini workshops Pieces — deconstructing Atlas Obscura Reuse — remixing pieces of structure Going deeper — complexity hidden in C2As
GDS
Slide 78
Reverse engineer an Instance of a Place from Atlas Obscura, a digital magazine and travel company.
GDS
Slide 79
Working individually, find as many pieces of content structure as you can.
GDS
Slide 80
Slide 81
Things Core Content Metadata Calls-to-Action
GDS
Slide 82
Slide 83
bit.ly/dwp-mural GDS
Slide 84
bit.ly/dwp-ao GDS
Slide 85
7 mins GDS
Slide 86
Slide 87
Place
Name
Status
Edit
Contrib.
Lede
LatLong
Add Img
Trip
Images
Counter
See All
Story
Caption
Topics
Add List
Course
Body
Country
View Map GDS
Slide 88
Part B — mini workshops Pieces — deconstructing Atlas Obscura Reuse — remixing pieces of structure Going deeper — complexity hidden in C2As
GDS
Slide 89
Reuse, remix and reassemble Attributes for contextual navigation in a digital interface.
GDS
Slide 90
Select and prioritise a handful of Attributes for use in a ‘card’ interface component in Atlas Obscura.
GDS
Slide 91
A schematic of a card component in Google’s Material design system.
GDS
Slide 92
Slide 93
Slide 94
Slide 95
7 mins GDS
Slide 96
Slide 97
Slide 98
Part B — mini workshops Pieces — deconstructing Atlas Obscura Reuse — remixing pieces of structure Going deeper — complexity hidden in C2As
GDS
Slide 99
C2A in a prototype
…but what happens next? 🧐🤔 Often overlooked structure, mechanics etc.
Slide 100
Atlas Obscura relies on Contributors (users worldwide) to create and add photos for Places they visit.
GDS
Slide 101
This is (mainly) so that thousands of Places in the system can have 1-many photos of them. But how does this happen?
GDS
Slide 102
Slide 103
Slide 104
Slide 105
Slide 106
7 mins GDS
Slide 107
User
Photo
Source
Upload
Caption
Add +1
Alt text
Submit
Help text
Cancel
GDS
Slide 108
Admin
Photo
Source
Confirm
Caption
Reject
Alt text
2i (??)
GDS
Slide 109
Summary
Slide 110
Adapted from: Factor Firm
Slide 111
Slide 112
“Well defined leads to well designed” Lindsay Sutton
GDS