 Okay, so welcome to today's presentation on device agnostic content strategies for display. So, I tried to make the name of the presentation really pretentious, like not just a mobile content strategy, but device agnostic. But who knows what kind of devices will be designing content for in the near future. And so I hope you're all in the right place. Content strategy, are there people in the room who are content strategists? To you people? Just a couple hands. Maybe by the end of this presentation we'll see all of them. So if you're not a content strategist, then to you. Are you a site builder? Are you a site builder? By a group of site builders? To your hands. Who here is like a major content type or a new group of... Okay, so you're all site builders. And you can hear like a really valid part like back end folks. Like front end folks, like stand-up, HTML, maybe some project managers. So in fact, even if you're not really like considering yourself a content strategist, you might actually be a content strategist. Or maybe you should be. So in this presentation I'll be kind of sketching on that and trying to bring everyone into the pool of content strategy to the mind of people. Just as an introduction before I start, my name is Xander Khilpat. I work at Evolving Web for a people shop based in Montreal, just down the road. And I do a lot of Drupal training. I also have experience doing CME and module development and site building. So I've done a lot of Drupal things over the years. And if you want to follow me because you want to know my thoughts on Drupal type things, you can follow me on Twitter at Suzanne and just work with me. We work for lots of different types of clients. Got a couple more slides here. We have some training coming up. Sorry for the promo pitch before the presentation. But if you are interested in training on Drupal, we've got some training coming up actually in Ottawa in September. So feel free to come to me afterwards about that. Or I've got some handouts at the back if you can pick up if you want more info. Okay, so let's dive right in. So I always saw a few hands of people saying they were content strategists. So that probably begs the question, what is content strategy anyway? So when I think of content strategy, I often think about story telling. So if you're looking at a website, not just necessarily publishing the content that you happen to have, that you think needs to go online, but actually making that content into something that's a bit more compelling. So connecting users to the content and making it engaging for them. So sometimes that means changing the structure of the content, changing how it's laid out, changing the architecture, like the types of content that we actually create can mean all sorts of things. So story telling is like a really nice friendly word like, oh yeah, I really love story telling. But from a more business perspective, of course there's also often a marketing intent behind content. So on the one hand you want to make content engaging for the users because the users are happy in their status side with the content and they want to stay on their site and read or look at what you have to present. And then from a marketing perspective, you also want to achieve some business goals. Like maybe you want somebody to see a piece of content so that they'll go and buy something or they'll contact you or there's some kind of call to action there that you want to replace. And then at the same time, sometimes your organization might just have a mandate to make content available. So especially when we're thinking of like government websites or public organizations, a lot of time the content just has to be there maybe even from a legal perspective. So making that content available and accessible to people so that they can find it easily, that's quite a content strategy too. So it's really like a meeting point between users and business goals. That's where we find good content strategy. So that's content strategy in general. And then when we're talking about content strategy across devices like for mobile or for desktop or for any kind of device in between or thinking out of the box like other kinds of future devices you might want to put content on. These content strategy apply there. So when you're thinking of your content strategy in general you want to remember that that content might be used by all types of different devices so you want that to be able to adapt well. So if you have especially long form content it might present really well on a big device but then as soon as you put it on a small device it's going to be harder to consume for the user. So thinking ahead in that perspective. Making content consistent across devices. So if you've ever looked at a website and then tried to use it on your phone and not being able to find the content you're looking for that's one of the most frustrating user experiences. So making sure that you can access content across devices is important. Giving users clear pathways that's a really important goal to content strategy in general. And on different devices that can be again a big challenge is giving users those click through points so that they can not just find the content that they land on on a given page but actually find related content. And then just another goal in general with content strategy is solving problems in the content rather than trying to fix things with design. So sometimes when we take a website and try and make it work across devices we start giving users a design to kind of compensate for the content. Like we say, oh there's all these tables so let's just change all the tables a little so that they work better on mobile. But if you're really implementing a good content strategy you'll try and fix those content problems rather than just moving pixels around a little bit with your CSS. So for the even really high level goals we want to make sure that with content strategy we have important content first. So I think the accessibility session was here just before often in accessibility we talk about the same kind of goal like making sure that our content is really semantic and then letting the design just take care of the display. So that's one good overall goal to have. And then letting the design yeah, letting the design change the content according to the screen resolution according to the browser capability or the speed but not kind of making those assumptions right out of the gaps when you're designing how the content is going to be structured. So just basically separating out your design from the logical presentation of the content. So some techniques. So those are going to highlight the goals and how are we actually going to achieve it. So with Drupal there's obviously lots that we can do on the site building side to change how content is organized. So the first thing I'm going to talk about is structuring your content in a controlled and granular way. So if you're at the beginning of your Drupal project and you're trying to build those content types or other entity types and figuring out how those should map to the content that you have that's really going to impact your content strategy and your content strategy across devices. So we're going to talk about that. Keeping the navigation simple. So navigation is a huge thing for content strategy. It's one of the main ways people are going to explore your site and it's also one of the key things that's challenging across devices. Having a clear path to content. So beyond navigation there might be other pathways to kind of leave users from one piece of content to another. Optimizing the use of media. So beyond just text you often have a lot of images and videos and that can be a huge challenge across devices and in content strategy in general you have to keep in mind that media is also crucial to your content. And cleaning up legacy HTML. So I'm going to talk about that at the end. You've got a lot of content that doesn't fall into any kind of real information architecture. Fodlin can handle that in the course of this project. Okay, so now let's start off with content structure. And this is a Fodlin because Drupal handles structuring content so well. Like when we think of Drupal as a content management system if you've been using Drupal for years you can just take for granted the fact that you can build content types and do really cool things with content structure. But if you're new to Drupal and for how many people is this year you're fairly new to Drupal. Like maybe this is your first Drupal event. Okay, so this is a bunch of you who are new to Drupal. So maybe you'll get really excited about this because Drupal is super flexible when it comes to setting up content structures. So our goals with structuring content is we want to make sure that content is semantic. So we want to be stripping out any kind of design elements from the content itself and just adding those in afterwards. And in terms of the content structure we want to make sure that when you're looking through the content and this is before you're even adding a design just in the way the content structure we want to allow for scalability and readability. So you might think like if I'm not the designer how can I make the content skimmable and readable? Well the best way to do it is to allow the designer to make the content skimmable and readable by breaking it up into chunks. So really making the content granular so that it can be presented in a way that users can distinguish between different ideas within the flow of the content. And that's what leads to like storytelling, right? If you've got pieces of content someone can just kind of look through it and see what's there rather than having to read every piece of text. So guidelines for structuring content so right off the bat and this might seem like an obvious one but breaking down the content into individual fields is really key. So if you have a lot of content on an existing site that's long form that's just like big dumps of HTML breaking that up into a separate field or different components, different text components even can be really powerful because it means that you can present it in a more granular way. Making fields required. So again this might seem obvious but if you have different content types and you don't make fields required then when authors are creating the content they might very well be thinking about it. And that makes content less consistent and less easy for people to consume. It also makes it harder to do that story about anything I'm talking about because you can't rely on the fact that a chunk of content is there. So for example if you have a lot of let's say you have a lot of events on your website and you don't make all the fields required so some of the events have locations and some of them don't take that location data and just put it into the body text like that's kind of an obvious one but that can make the content really easy to accept. So on one thing you have this really beautiful way of displaying the location and on another event page you don't just have it alongside the rest of the text. So making fields required is going to automatically just make your content strategy more successful. Sometimes it's challenging to make fields required because you want to give flexibility for the author but just so you know there's always a drawback of doing that. Ordering fields in a logical way. So when you're actually displaying content on the page before you get to the design part where you have some things that emphasize maybe some things right out some things to say on the right or the left you want to make sure that the actual order like in the DOM in the HTML that's being printed you want to make sure that that order is logical. So again if you have an event piece of content you want to make sure that the title of the event is first probably the date is the most important thing and you want to go through and make sure that that initial ordering is making sense. Current CSS practices allow us for a ton of flexibility in how the layout can order content visually. So you just want to focus on first the semantics of what's most important. Lifting the length of text component so to just again if you have one of these body texts you're going to end up with something really long but if you're able to break that up into smaller components that's going to make it easier to read. So here would be like a learning website where someone has a lot of information to consume and rather than just presenting a whole bunch of information that someone has to read you might break that up into sections and maybe it's kind of arbitrary maybe you say each section is going to be called components or a pathway on this page and then the author is going to enter in a title and actually each one but I've written those into separate fields it means that on the design side you can visually separate the page and make it easier to be used. Okay, so one example of how you can use granular content to your advantage for different devices this is the exact same recipe data on a mobile size device and on a bigger device and just the fact that you have separate ingredient and instruction fields means that on a mobile you can hide a lot of the data and you can make it easier for the users to split between one to you like list of ingredients versus instructions they also mean you can hide less important information you have less essential you can reduce that through the nutritional information so just the display of data able to be condensed on a different device so the more fields you have the more flexibility you have in the discipline long form content has its own challenges so if you're starting off with existing content and there's just a really long text like maybe you have academic articles or just descriptions that are lengthy it can be really challenging especially if there's a WYSIWYG that's used to manage that content so how many of you are using WYSIWYG on your site and how many of you have faced issues with WYSIWYG that you're trying to WYSIWYG off a lot so WYSIWYG is going to be challenging just because when you're using a WYSIWYG you're creating a lot of HTML really knowing what that HTML is and over the years that can build up to a lot of complex HTML and often that content is better served by separate fields so in 1881 technique for doing this for taking this long form of content and breaking it up is using a module called Paragraphs because I know I'm using the Paragraphs module yet okay great Paragraph is often used for creating content fields there's lots of use cases for this I'll throw out a couple examples so let's say we have events on our website and we want to have multiple dates when the same event is occurring so one way to do that would be to say okay if you have lots of event dates just type that information into the body text and you get this really long body text and all of these event details but a better way to do that is to actually structure that content so using something like Paragraphs you can design a 700 type group today for event events and then that event instance can have the date, it can have a location and then that's its own entity that's being printed out on the page which you can style it differently so it is a lot more control to the designer to make that presentation really useful on on mobile on other devices and then that same technique in the safety instances for events that could be used also just for long form tasks so let's say you have an article but it's a very lengthy article and you want to have different sections with a unique kind of display you can create a paragraph just for like an article section and that might seem like a good pill for just a lot of text but it means that your presentation is going to be really good all those titles are going to be displayed the same way the designer can quickly go in and change the font change the display of those titles and not have to go in and update all the content for this event so identifying those opportunities to make those different types of fields that's kind of the job of a content strategist so those are the types of things you're probably going to be looking for when you go for an analyze the site and what the needs of the site are okay so that's like individual content types obviously making content drama is important once you're actually putting the site together you're going to be also thinking about navigation so how is content related to each other you've got different content types and you're actually finding the content that they're looking for so navigation some of these things are pretty obvious prior to having important menu items if you're building a main navigation and removing unneeded ones so that might seem obvious but it can be quite challenging if you're building a site and you're trying to remove things from an existing menu or you're trying to figure out what goes first in the menu but this is really key and maybe one way to kind of sell it at your organization is to talk about different devices because as soon as you try and take a navigation that's large and make it work on mobile it's going to be a huge challenge so the flatter your navigation is the easier it's going to be to make it work across prices and sometimes a technique for this is going to be breaking up a menu into separate menus separate menus for maybe some less important content so that also involves characterization not relying on mega menus so I think again in presentation before this the discussion of how challenging it is to make mega menus accessible it's also really challenging to make them work on mobile so for example what I'm talking about with the mega menu like you scroll over and you just see something like a drop down it's like this massive amount of content in the menu and often with mega menus what happens is there's actually important content like pathways to content and only access through the menu and so they kind of took the place of landing pages almost in terms of organizing the section of the site so it's great to have manual menus for navigation because on mobile you're going to be forced to simplify them so I see mega menus as more an enhancement of the user interface and not something that you can say is essential to the site using calls to action to augment or replace menus can be really interesting so if you're trying to flatten a menu and figure out like okay I want to take things out of the menu about how are people going to access these pages having really clear calls to action like large links to related content on a page can be a really good replacement for many items and the reason it's useful is that on mobile menus tend to be less visible we have to collapse menus a lot of the time and so call to action is actually going to be a more effective way of getting somebody into a related page or something I'd say place all content in the navigation hierarchy so that's kind of like the reverse of what I just said should probably be like all key content so don't if you have a navigation hierarchy and that's where the user goes to figure out what are the most important things on the site don't leave out the most important page so if you've got like that donation button and that's what you want people to do on the site make sure that that's present in that navigation interface okay so some examples we look at navigation on mobile we often really see the complexity of the navigation so sometimes when you open up like a navigation interface you're actually seeing a lot of different menus you're carrying sometimes you're seeing nested menus like on this screenshot and here I wasn't able to fit the whole menu into the screenshot so I was just going to show how much content there is in there and remember these are the types of menus that are being used because somebody lands on a page they're not on exactly the right page and now they need to figure out where are they in the site where do they want to go it's what they're using mostly through the site so if there's something that you can do to highlight certain items just reduce the size or in this case we've got a couple menus that have the same this is more on the design side but you want to have that that you want the user to be able to distinguish between different parts of the site here and in terms of content strategy if you can simplify this on the content strategy side it just makes the design a lot easier and here's one site which I think does this really well it's in spot a very simple navigation a lot of the additional pages are interesting through calls to action but they're very consistent about the display of the key pages on their site that they want to direct users to and that's just made possible by having a simple site structure to begin with point out specifically for Drupal so if you're working on content strategy and you're building out your navigation your primary goal just like with content content structure is to make sure that the menu makes sense so you want your menu structure to start with to make sense so if you've got multiple levels of your menu but it's the same like the concept of the menu is the same you can go into a single menu and the way then that you display that is incredibly flexible so if you've been working with Drupal A and you've been placing blocks with Drupal A you'll know that there's studies in the block placement for a menu or you can choose what levels you're printing out and you can choose what levels are displayed so on the display side it's incredibly flexible so you want to make sure that in terms of just the menu itself the structure makes sense so don't try and worry about the display of a menu when you're building the menu you worry about the display of the menu when you're placing the blocks and doing the design part but just in terms of how your story menu items or the parent menu items make sure that that makes sense to start with so menu placement like I said super flexible but then what should the structure be okay so navigation is important for getting users to the right content but there's other methods of getting the user to the right place so content pathways that we can consider so calls to action how many here are familiar with calls to action yeah so calls to action you think of a big red button on the page like donate now but there's often lots of calls to action on a site right you go to a site and there's actually five things that you want the user to do and maybe you want them to do them all at once on the same page and so this actually I think that a lot of the time it happens that there's a lot of calls to action on a page because the page starts out in the design as being this big thing where there's room for lots of communication to go on but as soon as you start looking at the mobile version of that content there's not room to tell the user to do five things you want to really focus the user's attention on one thing or maybe two things at once and so if you're in the design process or your content organization process starts off looking at bigger devices then that's just not taken into account and you end up just going too much down on your page so starting off thinking mobile is going to really help the class making the link between the content on the page and the call to action is key sometimes you just say oh I want the user to do this so I'm just going to give them this big button to do this thing there's no link between that and what the users do so they're reading an article on the page and then they see a way to donate but there's no correspondence between the two things so you want to make sure that you're thinking about that you're thinking about the storytelling and you're analyzing what the user is actually trying to do on the page and what you want the user to do and if there's a link between those things then you're good to play and of course mobile is really flexible with how you place blocks on a page you don't have to put the same big red button on every single page you can make it contextual so it's very simple and you're able to place blocks contextually and so you can in that way reduce the number of things but you're pushing on the user so using calls to action might be a good way to highlight the most important navigation items so that you're not relying on the user going through all the navigation links so one example of this well here's actually a big red button so donate obviously that's what Canadian Red Cross wants us to do and here like there's a couple of concepts it's a very consistent design and just in terms of content strategy when they're placing this on pages they're not also adding a whole bunch of other things that they want us to do they're really just simplifying the content and making it there slide shows so often what happens when there's more than one thing you want users to do someone said oh we should make a slide show so that we can tell the users to do five things and they'll just see all these things in the slideshow and they'll click on the one that they want to do seems like such a great idea but this is something that you can avoid happening and maybe the time to do it is like at the content strategy phase of the project before you even get to the point so before you allow the designer to come to this conclusion that you need a slide show to fit in all the calls to action you can kind of do that before it starts so slideshows have their way of freaking into websites but just some rules of thumb about how Fermi should be at letting you know you should avoid slide slideshows for key communication so something has to be communicating to the user do not put it in the slideshow because maybe they won't see it because they're on a different slide or they don't click the next button so adding something to a slide show basically means it's probably not going to be accessible to everyone and some of them are going to see it you can look for alternatives so even if it's just image content maybe making a small gallery of thumbnails or some kind of other presentation of that data might be useful and so slideshows really if you're going to use them should be limited to subcommitery information so if you've got subvisuals that you're adding to kind of show off how nice something looks that could be drawn into a slideshow but it's not like the key data and then of course not using how to control like those are all just rules of thumb so slideshows like for this not such a not such a great idea here the content actually kind of remains in place while the content changes so maybe that's more acceptable but still probably not not a great way of making the content consistent applications like this having slideshows for more just visual content is probably more acceptable although you can also of course all these do kind of gallery solutions ok so media so we've got um we've got our content strategy going we're talking about making content really granular planning out our menus really well having well placed calls to action um and then we also are always going to have some kind of media content on this site so we're going to have images then we might have some videos and how are we going to make sure that those that those work well so just like with other content you have a separation with images in Drupal between the actual images that users are uploading to the site and the way that the images are displayed so for those of you who have been using Drupal you know that there is image styles in Drupal that we can use when we're displaying the images to change the the site so we can change the size we can change the proportions we can change the aspect ratio we can darken the lighting there's all kinds of effects that we can add to images but the actual images that are uploaded that's what's key, that's our raw data so if you're having your authors create thousands of pieces of content the last thing you want to do is to have to re-upload all that image on time because you change how it looks because of some new device so you want to make sure that you're really planning ahead for different devices when you're creating these images in the first place so you want to add the treatments resizing your images just on the display so that includes things like adding overlays you don't want to be adding that to the actual raw content you want to be adding that through CSS or through some kind of image processing on large devices make sure you're optimizing your images so one thing that comes up with having a website that works on multiple devices is that there's this assumption that on a large device we don't need to optimize this much but surely on a large device you have a great internet connection and you can display these massive images that look awesome so it tends to be that on mobile people have worse connections but it could be that I'm using my laptop at a conference, I haven't used the Wi-Fi for years but maybe it's less than ideal I'm not going to be a real change you know that massive image the designer put up is just taking forever to load so you want to make sure that you're optimizing your images everywhere so for Drupal 8 there is a responsive image module and this is getting more into the technical or design details but it's important for you to know so here it means the responsive image module so it's a module so it's a module you should for sure be using and what it does is it's going to allow you to have different different sizes of image load for different sizes of screen so if you're on a really big screen you could load that larger image but load something smaller to optimize the site further for smaller screens but again you don't want to just rely on that and have the massive image always if it's not needed you want to make sure that your images are only as big as they need to be media guidelines don't auto play audio and video you want to make sure that you're not again assuming that somebody on a larger device wants to or has a bandwidth to play a video maybe they're tethering off their phone and they don't want to use all their data on your little quirky video and then using video thumbnails so instead of actually loading a whole player just displaying the thumbnails so that the user can pick if they're consuming that video that's a good rule of thumb so these are kind of best practices that we can take from mobile and also apply to our other devices displaying smaller images responsive image it's pretty easy to set up with a different module and you can integrate it with your theme you can have different sizes that you define on your theme and those will integrate great into the module okay so cleaning up legacy content so this is like a super fun topic who here has had to clean up legacy content from an old site and it's actually the first thing I think of now it's like the less fun part it's like oh we're designing this brand new Google site and the content strategy is going to be amazing but I have you know 10,000 old pages just written in canvas in each channel that doesn't fit at all with the new strategy so this is the reality of content strategy and it can be particularly challenging for devices because a lot of legacy content was not written with mobile in life so the key the key what do we call this culprits in terms of legacy content tend to be things like fixed with tables media that's just included in your HTML and having a lot of styling within the content so sometimes if you're looking at legacy HTML look at the source you'll see all these inline CSS styles that have been added to float content so particularly things that create some kind of layout if that's defined in the HTML in the actual content HTML that can be a real challenge to deal with especially if it's been done in different ways throughout the content so you don't have a consistent thing to to convert and so one of the key things that you often try to do with legacy content is take all that unstructured HTML and convert that into structured content types so if you can find patterns that will allow you to maybe even script the process to take that unstructured content and put it into content types but often that's not possible because usually the contents they're written with a busy week editor they're written by hand there's not that consistency there so often this is something that actually has to be done by hand so normally when we're doing this for a project and I have my colleagues are presenting tomorrow on a case study for Princeton University Press we just found through the process of doing this for a lot of their legacy content and what we had to do was we had to prioritize the high visibility content so you say okay there's 20,000 pages on the site and of those there's maybe 1,000 pages of static HTML to convert so that's too many pages for us to go through by hand but let's take the top 200-300 pages that are viewed most often and let's make sure that we're prioritizing those in terms of cleaning up the content so prioritization is important and one challenge with prioritization is that when you're taking a bunch of legacy content and moving it into a new system the pages that people look at might change because maybe in the old system you have these pages that were hidden away and maybe they're going to be highlighted so you just have to make sure that the content people are actually using that that's what you're taking a look at and analyzing so this is just an example from that project where there's a lot of pages like static footage in the tables part of it that then on mobile will really well still look maybe that way even not on mobile on particular on mobile they look really switched because of the table structure and so that's where you're looking at actually manually going in and converting that from tables to some kind of a grid a grid system so it's a good opportunity to in terms of doing your content this is when you probably want to come up with some kind of standards for that static content so even if you're not able to convert your big static pages into more structured content because maybe it's not possible to figure out the pattern of a field for a thousand static pages at least having more consistent html is going to be better so for example if there's a certain criteria you want to have for creating lists or creating tables or when someone should use a bootstrap grid to lay out the content those are the kind of guidelines you can come up with during your content audit to ensure that consistent so just to summarize before I wrap up so first rule of thumb create granular content that's a great place to start especially with things that really make sense as your content types don't shy away from creating really distinct specific fields for your content and trying to fit your content into that structure cleaning up with even generated html that's harder than it sounds obviously but if you're able to limit how busy we can be used it's going to actually avoid those problems in the future so that would be a great strategy to implement planning your mobile navigation so don't plan your navigation and then at the last minute say oh yeah let's do it on mobile make sure that you understand that your navigation so make sure that it works that it's going to work for that context optimizing media on mobile so making sure you've got the right raw data and adapting it well and then simplifying your pages and calls to action so calls to action there's some landing pages on your site where you might have a lot of things going on and so trying to simplify that and taking a look at those pages on mobile at the beginning of the process is going to help and then finally doing user testing on mobile so I know some projects like user testing does happen kind of like user testing expert right here taking my photo but how often does that happen on mobile I don't know like even though everyone knows that people use their phones all the time it's not necessarily the first thing you think of when you're doing user testing so just watching somebody browsing through your site on a mobile device is going to happen and that's probably something you want to do maybe at the beginning of the process so if you're creating a new site and you're going to your content that's a point at which maybe you should be doing a user testing and seeing what should be prioritized in terms of how it happens that's all I have are there any comments or questions or things I missed everyone is like I'm going to have lunch they just give me breakfast so I have just a list here of the upcoming trainings in case you're interested these are more advanced than what I've covered now it's a pretty high level session and if you're interested in more about the case study for Princeton and knowing exactly how we did that content that's mostly what my colleagues are going to be talking about tomorrow afternoon so it would be great to see you there how do you do when a client pushes back on your recommendations for your students? yeah so for sure what do people push back on? simplification it's really hard to get users to simplify their content and to be honest it's not possible it's really hard they have an existing site with a lot of content so that tends to be the biggest thing the other thing is the leading thing if you've gotten the content out you know how hard it is to get anyone to agree to remove content so really coming up with a good terminology there and saying if we're going to archive this to remove it or actually going through and meaning it works for them and saying here's what we've highlighted for removal please approve this rather than having them stick that delete button that can be hard because they're the ones who wrote all that content a lot of sites in terms of content I didn't talk too much about this but a lot of PDFs that are not really accessible and not really appropriate for 2017 so those things can be very hard to get removal on and I've just seen a value in spending time on this so this is something that we kind of just base this into our projects that are high because client starting to do something they have to do but it's not always something that seen as important or it's not something that the client identifies and share content strategy like no they just want to get their website done so we kind of have to to build this into the process yes it's in terms of not all the time video have you reconciled about the 30 minus in terms of what those videos seem to be you're only talking about who has that on their website the auto saying video the website ones that have it and for some reason people would be looking at the website and they're all looking at the website like the video yeah I guess some of those videos are less distracting than others so I didn't say maybe that's actually the video selection it's going to be useful like some of them seem more decorative like taking all of your attention and then for sure you shouldn't need that on a big screen right so now I've done that on a mobile phone if you close it it doesn't bother you so in the context of what you're saying with respect to the mobile needs and so on yeah that's a great question it'd be nice to be able to say if you're if you need to make it less than X then don't auto play the main purpose to me is to manipulate the mobile it doesn't auto play it does auto load at the same time it's interesting 7% where is that I think it's higher than that whatever the number is it's going up to me some vacation no no but I was using my phone constantly to look at websites and of course any website that cannot really optimize this message so yeah any other comments or questions yes so I think you've covered really well what I call the traditional model there's kind of a new model emerging in the current lake is there any emerging standards of how I might deliver to HTML so like designing your content for JSON feed and giving it out like I would say a lot of the same principles apply creating your content in a granular way I'm not sure specifically like if you really have no idea how much content is going to be used it can be harder to come up with those standards I guess but in general if there's any lay assumptions attached to your content like obviously that's not going to work if you can if there's information about the ordering of the content like is that making sure that that's kind of an inherent in your content as well if you have a set of options that users pick from and that the options themselves are important for making sure that that's included it was really the kind of thing more on the specifics of the content yeah I think it comes down to those people describing like if you're super specialized or especially if there's just no editing content where it is super formatically structured or is there still flexibility to have HTML content well yeah I think people tend to deliver HTML content then you have no idea what what's the idea yeah like if there's a length limit that's going to restrict how it's displayed like it just seems like when you're giving up it's kind of control anyway by surviving it's just yeah that the more structure you give you're kind of like well you're kind of deriving how you might use it but yeah I'm going to just go around the world right well if you have any other questions feel free to come by me I'll be here throughout the conference and thanks very much for coming today