Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Doing it for the kids: Tate Online on engaging, entertaining and (stealthily) educating six to 12 year olds Sharna Jackson...
Tate Kids pre (re) launch…
Tate Kids today
Tate Kids had to… <ul><li>appeal to a  diverse audience </li></ul>
Tate Kids had to… <ul><li>appeal to a diverse audience …   while  stealthily educating  them </li></ul>
Tate Kids had to… <ul><li>have a unique but fitting  visual style , with well written copy </li></ul>
Future plans <ul><li>Promotion </li></ul><ul><li>New content </li></ul><ul><li>Extend the brand </li></ul><ul><li>Forge pa...
Tying it all together <ul><li>Integrating game client- & server-sides </li></ul><ul><li>Integrating games with My Gallery ...
Tate Kids Games <ul><li>4 basic interactions: </li></ul><ul><ul><li>create </li></ul></ul><ul><ul><li>save (publish to gam...
Tate Kids Games <ul><li>Tate Paint </li></ul><ul><ul><li>client-side developed externally, in Flash </li></ul></ul><ul><ul...
My Gallery Integration <ul><li>Goals: </li></ul><ul><ul><li>Allow a user to add works created in the games to their galler...
Design Strategy <ul><li>Minimise coupling </li></ul><ul><ul><li>no shared state (databases, files) </li></ul></ul><ul><ul>...
The Protocols <ul><li>My Gallery and the game back-ends provide web services (XML over HTTP) for each other </li></ul><ul>...
A client/server protocol <ul><li>Tate Paint / Street Art </li></ul><ul><ul><li>save (POST, image/jpeg) </li></ul></ul><ul>...
A client/server protocol <ul><li>URL  base of back-end is passed to client via Flash parameter </li></ul><ul><ul><li><para...
Integration Protocol <ul><li>Games are registered with My Gallery using the online admin interface </li></ul><ul><li>The r...
Integration Protocol <ul><li>Game registration includes: </li></ul><ul><ul><li>game homepage URL </li></ul></ul><ul><ul><l...
Integration Protocol <ul><li>My Gallery presents: </li></ul><ul><ul><li>artifact upload (POST) </li></ul></ul><ul><ul><ul>...
Lessons learned <ul><li>Know what scenarios you need to support </li></ul><ul><li>Communicate with all implementors </li><...
Upcoming SlideShare
Loading in …5
×

Sharna Jackson and Rob Adamson, Doing it for the kids: Tate Online on engaging, entertaining and (stealthily) educating six to 12 year olds

2,513 views

Published on

A presentation from Museums and the Web 2009.

Children between the ages of six and 12 are not a homogenous mass. Both ends of the age range have differing needs, abilities and expectations. When designing a Web site for them, it is crucial to appeal not only to all of them, but also to their 'gatekeepers' – their parents and teachers, who tend to manage their time online. Taking the new Tate Kids Web site as a case study (http://kids.tate.org.uk/) , this paper will outline a process of designing a Web site that attempts to meet the needs of the three audiences, while embodying the Tate Kids ethos: smart, fun, irreverent, anarchic content with educational value. It will outline the graphic design process, the strategy for user testing, the importance of differentiating content, and the purpose of an adult zone. It will discuss our efforts to alleviate online safety fears and the use of teachers' notes to support the use of the Web site in the classroom.

A unique aspect of Tate Kids is My Gallery, a carefully managed online community. Here users create profiles, upload their own art, take work from the Tate Kids Collection (a subset of around 500 works from the online collection) and save work they have created in two new games: Tate Paint and Street Art. This paper will discuss how this functionality was created, and how its audiences are receiving it. This paper will also discuss how Tate Kids will be developed in the future and will also look at the possibility of working in partnership with external companies to share audiences.

Session: Young Audiences and Creators [Technology]

Published in: Technology
  • Login to see the comments

Sharna Jackson and Rob Adamson, Doing it for the kids: Tate Online on engaging, entertaining and (stealthily) educating six to 12 year olds

  1. 1. Doing it for the kids: Tate Online on engaging, entertaining and (stealthily) educating six to 12 year olds Sharna Jackson - Tate Kids Editor Rob Adamson - Application Developer
  2. 2. Tate Kids pre (re) launch…
  3. 3. Tate Kids today
  4. 4. Tate Kids had to… <ul><li>appeal to a diverse audience </li></ul>
  5. 5. Tate Kids had to… <ul><li>appeal to a diverse audience … while stealthily educating them </li></ul>
  6. 6. Tate Kids had to… <ul><li>have a unique but fitting visual style , with well written copy </li></ul>
  7. 7. Future plans <ul><li>Promotion </li></ul><ul><li>New content </li></ul><ul><li>Extend the brand </li></ul><ul><li>Forge partnerships </li></ul><ul><li>Win the Webby </li></ul>
  8. 8. Tying it all together <ul><li>Integrating game client- & server-sides </li></ul><ul><li>Integrating games with My Gallery </li></ul>
  9. 9. Tate Kids Games <ul><li>4 basic interactions: </li></ul><ul><ul><li>create </li></ul></ul><ul><ul><li>save (publish to game-specific gallery) </li></ul></ul><ul><ul><li>send to My Gallery </li></ul></ul><ul><ul><li>send to a friend (email) </li></ul></ul><ul><li>Constraints: </li></ul><ul><ul><li>must be able to use without logging in </li></ul></ul><ul><ul><li>content must be approved before being displayed to other users </li></ul></ul>
  10. 10. Tate Kids Games <ul><li>Tate Paint </li></ul><ul><ul><li>client-side developed externally, in Flash </li></ul></ul><ul><ul><li>server-side developed internally, in Java </li></ul></ul><ul><li>Street Art </li></ul><ul><ul><li>client-side developed externally, in Flash </li></ul></ul><ul><ul><li>server-side – re-use of Tate Paint server-side </li></ul></ul><ul><li>Tate Tales </li></ul><ul><ul><li>client & server-side: Wordpress (HTML / PHP) </li></ul></ul>
  11. 11. My Gallery Integration <ul><li>Goals: </li></ul><ul><ul><li>Allow a user to add works created in the games to their gallery </li></ul></ul><ul><ul><li>Respect moderation status of work </li></ul></ul><ul><ul><li>Support a convenient moderation workflow </li></ul></ul><ul><ul><li>Allow for new games </li></ul></ul><ul><ul><li>Allow for evolution of My Gallery </li></ul></ul><ul><ul><li>Flexibility to handle any changes to hosting </li></ul></ul>
  12. 12. Design Strategy <ul><li>Minimise coupling </li></ul><ul><ul><li>no shared state (databases, files) </li></ul></ul><ul><ul><li>use messaging between My Gallery and games </li></ul></ul><ul><li>Whole transaction per request </li></ul><ul><ul><li>simplifies locking and database transaction handling </li></ul></ul><ul><ul><li>simplifies protocol </li></ul></ul><ul><li>“ Parameterise from Above” (Kevlin Henney) </li></ul><ul><ul><li>no hardcoded external references </li></ul></ul><ul><ul><li>configure from outside (“above”) the code </li></ul></ul>
  13. 13. The Protocols <ul><li>My Gallery and the game back-ends provide web services (XML over HTTP) for each other </li></ul><ul><li>Game back-ends provide interface to Flash front-ends </li></ul><ul><ul><li>Flash cannot send files using multipart/encoded! </li></ul></ul><ul><ul><li>So send the file as the content (image/jpeg) and put the data in URL parameters </li></ul></ul><ul><li>Game front-ends only talk to their back-ends, not to My Gallery directly </li></ul>
  14. 14. A client/server protocol <ul><li>Tate Paint / Street Art </li></ul><ul><ul><li>save (POST, image/jpeg) </li></ul></ul><ul><ul><ul><li>parameters: name, title, age, country, galleries </li></ul></ul></ul><ul><ul><ul><li>response: id of the new painting </li></ul></ul></ul><ul><ul><li>send (POST) </li></ul></ul><ul><ul><ul><li>parameters: </li></ul></ul></ul><ul><ul><ul><ul><li>id </li></ul></ul></ul></ul><ul><ul><ul><ul><li>smg = true | false (send to My Gallery) </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>My Gallery username & password </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>stf = true | false (send to friend by email) </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>friend's name, email address, personal message </li></ul></ul></ul></ul></ul><ul><ul><li>GET methods: </li></ul></ul><ul><ul><ul><li>image (jpeg), gallery (xml), painting (xml) </li></ul></ul></ul>
  15. 15. A client/server protocol <ul><li>URL base of back-end is passed to client via Flash parameter </li></ul><ul><ul><li><param name=&quot;flashvars&quot; value=&quot;tateURL=http://kids.tate.org.uk/paint/&quot; /> </li></ul></ul>
  16. 16. Integration Protocol <ul><li>Games are registered with My Gallery using the online admin interface </li></ul><ul><li>The registration record comprises the service URLs </li></ul><ul><li>URLs pertaining to an individual work are specified in a template form </li></ul><ul><ul><li>e.g. http://kids.tate.org.uk/paint/painting/ {artRef} </li></ul></ul>
  17. 17. Integration Protocol <ul><li>Game registration includes: </li></ul><ul><ul><li>game homepage URL </li></ul></ul><ul><ul><li>game icon URL </li></ul></ul><ul><ul><li>work showcase URL </li></ul></ul><ul><ul><li>work data URL (XML) </li></ul></ul><ul><ul><li>approved work list URL (XML of references only) </li></ul></ul><ul><ul><li>approve action URL </li></ul></ul><ul><ul><li>reject action URL </li></ul></ul>
  18. 18. Integration Protocol <ul><li>My Gallery presents: </li></ul><ul><ul><li>artifact upload (POST) </li></ul></ul><ul><ul><ul><li>Parameters: </li></ul></ul></ul><ul><ul><ul><ul><li>username, </li></ul></ul></ul></ul><ul><ul><ul><ul><li>password, </li></ul></ul></ul></ul><ul><ul><ul><ul><li>game reference (as registered with My Gallery) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>unique reference (e.g. painting ID) </li></ul></ul></ul></ul><ul><ul><ul><li>Response </li></ul></ul></ul><ul><ul><ul><ul><li>HTTP response code indicates success or the type of error </li></ul></ul></ul></ul><ul><li>This URL is specified in each game's context or webapp configuration, via JNDI </li></ul>
  19. 19. Lessons learned <ul><li>Know what scenarios you need to support </li></ul><ul><li>Communicate with all implementors </li></ul><ul><li>Find out constraints </li></ul><ul><li>Parameterise </li></ul><ul><ul><li>for configuration and for flexibility </li></ul></ul><ul><ul><li>Don't assume there will only ever be one instance </li></ul></ul><ul><li>Test, Test, TEST! </li></ul><ul><ul><li>make sure you can! </li></ul></ul>

×