Employing a Collaborative Model for Structured Content
•Télécharger en tant que PPTX, PDF•
1 j'aime•234 vues
Web projects don't begin with visual design, they start with modeling the content. This presentation focuses on the roles that the content strategist, content creator, designer and developer play in building the content model, and discusses why the team should care about this aspect of the project.
Recommandé
Recommandé
Contenu connexe
Similaire à Employing a Collaborative Model for Structured Content
Similaire à Employing a Collaborative Model for Structured Content (20)
Plus de Dori Kelner
Dernier
Dernier (20)
Employing a Collaborative Model for Structured Content
- 1. Employing a Collaborative Model for Structured Content September 22, 2016 Dori Kelner, Managing Partner Sleight-of-Hand Studios
- 2. About me Survey data collection Data warehousing Technical project management Strategist Foodie and oenophile 9/29/2016 | 2
- 3. Unstructured Content Trapped in the body field Styling and relationships are static and locked No opportunity for meta tags 9/29/2016 | 3
- 4. Structured Content Structured content is information or content that is organized in a predictable way and is usually classified with metadata. 9/29/2016 | 4 WEB SITE INTRA NET PRINT EMAIL SOCIAL APPS BLOGS MICRO SITES STRUCTURED CONTENT
- 5. Why care? 9/29/2016 | 5 Reusability Scalable Multi channel Future proofing Device agnostic Content becomes data
- 6. “Get your content ready to go anywhere because it’s going to go everywhere.” —Brad Frost 9/29/2016 | 6
- 7. Project Roles Content Strategist Content Creator Designer Developer 9/29/2016 | 7
- 8. Content Strategist How do we organize the content so content creators can store and retrieve it? How do we structure the content for consistency and reusability? How do we future proof our content? 9/29/2016 | 8
- 9. Content Creator How do I create content that represents my organization? How do I optimize the time to manage the content? Can’t you make it easier for me to publish my content? 9/29/2016 | 9
- 10. Designer How am I going to build a good UX? What is available to me to create the UI? What design systems will I employ? 9/29/2016 | 10
- 11. Developer How do I move the design into the theme? What are the relationships in the database? How will the content be used across platforms? 9/29/2016 | 11
- 13. Domain Model Create a shared language Decide how the content fits the audience and business goals Define concepts and relationships 9/29/2016 | 13 Ingredient s Process Contributor s Stores
- 14. Content Model Fielded content chunks Consistent semantic markup Visual hierarchy/importance Control data feeds Apply metatags 9/29/2016 | 14
- 15. 9/29/2016 | 15 RECIPE Title Subtitle Short summary Summary Person Image Video Ingredients Process Nutritional info Yield Cook time Prep time Category Rating Comments Content priority PROCESS Steps CATEGORY Title INGREDIENT Measure Quantity Name PERSON Full Name First name Last name Summary Bio Role Affiliation ROLE Title REVIEW Rating Comment STORE Name Address City State Ingredient AFFILIATIO N Title
- 16. Content Types 9/29/2016 | 16 RECIPE PROCESS INGREDIENT PERSON
- 17. Name Description Title Field Body Field Fields Type Widget Required Person Information about people who interact with the site Full name About First name Text Text Yes Last name Text Text Yes About Text Long text Yes Role Term Reference - role Select list Yes Affiliation Entity Reference - workplace Select list Yes 9/29/2016 | 17
- 18. 9/29/2016 | 18 Content: Person Content List (entity reference): Affiliation Term reference: Role
- 19. Meta tags 9/29/2016 | 19 Snippets of text that describe a page's content
- 20. schema.org 9/29/2016 | 20 “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.”
- 21. 9/29/2016 | 21
- 22. 9/29/2016 | 22
- 23. 9/29/2016 | 23
- 24. Separate Content from Presentation True device agnosticism Do you know where your content is? 9/29/2016 | 24
- 25. 9/29/2016 | 25 Dori Kelner, MS Managing Partner Sleight-of-Hand Studios 703-758-7178 dmkelner@sohstudios.com Twitter: @dorikelner LinkedIn: https://www.linkedin.com/in/dorikelner
Notes de l'éditeur
- Data girl
- Why is this important? 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 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
- 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
- Now design, development and content creation can run in parallel Wireframes or prototypes Everyone working together Everyone can bring something to the table What is missing? What needs to be adjusted? Test early with real content
- Step 1: Model the domain Create a shared language and make sense of the subject matter Define the meaning through concepts and relationships Think about audience and business goals The design process begins by deciding how the content fits together Not by creating interfaces Or building functionality We need to build a shared language before the interface Each interface then is like looking at the content through a different lens
- 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
- Define the content types Work with the content creators to make a common vocabulary
- Need to work with content creators Flexibility vs consistency Define taxonomy and other data sources here
- 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 public-schemaorg@w3.org mailing list and through GitHub.
- 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 Semantic Aesthetic