11. Why content does come
first
1. Business
Data and information comes first because
it’s arguably the most important thing to a
business online.
2. Sitecore
Data and information structure should also
be one of the start points when
implementing a Sitecore site…
fusionworkshop.co.uk
12. What is content?
con·tent [kon-tent]
Something that is contained: the contents of a box (website).
Something that is to be expressed through some medium, as
speech, writing.
Substantive information or creative material viewed in
contrast to its actual or potential manner of presentation…
http://dictionary.reference.com/browse/content - 22/10/2012
fusionworkshop.co.uk
13. Content is derived
“ …a single piece of web
content will probably be made
up from a number of data
items, commonly including
text, images and metadata
from any number of sources.
”
fusionworkshop.co.uk
15. Considerations
“ Think about the sites
users, the CMS user, the
business’ need for return on
investment, and the
technologies capabilities
and limitations.
”
fusionworkshop.co.uk
16. Sitecore best practice
“ When defining
requirements, focus on
information architecture, which
includes data template and
standard values definitions
including workflow, layout
details, and insert options, the
content tree, and other relations
between items.
John West CTO Sitecore
”
& author of “Professional Sitecore Development”
http://sitecorejohn.wordpress.com/
fusionworkshop.co.uk
17. Principles to aid with the creation and
understanding of IA
Choices
Objects
Entry points
Focused navigation
Evolution
Top down – bottom up
D. Brown EightShapes 2010
fusionworkshop.co.uk
18. Artefacts to aid the creation of IA
Online business goals and objectives
Online brand guidelines
Representative content
Content audit/inventory
Personas
Personalisation, engagement plans
UI style guidelines, wireframes and prototypes
SEO recommendations
Social strategy
Accessibility audit, usability findings
fusionworkshop.co.uk
19. Give content focus
Business goal
what does this do for the business?
Objective
what is the operational purpose?
Communication goal
how should we deliver to the customer?
Defining KPI’s will ensure contents
effectiveness can be measured and refined.
fusionworkshop.co.uk
24. Putting it all together
IA in the context of Sitecore is a process that leads to
object and template definition.
Ensure user ambitions and business goals can be met.
Use Sitecore field types based on content
requirements, you are building the editors UI.
Sitecore is a customer engagement platform (CEP)
unless your content is structured correctly DMS will
simply not work.
Content tied to layout can not be repurposed (the be’s).
fusionworkshop.co.uk
25. IA resources
“Professional Sitecore Development” by John
West, chapter 2
Data Definition Reference and Data Definition
Cookbook
http://sdn.sitecore.net/upload/sitecore6/data_definition_reference_sc61_usletter.pdf
http://sdn.sitecore.net/upload/sitecore6/datadefinitioncookbook-a4.pdf
Reusing and Sharing Data
http://sdn.sitecore.net/upload/sitecore6/64/reusing_and_sharing_data-a4.pdf
Continue the conversation … Sitecore user group
fusionworkshop.co.uk
26. Summary
The way data is stored, it’s structure, its
relationships and governance should
support it and allow it to become focused
content no matter how or where its
surfaced, who is viewing it and why.
Release the content …
fusionworkshop.co.uk
27. Why content comes first
justin.rowe@fusionworkshop.co.uk
fusionworkshop.co.uk
Editor's Notes
Aim of this presentationShow how to remain focused on business requirements.Pointers for implementing an information structure into Sitecore.
Search for “what is web content?”get 2 sets of answers;90% will be lists of the types of page commonly found on websites – news, home page, testimonials, reviews, FAQs etcRemainder will simply be 2 things - text and multimediaText and multimedia is the level we need to work at, pages are not granular enough to get the best from an object based CMS such as Sitecore
Maintain a balanced approach.Find out everything you can about the business and their customer base.Understand the strengths and limitations of the proposed technology.What other data stores will be integrated with, CRM, PMS and eCom … how is the data stored.Collect as much representative content, data and information about the proposed site as possible.Break it down, group it, categorise it and then re-build.Above all consistency is key.
Defining requirements is part of initiation, requirement gathering, grooming user stories…In initiation not build.
Choices People make choices, people have limited capabilities. Limit the number of options so as not to overwhelm, offer choice in depth, use progressive disclosure.ObjectsTreat data as an entity, it has attributes and relationships, it grows with age.Entry pointsWe don’t know how people will find our content ensure it can be viewed in context, provide spatial awareness and depth.Focused navigationNavigation should be simple and should have singular purpose. Navigation items should be grouped in the same manner.EvolutionAnticipate growth; be aware of change and shift of focus and priorities. Don’t focus to tightly. Top down bottom up (or both)Support both a hierarchical navigation structure and search through the use of intelligent categorisation (personalisation).
Personas should contain user stories for that user types top level tasks.Prototype where possible in Sitecore to save effort.Content inventory Page ID, Name and URLBusiness goal, Objective and Communication goalAudienceCategorisationLanguageDocument type, file typeAuthenticationOwner maintainerDepartmentExpiry dateRedundant outdated or trivial (ROT)