VIP Kolkata Call Girl Kestopur 👉 8250192130 Available With Room
Architecting Content for the Unknown Consumer
1. TM
Architecting your
Content for the
Unknown Consumer
19.10.16
Richard Jones, Technical Director
@richardjones @inviqa
Digital Publishing Innovation Summit, London 2016
23. Use of structured data for other purposes
#DigiPub @richardjones @inviqa
24. How do we support these unknown
consumers?
#DigiPub @richardjones @inviqa
25. Many people still think in the
“page” model
Pages may have semantic
elements
At best these are signals for
interpretation
The Web as Pages
#DigiPub @richardjones @inviqa
26. We need a Content Management System
to allow us to move beyond “page”
thinking
Beyond the page
#DigiPub @richardjones @inviqa
27. Content model and structure
Delivery / Access mechanism
Essential ingredients
#DigiPub @richardjones @inviqa
28. Content creators need to think beyond
pages
Relinquish control of layout
Challenging the status quo
Challenges
#DigiPub @richardjones @inviqa
29. A debate well covered elsewhere
aka Battle for the Body Field
A conversation that is still ongoing
Blobs vs Chunks
#DigiPub @richardjones @inviqa
30. Also a well covered topic
Very relevant to our scenarios
The use case for context specific content is
valid here
Adaptive vs Responsive
#DigiPub @richardjones @inviqa
36. Structure the content model
Expose content using a documented API
Steps to Prepare
#DigiPub @richardjones @inviqa
37. Conceptually can start quite simple
Complexity tends to escalate as you work
through the relationships
The Content Model
#DigiPub @richardjones @inviqa
41. Object Oriented Programming
Well understood in the computer science
world
Some principles could be applied to
content modelling
Comparing to OOP
#DigiPub @richardjones @inviqa
42. Objects which may contain data in the
form of fields
Code in the form of methods
Single responsibility principle
Definition
#DigiPub @richardjones @inviqa
43. A content type should be as simple as
possible
It should be for one purpose only
Do not assume dependencies that may not
be present
A field should have one clear purpose
Loose interpretation
#DigiPub @richardjones @inviqa
50. Multiple use cases
Violates the single
responsibility
Reluctance to have
multiple content types
leads to a monster
content type
Godzilla Content Type
#DigiPub @richardjones @inviqa
51. Multiple use cases
Violates the single
responsibility
Reluctance to have
multiple content types
leads to a monster
content type
Godzilla Content Type
#DigiPub @richardjones @inviqa
52. Instead:
Don’t be afraid to have
more smaller content
types
Consider relationships
Think carefully about
single responsibility
Godzilla Content Type
#DigiPub @richardjones @inviqa
54. Using a field name that doesn’t make
immediate sense to the editor
Fields that are used for different things in
difference scenarios
Lead to loss of structure
Field Ambiguity
#DigiPub @richardjones @inviqa
55. Instead: Agree clear naming with all
content stakeholders
Create clear guidelines / help text.
Field Ambiguity
#DigiPub @richardjones @inviqa
64. Spend time on the content model
#DigiPub @richardjones @inviqa
65. Allow more time than you think you need
Focus on the future - and abstract
Simplify the design - leave no room for
interpretation
Consistency of fields - eg date formats
Content Model
#DigiPub @richardjones @inviqa
66. Think through all possible relationships
Break content into the smallest possible
pieces
Hold the smallest amount of formatting
possible
Content Model
#DigiPub @richardjones @inviqa