Upload
richard-jones
View
396
Download
2
Embed Size (px)
Citation preview
TM
Architecting your Content for the Unknown Consumer
19.10.16
Richard Jones, Technical Director@richardjones @inviqaDigital Publishing Innovation Summit, London 2016
You need to keep pace with requirements you may not
even be aware of
TM
#DigiPub @richardjones @inviqa
Being PreparedWhy today’s web is unpredictable What’s likely to change How you can be ready now
#DigiPub @richardjones @inviqa
Beyond the headlinesEnvironmental monitoring Infrastructure management Manufacturing Energy Management Medical and Healthcare
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
We need a Content Management System to allow us to move beyond “page” thinking
Beyond the page
#DigiPub @richardjones @inviqa
Content model and structure Delivery / Access mechanism
Essential ingredients
#DigiPub @richardjones @inviqa
Content creators need to think beyond pages Relinquish control of layout Challenging the status quo
Challenges
#DigiPub @richardjones @inviqa
A debate well covered elsewhere aka Battle for the Body Field A conversation that is still ongoing
Blobs vs Chunks
#DigiPub @richardjones @inviqa
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
Structure the content model Expose content using a documented API
Steps to Prepare
#DigiPub @richardjones @inviqa
Conceptually can start quite simple Complexity tends to escalate as you work through the relationships
The Content Model
#DigiPub @richardjones @inviqa
Object Oriented Programming Well understood in the computer science world Some principles could be applied to content modelling
Comparing to OOP
#DigiPub @richardjones @inviqa
Objects which may contain data in the form of fields Code in the form of methods Single responsibility principle
Definition
#DigiPub @richardjones @inviqa
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
Content types that provide nothing in isolation “Signposts”, “Jumps”, “Shortcuts”
Non-Content Content
#DigiPub @richardjones @inviqa
Instead use alternative views of the referenced content: e.g. Teasers, List view
Non-Content Content
#DigiPub @richardjones @inviqa
Content Antipattern #2 Godzilla Content Type
#DigiPub @richardjones @inviqa
Content Antipattern #2 Godzilla Content Type
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
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
Instead: Don’t be afraid to have more smaller content types Consider relationships Think carefully about single responsibility
Godzilla Content Type
#DigiPub @richardjones @inviqa
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
Instead: Agree clear naming with all content stakeholders Create clear guidelines / help text.
Field Ambiguity
#DigiPub @richardjones @inviqa
Fields that are not really content Designed to affect the layout of the “page” via template logic
Logic Fields
#DigiPub @richardjones @inviqa
Don’t mix layout with content The application theme layer can handle this for you.
Logic Fields
#DigiPub @richardjones @inviqa
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
Think through all possible relationships Break content into the smallest possible pieces Hold the smallest amount of formatting possible
Content Model
#DigiPub @richardjones @inviqa