You may not realize it, but structured content is everywhere I look for classification schemes in everything How to create a common vocabulary that everyone can relate to
Recipes have become my go-to classic example of intelligent content at work because recipes are everywhere: blogs and websites, mobile apps like Epicurious, social networks like Pinterest, and in search-engine results.
Structured content definition Unstructured content is trapped in the body field The styling and relationships are static and locked
Let’s fix this
Move your content into a structured format so that it can be shared and distributed to any platform – even ones that haven’t been invented yet
Content types Fields and metadata Data centric, not page centric
Categorize content with fields and tabs we can sort, filter and prioritize it What types of content do you have – audio, video, articles, news, events Figure out what fields and metadata you need for each Make it easier for content creators to enter the information and for the web to reuse the information Writing content for the chunk, not the page – data centric not page centric
Make it easier for content creators to enter the information and for the web to reuse the information Writing content for the chunk, not the page – data centric not page centric
For each concept, there is a content type. What are the attributes or properties of each concept? Unique fields in the database Semantic markup
What limits do we set on the attributes?
Define the content types Work with the content creators to make a common vocabulary
A shared vocabulary makes it easier for webmasters and developers to decide on a schema and get the maximum benefit for their efforts. You can give context to your data and make your Drupal site part of the semantic web. Helps Google understand your markup.
Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model.
Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences.
Schema.org is sponsored by Google, Microsoft, Yahoo and Yandex. The vocabularies are developed by an open community process, using the email@example.com mailing list and through GitHub.
The modern automobile factory is no longer the assembly line that Ford pioneered, but has been effectively reduced to an assembler of finished components.
working “the old way:” crafting custom pieces of UI for every new feature we dreamed up. The CSS was unmanageable, and as much as we tried, things never felt like a true family of components—everything had a slightly different makeup, both visually and in the underlying code.
A unified design system is essential to building better and faster; better because a cohesive experience is more easily understood by our users, and faster because it gives us a common language to work with.
Why is this important? The internet of things Because content is on every device – not just computers, but in our cars, our appliances And will be in places we have yet to consider We need to push content where everyone is
Turn content into data that can be read by humans & machines Reusable chunks across devices, social – content in whatever context makes sense Change content in one place and it updates everywhere Social chunks
Scalable over time
Divorce interface from the content – the interface is a representation of the content – facelift
Content becomes data – robots can make sense of it Your content can be made available through an API
No more blobs
GIVE UP CONTROL!!! goal of achieving true device agnosticism
any markup that is in the content should only be semantic HTML and not in any way make assumptions about delivery (no table driven layouts). Let the CSS in whatever delivery layout wrapper make those decisions at render time
Structured Content Part 2: Why designers should care
Why Designers Should Care
August 17, 2016
Dori Kelner, Managing Partner
Survey data collection
Technical project management
Foodie and oenophile
8/18/2016 | 2
Trapped in the body field
Styling and relationships are
static and locked
8/18/2016 | 4
“Get your content ready to go anywhere because it’s going to go
8/18/2016 | 5
Plan for Structure
1. Content modeling
2. Design systems
8/18/2016 | 6
Fielded content chunks
Consistent semantic markup
Control data feeds
8/18/2016 | 7
Fields Type Widget Size Required
Person Information about
people who interact
with the site
Full name Bio
First name Text Text 20 Yes
Last name Text Text 20 Yes
Headshot Image Image Yes
Summary Text Text 120 Yes
Term Reference -
Select list Yes
Select list Yes
8/18/2016 | 8
8/18/2016 | 9
8/18/2016 | 10
“Schema.org is a collaborative, community activity with a mission to
create, maintain, and promote schemas for structured data on the
Internet, on web pages, in email messages, and beyond.”