Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723

Warning: Cannot modify header information - headers already sent by (output started at /webroot/b/e/benedi1/primary/www/wp-content/themes/bloghill/inc/sections/project.php:211) in /webroot/b/e/benedi1/primary/www/wp-includes/rest-api/class-wp-rest-server.php on line 1723
{"id":12,"date":"2014-09-20T20:27:00","date_gmt":"2014-09-20T20:27:00","guid":{"rendered":"http:\/\/www.benedictireland.com\/?p=12"},"modified":"2014-09-20T20:27:00","modified_gmt":"2014-09-20T20:27:00","slug":"designing-for-content-and-data","status":"publish","type":"post","link":"http:\/\/www.benedictireland.com\/?p=12","title":{"rendered":"Designing for content and data"},"content":{"rendered":"

Ultimately, everything we design is there to consume content. Whether\u00a0that’s images, text, video, or whatever, they are (almost) all containers. When designing for responsive sites, this is even more true. The modules\/components will scale and in many cases the content within them will too. A lot of the work we are doing at Splendid these days is responsive, and it’s surprising how many designers don’t really understand the importance of the pattern in this type of project.<\/p>\n

My first exposure to patterns was back in 2003, when the company I was working for were working on design patterns for Visa. The discipline was considered relatively new at the time, at least from a digital context. Obviously lately there’s been a resurgence, as designers begin to understand how to use patterns, and more importantly how to make them scalable.<\/p>\n

An article popped up on my Twitter feed the other day, which is actually a pretty decent set of considerations. I shared it round the office, and will hopefully get roux to seeing if anyone actually read it! Here’s the link:<\/p>\n

Hot Data and Content Design Patterns for Mobile<\/a><\/p><\/blockquote>\n