Thursday 27th February, 2014
10:45am to 11:30am
Content management uses technology to support the processes that people use to produce, manage and deliver content. However, this is seldom done efficiently and suffers from frustratingly low levels of productivity in the processes and employees that end up the managing content. Why? Fundamentally, we don't spend enough time designing the solutions that enable content to get everywhere it needs to be. There are two parts to this problem. First, we need content strategy to raise, scope and socialise the "why" challenges. Second, we must design the "what" of content before we attempt to manage it. This session is focuses upon the design problem.
Customers have stopped asking for websites. They want content platforms to deploy and scale multi-everything properties across their entire digital landscapes. Today's content brief is broader and deeper.
In this session we talk specifically about content architecture. Establishing architectures in which content flows freely, accessible to all, adapting to change requires discipline, planning, collaboration and commitment across the business, UX and technology. After building and supporting a number of digital content platforms for major brands, this session walks through a set of design principles learnt succeeding and failing when designing for content. How do you tie analytics to content? When does it makes sense to invest in a content API? How and what do you need to best approach responsive design? When does content modelling help or hinder the process of designing structured content? Which types of content (assets/structured/unstructured/data) should we focus on? Why wouldn't you store content in the CMS?
Use this session to learn and ask questions on how to use content architecture to inform and be informed by both content strategy and technical implementations of content managed solutions.
Sign in to add slides, notes or videos to this session