Content Design, UI Architecture and Content-UI-Mapping

When you want to gather, manage and publish content and display it independently on any user interface and/or target channel you need a system that supports “Content Design and Content UI Mapping”. Content and user interfaces can be planned and assembled modularly and structured in a similar manner — comparable to bricks in a building block system. Content basically runs through three steps until it reaches its recipient: Gathering, management and output. A mapping has to occure at the intersections of these three steps.

This is the extended slides version on the topic.

There's also an article on the topic: https://medium.com/@wolframnagel/content-design-and-ui-mapping-a35af8cac3f6#.3ylkxrakf

15.
channel-independent and
consistent content
1) Central hub for content
2) Central system for definition of UI elements
3) APIs
4) Workflows and rules
Requirements for content that can be published consistently in various channels.

105.
Thought:
That in the future information can be coherently
outputted on any imaginable channel, you must also
consider the Internet of Things and all other shapes of
interfaces when thinking about UI libraries, styleguides,
content models and mapping.

106.
Thought:
That in the future information can be coherently
outputted on any imaginable channel, you must also
consider the tbd and all other shapes of
interfaces when thinking about UI styleguides, content
models and mapping.