Hello, and welcome to the August 2016 Wikimedia Foundation Metrics Meeting. We have a number of exciting feature presentations today. Yup, the exciting ones will be all of the things you see here. Metrics, transparency report, an engagement survey update, and a research update. And then you can buttonhole all of the people who presented. So we'll start with the welcomes. New people, Ricardo Coccioli, Melody Kramer, Olga Vasileva. Please hold your applause to the end. It is very exciting though. Chelsea Shea, Danny Kaufman, Sam Patton, Anna Maria Acosta, Tarun Krishnakumar, Namayli Huyjit, and Samir Elsharbati.  I thought I might get to use that Jeb Bush line. You can club now.  Brian Vibber, 10 years. James Alexander, 6 years. Jonathan Curiel, 5 years. Andrew Bogget, 4 years. Manpreet Brar, 3 years. Brendan Campbell, at 1 year. Ash Miner, Peter Hedinskog, Eliza Barrios, Chuck Rosloff, and James Holder, all also at their 1 year mark. And still haven't found another job. New update. Hi all. I'm Maria Cruz, communications and outreach coordinator for community engagement department. I'm going to be sharing a few stories from communities. Too many things. Okay. Wiki conference India 2016 took place between 5 August and 5 and 7 August in Chandigarh, India. This was the second conference in the region. The first one was in 2011. And a lot of amazing things happened. I was organized by Punjabi Wikimedians, the newest affiliate in the region. It was, it's one of the largest regional conferences. It had like about 250 participants from 20 language communities. 25% of scholarships went to women. And there was a hackathon as well where seven different projects saw some progress. And I have my notes here. Some of the projects. Some of the projects include optical character recognition for India and Malayalam. A communications platform that hackathon participants used during the event. And Wiki speak for the web and for Android. In this conference, the first Wiki women's launch took place in the region as well. There was one new Wikipedia that went live. Sorry, Tulu Wikipedia. And as Ravi said in the closing keynote, this was a conference that really brought community together beyond any language and political barriers. And there was a renewed sense of hope in the region. People are coming together to work in new programs. We also noticed that Wikipedians often work beyond the frameworks of formal organizations. They work on their own. And a lot of them were inspired to start new Wikimedia programs after this conference. So it was a really good experience overall. Another awesome thing you may have heard about is a global campaign called her story. It was co-hosted by UN Women Initiative and Wikimedia. It took place in 12 different cities all over the world and there were other volunteers who joined online. It was a very innovative strategy as UN women facilitated partnerships with local organizations in different cities. So that was one of the highlights at least that we are focusing on in the programs team to try and bring out a case study of how this actually worked. And they focused on adding content on Wikipedia with two main focuses on quality, how to write from a gender perspective and on quantity. Sorry, I didn't make this clear before, but the objective was to write women back in history as many gender gap initiatives have as a goal. And this was creating biographies and content articles related to women topics. So these are the two stories I have for this month. And Wikimedia project milestones and affiliates. Well, as I said, Wikipedia and Tulu went live with 680 articles. Oxytons Wikipedia reached 90,000 articles. And Punjabi Wikimedia reached 1,000 entries. Yay! There are two new affiliates recognized, Wiki2Learn user group, which is dedicated to make the content on Wiki2Learn accessible on Wikimedia platforms. And Wikimedians of IOI user group, who is that it's a group that is starting activities in the capital this month. And the other news about affiliates is that the affiliate committee announced a new criteria for chapter recognition. So this applies to user groups that want to become chapters and for other groups who want to just be chapters altogether. We can read more about this on the meta page. Finally, upcoming collaboration with communities. Wikimedia Central and Eastern Europe meeting is happening this weekend in Armenia. There will be a leadership conversation starting in September. And if you have any collaborations with communities that are reaching 50 people or more, please don't forget to add it to the calendar on meta. That's community engagement. Thank you. Passing on to Matryek. Thank you, Maria. I am Tim and Bayer from the reading team. And I'm going to present the usual walkthrough for our core metrics this time for leadership. So global page views are around 500 million every month. Time desktop is a bit more than half of page views, decreasing mobile web with below 50% apps at 1.4%. And I should say that we had, if you look at the graph here, that's the last seven months. You see a pretty huge rise here. So I mean, that's an anomaly we saw. It was a pretty missed year. We found out that a couple of years on our brothers were requesting the main pages of some Wikipedia's Russian, Dutch, English, very often. And those were isolated, but it totally blew up our total metrics. So it was about 11%. And we could say that's great, of course. But after investigating it doesn't really look like these are human pages. So we have been trying to correct this. So what you're seeing is actually correction, but keep that in mind. And yeah, it's a useful reminder that these metrics can be kind of brittle sometimes. I should mention one other thing. As you may have heard, Google did a great thing. We had a few search for things on mobile version of Google and they have this panel, which accepts Wikipedia content and they improved attribution a lot recently. We had a lot of questions about it. It did not drive a lot more pages to our mobile site. But that's what we have been seeing here, but it's a good set nevertheless. Quick look at our long-term traffic trends. This is basically the same time, same every time. We're seeing since last three years, we're seeing a slight decrease minus 3%, which is kind of in a margin of error, but it's not falling a lot. But it's also not rising. Best of though has been falling very markedly over these three years. That's the blue area here. Mobile has been rising, although a bit more slowly recently. If you're interested in which current changes are regular seasonal and which not, it's also kind of hard to distinguish from actual effects of things that we're doing. You made this chart where what you're seeing here is four lines, two pages this year, last year, two years ago and three years ago. That's the time spent where you have page view data by the new page view definition. And it's kind of interesting that you see the same things happen every year. You have a huge drop on Christmas or actually before Christmas, getting back in January. You have a drop in the Northern Hemisphere summer. So I've been talking before that last year, I've had a pretty huge drop more than these long-term trends. Due to two events in June and May, which was the switch to HWS, only connections, which caused some slow connections and a block of the China. We give you a China. And we cannot also confirm this directly. So if you look at the red line, that's what happened last year. So it was above the yellow line, which is here before, and the blue line, which is now. And while in May June, it really dropped below the yellow line and even the blue line. So you can infer that there was probably an unusual non-season effect. You're also checking the ratio of mobile traffic. So I mentioned this before on Christmas. We had a huge bump because people were getting new phones probably. And this was also sustained, but it kind of stagnated. And the last few months, it actually started to rise again. We don't really know why. And what you see here is this drop is the anomalous mention was these artificial devices were only in desktop, so it decreased that ratio to keep that in mind. That's not corrected yet. Then we look at unique devices. That's a matter we introduced at the beginning of this year. And just to give you an idea about the largest 5 Wikipedia's have issued with that for 159 million. And what's also to give in mind is that the majority of them are already mobile. So what we're seeing is that on desktop, people have more pages per device to rely on mobile web. It's only less than half that. And so to give you in mind, there's still more pages on desktop, slightly more, but in terms of devices, the majority are mobile. And also in mind, devices are not users. One user might have several devices. And so this has been available for a bit over half a year, and we don't track long-term transits. But something we're seeing is that the pages per device have been slightly rising. So we'll see if that's the actual thing that's happening or that continues. But that's anything to keep in mind. Lastly, we're looking at the pages per region, Global South or the Global North. This has been decreasing, as I mentioned before, at the beginning of this year. That's the Global North, so you might have gained more to have performed the Global South, but it's been pretty much stagnating. And that's something that we're thinking currently. So the new readers are probably looking into maybe replacing that with a different country selection. Okay, that's pretty much what I wanted to say. Now we have a legal team. It's the Transparency Report. Is this on? It is. Yay! Hi, everyone. I'm Erin Palmer, a legal counsel, and this is my colleague, Jim Bawadi. And today we're going to talk to you a little bit about our latest Transparency Report. We're basically going to give you an overview of what the Transparency Report is, what's included in this report, some comparisons with previous reports, and tell a few stories that we featured in this report. So what exactly is the Transparency Report? The first page of the report really says it best. Every year we receive requests from governments, individuals, and organizations to disclose information about our users or to delete or alter content on our projects. Some are legitimate, some are not. The purpose of this Transparency Report is to shed light on the requests we receive and how we respond to them. So as you all know, Transparency is one of our guiding principles here at the Wikimedia Foundation. And one way that we can let our users and the public know that we're really committed to Transparency is about requests that we receive to alter content or delete content or to hand over information about our users. Putting together a Transparency Report like this is something that's especially important for a couple of reasons. One, our community really values privacy and transparency. And two, Transparency Reporting has become something of an industry standard in the past couple of years. Most tech companies or organizations do put out a Transparency Report. In fact, last year, Harvard's Berkman Center did a report on best practices in Transparency Reporting, and our report was cited positively in a couple of places, which was nice to see. So the report is comprised of three main categories. And the first kind of request that we report on is actually the most common. And those are requests to alter or remove content from the projects. And the classic example of this might be someone who emails the legal team because they're unhappy about a Wikipedia article about them or their business. The second category we report on are copyright-related takedowns. And we report these separately because they're governed under separate legal rules. And if someone sees content on the projects, they believe violates their copyright. They can send us what's called a Digital Millennium Copyright Act Notice or DMCA Notice, asking us to take it down.  And then the last category we report on are requests for user data. And as many of you know, we actually don't store very much user data, mainly just IP addresses, user agent information, and an email if once provided to us. We also don't store it for very long. But we occasionally do get requests from individuals, governments, and organizations to disclose some of this information. And so we report on that. And I'd say the classic example of this would be a question about who edited a specific Wikipedia article. So in addition to the sections I just mentioned, we also have a few other features on the report. We'd like to tell a few stories about requests that we received. We'll be talking about a couple of those in a minute. And we also have an FAQ that sort of explains some of the legal concepts, provides cross-links throughout the report, and just helps make the report as comprehensive as possible. So now that we've introduced the report itself, let's talk a little bit about the numbers we had this time around. In the last six months, we received 243 requests to alter or remove content on the projects, and we did not grant a single one. Thank you. Included in that 243 are five requests that were made citing the right to be forgotten specifically. The right to be forgotten is a legal concept that exists in certain countries, most notably throughout the European Union, that allows people to ask search engines to de-index certain content about them. Despite the fact that we are not a search engine, we do still get requests to alter or remove content that cite the right to be forgotten as the reason why something should be taken down. This is a comparison showing the numbers we had this time with our previous reports. As you can see, we had about a 10% increase in the number of requests we received from the previous cycle. This is the highest number that we've ever gotten, but the distribution has been more or less consistent since late 2014. Another notable fact about this report is that we had requests from more countries than ever before. This time, we had requests from 42 separate countries, usually the numbers in the high, 20s, or low 30s. We have a pretty strong culture of pushing back against requests to remove our alter content because the user should decide with the ones on the projects. That's the point of the projects. Of all the requests we've ever received, we've only granted one. That was an instance where someone's unredacted travel documents were posted on the projects without their consent and with all their information visible, and so we thought that was an instance where it should probably be taken down. We feature a couple of stories about interesting things that happened during the time that the report was being compiled, and one of the requests that we received this time around, we decided to tell the story Happy Hour, which is something the legal team knows very well these days. This was about a request from an alcoholic beverage association. They were frustrated that certain Wikipedia articles were referring to their product, which is region-specific, by what they said was a generic term, and they argued that this was contrary to both trademark law and also an international treaty. And so Jacob, who handles mostly requests that come into legal at or in box where we get information and requests from all over the world, examines this request, the examines all requests, evaluated their arguments and got back to them to let them know that A, neither trademark nor the treaty prevent people from just talking about products, and B, if they wanted to express their concerns with the community, he was happy to put them in touch. So I mentioned before that a DMC notice is a special kind of notice we can get under U.S. copyright law, asking us to take down allegedly copyrighted content. The total number of requests we got this time around was pretty straightforward. We got 22 and we granted six. One unusual thing about this cycle was that we received two DMCA counternotices. And for those of you who don't know, a counternotice is a special notice that a third party can send us after content has been taken down, asking it to be restored. In this case, we didn't grant either counternotice. The first one was mooted when the underlying DMCA notice was withdrawn, and the second one was missing some vital information so it wasn't legally valid, and we had to reject it. So over time, you can see that we received more copyright notices than we've ever received before, but the increase was pretty small, just about 10%, and the distribution was consistent with previous cycles. The bigger story is probably that the grant rate dropped from 45% last time to just 27% this time. And as I mentioned before, we received two counternotices, which we'd never gotten before. One thing worth pointing out is that it's basically unheard of for projects of our size and scope to receive DMCA notices at such low levels, and just for comparison, it was receiving 17 and 21 million of these notices per week. So to receive them in the low 20s, not 20 million, really speaks to the diligence of our user community. We also have a copyright story for you. So earlier this year, we received a notice from an Asian newspaper alleging that an article on English Wikipedia had infringed the copyright on one of their articles, but when some people investigated it, it actually turned out to be the opposite, that the content appeared on English Wikipedia before it appeared in the newspaper. They had copied Wikipedia and then sent a notice asking that it be taken down. Naturally, we rejected the notice, and we provided them with links to Creative Commons licenses and how to properly reuse Wikipedia content. Yeah, it's appropriate to laugh there. So the last category is requests for user data. This time around, we received a total of 13 requests for non-public information about our users. Seven of these were informal non-government requests, and six of these were informal government requests, and none of these requests were granted. So unlike a formal legal process like a warrant, an informal non-government request is when a private individual or organization just emails or calls us and asks us to turn over information about a user. An informal government request is when a government does the same thing. Now comparing with previous reports, we had a pretty substantial drop in the number of requests this time around, almost 50%. The type of request was also less varied. As I mentioned, we only had informal requests this time around. Usually we do get one or two formal requests, a warrant or a court order, maybe subpoena, something like that. Another thing worth noting is that as with the content request, we have a very strong culture of pushing back against these requests. We'll only disclose non-public information about a user in response to a valid and enforceable legal process such as a warrant, and often we don't have any information to turn over in the first place because we collect so little and retain it for such a short time. So during many reporting cycles, we haven't disclosed any information at all, and if we do, it's maybe one or two in a six month period. So we thought we'd wrap up by talking about some of the changes we made to this most recent report. And the first is that we added a users notified category. And just for context, we've always had a policy of notifying users when we plan to disclose their information in response to a request so long as we're legally allowed to do so and we have the necessary contact information. But until now we weren't reporting on the number of people we reported pursuant to this process. And one thing we're noting is this time the number was zero, but that's because we didn't disclose any information at all, so there was no one to notify. The second change is that we added a bit more detail about the amount of information disclosed in response to a user data request. In previous reports, we just said yes or no. We either disclosed information or we didn't. But now in going forward, we're saying when we disclose just some of the information that was requested and not all of it. An example of when this might happen is if someone asked for more information than we have and we disclose just what we do have, or when we receive a valid legal process for some of the information, but not for all of it. So that's the summer 2016 transparency report. We'd like to thank everyone who was involved in preparing it, and that includes Siddharth, Michelle, James Alexander, Ori, our legal interns, the comms team, and of course Jacob, who actually responds to all these emails and phone calls. And we'd also like to thank Pratik and Moaz who helped design the very first report. So thanks again. Okay, hopefully you guys can hear me. This is Jodi with the Talent Culture team. We wanted to give you a quick update on what's been happening with the employee engagement survey. It's this follow-up to the employee engagement survey. And we also just wanted to show you guys a bit more broadly. So if you can go to the next slide. So this is a survey. This is probably very familiar to most of you. This is the one that was shared with us in June. The biggest highlights here are the 11% increase, as well as a continued high level of participation with staff. The engagement scores for the questions related to leadership also showed an increase of 23 to 63%. Now, despite all these overall increases, there's still tons of work to be done. So on the next slide, what's been happening since. So as part of this, we just wanted to give you a quick update. First, we wanted to share that we have put a more transparent process about the engagement survey to make sure that they are consistent going forward. We've also restarted the engagement committee. The talent culture team helped them with a workshop to help identify projects that are going to be the most impact to the foundation. Initially, they focused on collaboration as a top priority and have been working on a project with staff to bubble up what ideas make the most amount of sense to get the biggest impact. We've also done a sea level workshop in a similar fashion, and they've also launched their first project focused on showing staff how important they are to the success of the foundation. Talent culture has also been doing a lot of hard work focused on manager training starting with foundational work this quarter and then moving into performance management. The team has also been doing a lot of work on values, inclusion, well-being, transparency, and operations. Next slide. So what's next? Now as part of the next step for the sea level, they're going to be talking with their team, finding a bit more about what helps the teams to feel like they are important to the foundation. The engagement committee is also going to be taking feedback from staff to pinpoint what their projects are going to be and to roll those out. And of course the talent culture team is going to continue working hard on all of our work. And then of course the engagement survey is going to run again in November to see how we're doing. And that's it for the engagement survey. Hello. Hi, folks. Thank you for coming today. People in both the foundation and the community. I'm Toby. My name is Toby. I'm a member of the team. I lead the reading team. And I'm going to tell you, I'm going to introduce the new readers research that Abby is going to tell you about. I wanted to give you a quick background on the project. So New Readers is a project designed to reach people in parts of the world that have not traditionally read or edited Wikipedia and sister sites. It's really exciting for me because it gets to the core of why I'm at the foundation. Working with great people and making an impact on the world. New Readers has been and is a collaboration. Community, communications, partnerships, reading and design research are all part of the project. We're united by a common belief in what we're doing and we've worked together for many months to make it happen. We've started the process with design research. We realize that we get the people that we're trying to reach. We have a little of experience with Wikipedia zero, but we clearly needed to know much more. And we're really hopeful that with deep engagement, with our users will lead us to better outcomes. So anyone who knows me will also know that I am interested in getting things done. So I'm going to tell you a little bit about the project itself before Abby tells you about the research. So we envision the process. The project is having three stages and we're just finished with the first, which is research. We're going to figure out what we need to build. We're going to build it and then we're going to launch it. And obviously this is very high level. There are iterations within the projects, even though the research is super exciting. We're just at the beginning. And here's a little bit more detail about the timeline because as a manager, I like timelines. We're generative research in last quarter, where we're finding concepts and then we'll start prototyping and doing evaluative research with our users before implementing and building in the next calendar year. So I'll leave you with this. If you have a mission you believe in, collaborate with great people and listen to your users, you can do great things. So Abby's going to tell you about the research and about how we did the listening and what we heard. Thanks, Toby. So yeah, I'm going to tell you about the research. So we went to four different countries. Dominic Valley did a volunteer design ethnography for us in South Africa. He did 15 interviews in about a week. Then a small team of us from the foundation of staffers went to Mexico. There were six of us. We were there for two weeks. We also did 15 interviews. In both of these research projects, the researchers were able to observe some patterns and they stepped it up and scaled their research by partnering with a team called Reboot. They're an organization that does this kind of research all over the world all the time. So we went to Nigeria and we went to India. In Nigeria we had a team of 12 people and we did 70-plus interviews. In India we did 60-plus interviews with a team of six or seven. Both those projects were two weeks too. So because we did so many more interviews, we were able to see patterns just like we saw in South Africa and Mexico. But then we went back into the field and we validated and we found more patterns. We found a lot more patterns because we were able to talk to a lot more people. So there's differences in those researchers. So when we went to Nigeria and India and Mexico, we spoke with community members in each of those countries. We were able to visit with some people in Nigeria from community of some of which you can see there. We did a whole series of phone surveys led by the global reach team in Danpoi to learn some qualitative data about people's use of wiki technology. We also did the design research that I'm going to go into a little bit more. So design research is a way, it's a part of human-centered design and it's a way that we can learn from the people we're building for what they need, what their challenges are, what goals and motivations they have so we know what to build so people can participate in free knowledge whether it's consuming or tripping. So some of the methods we use to do that are ethnographic interviews where we go into people's homes or in their workplaces and learn from them through interviewing them and talking with them. We also can see their context and their technology that they use and the technical context as well as the physical context they're in. And we asked people to demo their technology if they felt comfortable with it. Also we did some key informant interviews or expert interviews with people who are studying technology or communication or education in places that we went. We also, the phone surveys were really integral also in these regions. So I want to dive into some examples of what we learned. We came back with about 24 findings and I'm just going to share a few examples of those right now. So in using Wikipedia, a lot of times people go to Google of course and search and then find what they're looking for. They might go to Wikipedia but they might not even use Wikipedia. So, but then once people use it a little bit more and start to get to know it a little bit more, they can become suspicious of the content model. If anyone can edit, it can arouse some suspicion, especially in places like Nigeria, Mexico, when the media is captured by political or commercial interests. So trust in the content may be compromised a little bit. Utility is super high so people keep coming back to get that information they're looking for when they're searching. Low band with browsers rule both Nigeria and India. People are precious about data usage because it's expensive and... Here we go, put the card. So in Nigeria people use Opera Mini. It saves on data and it ups the speed when you're browsing. And then in India, UC browser is a highly used browser. Even though in India the cost sensitivity is a little less than in Nigeria, the speed was really articulated as a reason to use UC browser in India. And then this is one of the most interesting findings that in my opinion about language. And I'll go a little bit more deeply into it than just this one slide. But English is widely accepted as the language of the internet and of technology. Even among people whose mother tongue or their language of comfort isn't English, people don't necessarily expect that the internet and technology are going to be delivered in their local language or their language of comfort. It's also a matter of keyboards and other input devices are usually designed and used in English. So that's general for both places. In Nigeria, English is the general language. People said, yeah, English is the general language. We have lots of languages and we speak English to be able to communicate with each other. And in Nigeria also, school instruction is done in English or a combination of English in a local language, potentially. And when people write in their local languages, it's usually done in, you know, transliterated through Roman alphabet. Also, yeah, so English is the default language for online content. And local languages are used more for interpersonal communications. And in India, people can choose their language of instruction, what medium that they're going to go to school in, whether it's Hindi or Tamil or English. And when a person chooses a language besides English, it sometimes necessitates workarounds. Because of English being the language of the internet and technology, people need to do potentially workarounds with finding different input methods, potentially learning some English. And it impacts their comfort on online learning searching. So mobile web dominates for getting online and Android's a platform of choice. So feature phones and lower-end grade androids are the primary devices for getting on the internet. Only wealthy people use the higher-grade androids or iOS or Blackberry. And even then, most people prefer Android as a primary connecting device or a tethering device because of cost and also battery life. So learning technology, people are learning through other people, through friends and family and people at work. And also digital immigrants are learning from digital natives. So parents learning from their children. This particularly happens when young adults are going away to school or going away for a job and technology will then intervene as a way for the family to stay connected. So maybe someone gives someone else a phone and then helps them install WhatsApp or Facebook so they can keep in contact with the way. So in India particularly, people share and pass down devices and this spurs digital learning within the household. So people are teaching each other at home. Also men heavily influence women's technology behaviors. Women of all age groups are influenced by their male family members or colleagues in access to choice of and use of technology.  Some people will just say, hey, give me whatever you need. So maybe as we were interviewing people, we observed that they had many, many apps on their phone but only used two or three. So where'd you get those? Oh, the guy put it on my phone. So that's one way people are learning about different apps and how to use their phones and stuff in Nigeria.  So if you step back a little bit and we look at all these, not only these findings but with others in our depth, you can go to and find in a minute. I'll share the link. People using Wikipedia doesn't necessarily equal recognition of Wikipedia because as I mentioned earlier, people can go to Google and get the information they know and not even know that they're using Wikipedia. We saw Wikipedia in people's browser history but when we asked at the interview, at the end of the interview, do you know what Wikipedia is? They would say, yeah, I know it but I don't ever use it so we saw evidence of them using it. So familiarity does not necessarily equal trust as people get more familiar with it. That thing happens where people see the, there's like a crisis of trust when people find out that anyone can edit, particularly in these contexts where the content is co-opted. And also repetition of use doesn't mean that people understand about Wikipedia and the movement and the values of the movement and what it's all about. So we're really using this research. It was a big investment. A lot of people worked on the project. We now have a really valuable database of observations, of patterns, of findings and we're using this research to the biggest extent that we can. So here where you can find unmeta, there's pages you can keep up with what we're doing here. You can see the report that Reboot and us who were in the field with them wrote and built. You can look all that over and please just add questions, talk with us on the talk pages. We're really interested in knowing of these findings, what are efforts that are already existing out there in the world. We want to partner with people to address these things. We're going to have some workshops in September which will be more about discussing and communicating about these findings and learning about efforts people are making. Then those will be announced soon. And then our next steps, like I said, we're learning and getting information about what's going on around these findings. We're also going to focus in on what we're going to take action on in this first round. Because we're also exercising new processes and tools for product development, for developing partnerships and for communications and other things that we're going to do with these findings. We're narrowing into focus. With that, I guess it's time for questions and discussion. Questions from IRC. Hi there. First question, Abby. I've got multiple questions for you, but that's what. I'll start with one. Erin said, your results suggest that English has already gained dominance. So why focus on non-English in these areas? Who or what are we missing by not focusing on other languages? Well, people need content in their local languages. This is no way of suggesting that we're only going to focus on English. It's just an observation that people are using English, expecting English. That English is kind of a... Because of the way the hardware is built and the internet has been built, English is a major language there. Yeah, I just want to echo what Abby said. I think this was a super interesting finding and something we definitely didn't expect. But, you know, I don't think it's going to drive our product development into, you know, or just focusing on English. Hello, yes. This is a technical question for the legal team. I'm curious to know what is a formal request versus an informal request. If... I'm actually curious to know what is an informal request. If that happens in conversation, if it's at an email, but it's not like a formal legal paper, what does it mean? So an informal request is basically just an email or a phone call asking for something. Sometimes nicely, sometimes not, but usually they'll just ask for information. So a formal request is when we get a formal legal process like a warrant or a court order or a subpoena. It's where there's some sort of legal oversight with a set of legal rules that someone had to follow to send a request. And informal is just when they call or email us without any of that just asking for something. Thank you. And also thank you so much for the presentation. It was really clear and it made at least me understand better what transparency work is about. Thank you so much. Hey, another question for Abbie from Layla. How do we choose the specific countries to study versus all the other countries in the world and what was the line of reasoning there? The short answer is there was a lot of thinking and a lot of work about that. I'll let Toby describe that process a little bit. I'll just echo Zach.  We looked at the continent on which they were located and we wanted to have sort of one country in Asia, South America and Africa and then we voted. So it was a combination of qualitative and quantitative data and Zach put up a link to the discussion of the assessment process on and you can find it from the New Readers Wiki page. And third question also for Abbie. Mike asked whether the interviews were typically with English speakers in English or were they translated in some manner and were they all city dwellers, were they countryside people, how did that work? So about the interviews, we worked with a mixed team. So there were a few staff members in both countries. There were also reboot researchers who are on the reboot team and then we hired local researchers who are there. So there were four local researchers who spoke Pijin and the other languages that we needed to speak with our participants. In India, there were also three local researchers who spoke the languages that we perceived that we would need. So most of the conversations were done in the language, all the conversations were done in the language of comfort for that individual. So we just started the local researchers who would start the conversation and kind of assess, you know, sometimes people will start in English and assume, but then maybe they would detect that they're more comfortable in their other language so then they'd switch. So that made me like the, I was there to take notes basically. And so at the end after that, I didn't understand the language. The researcher and I would go and do a quick debrief right after the interview. But the interview itself would be taken in the language of comfort for the person that we were interviewing. What was the second part? Rural versus urban. Oh, most of the places were more urban. We did go to a peri-urban, second-tier cities. We did go to a peri-urban place in Nigeria called Ape, which is less urban than the other two places. So I also have a question. I'm just curious if you can maybe talk about the sample sizes because, you know, someone who comes from, you know, more hard science like statistical stuff, we are used to a lot of like a really big large data set to draw conclusions on. And this seemed to me to be a relatively small one. And then again, the conclusions were kind of like a different type that would expect from a large data set. Like how do you handle the fact that, you know, to speak to a few people, what do you expect from that? How can we kind of generalize this? Yeah, thank you. Great question. So you notice that in Mexico and South Africa, there were only about 15 interviews. And we were able to see a few patterns across those interviews. So that's one level of, you know, like build hypotheses from them, from those. When we had 60 or 70 interviews, we would start to see patterns, and then we would go back in the field to refute those patterns or iterate as we went. So we did that in several iterations as we went through the 60 or 70 interviews. And that said, these are all hypotheses. These are patterns and groupings of patterns we did before. And we're triangulating with quantitative data so that we can, you know, learn from the qualitative and we've observed and we've heard from people, along with quantitative data, because if you just look at the data, you're not seeing the human part as much. We're seeing the actions of the humans through the machines. So I think that this kind of work is really valuable for us to understand the human aspects in collaboration with quantitative data. Thanks. Yeah, we could have. I know, like, Zach is also getting in line to address this question. But I think it's a great one, because we've relied on quantitative data here a lot. And I think in general quantitative data can tell you what, but qualitative data, what Abby's been doing can tell you what. Also, you can't get quantitative data about users you don't have, right? If we're going to put our new readers and our new editors want, you know, we're going to have to go ahead and talk to them. I just want to add that... So in an effort to be thorough about doing this and saying, okay, if we're going to be detailed and intimate with a certain set of research participants, we also want to know how these map to trends. So wonderfully, Dan Foy and the Global Reach team have conducted phone surveys with more than 1,000 participants per region to go ahead and look at some of those high-level findings. And in India, remarkably, we did, I think it was 6,000 phone surveys across 12 languages. So it's not that we don't have quantitative data. We have qualitative data and quantitative data in an effort to really have a holistic view of the new reader situation. And to sum up, check out the thick data. That's sort of the buzzword for this kind of blend of qualitative to get a true stack, but a holistic view of your users. Okay, so thanks for this amazing research. We're looking forward to seeing how it's implemented except for the reading team. Actually, the question slash suggestion for Tillman about the traffic report. I'm very happy and grateful that we're having constant discussions on traffic trends. I really appreciate that. One suggestion I'd like to make is that as much as it's interesting to see where traffic comes from on a regional basis, I think we need to start monitoring and discussing comes from resources. I know this is something that is co-owned by reading and discovery, and the discovery team is a focus on this. They also know that we have some invitations. There's a data collect, specifically after HTTPS rollout. But I think going forward, something to monitor and discuss it. Yeah, I agree, of course. The data discovery team has been tracking this. They also have a dashboard abroad, which some of you might have seen for how the percentage of traffic we get from search engines, from internal referrals, from one link to another, et cetera. I mean, of course, this is like the surface of the ocean, what these graphs you're seeing, and we don't know much about it. I think it was country changes. I mean, I sometimes try to add these, which countries gained or lost, but there's a lot of detail that drives these changes, and we could do more to understand it. Who's that? You can understand our referrals as one-third Google, one-third internal, like links from our own site, and one-third everything else. So a question about the new readers' research. It seems like the selection of countries, or one of the findings that I thought was particularly interesting had to do with people's expectation and the fact that they were accustomed to using English on the internet. But I do wonder to what extent that comes from the selection of countries, because South Africa, Nigeria, and India, those, to me, are countries where English is kind of the language of unity even within the country. And I know that I can think of others that's not necessarily true like Brazil. Yeah, I'd say we're not generalizing this to the whole world. These are the findings we found in these particular countries. I agree with you. Yeah, it's a good point. I do think we saw this in Mexico as well, but, again, that's right next to the US, so... It was a little different, so this was 15 interviews, but one pattern we did see was people wanting to search for content in Spanish, not finding what they're looking for, using Google Translate to translate into English, search in English, and then using some translation tools depending on their English capabilities to understand the search results. So it's not just about the language you speak and the language you're comfortable in and the language of the internet, it's also about the content that's available on the internet. So that was a little bit different in Mexico from those 15 interviews that we saw. Hey, a follow-up from Aaron. Abby, do you feel like you can speak to what we'd be missing if we were only focusing on English? We said we're not only focusing on English, right? But what is it where the value is from those working on lots of different languages? For those new readers, is that particularly valuable? I'm not sure I understand exactly. What's the value? You're asking me the value of the local languages? Oh, we'll speak English, not getting content in the language that they speak. That's not a good thing. I mean, I feel like there's a huge amount of evidence. I mean, in South Africa, one of the things that Dominic Valley, who did that volunteer ethnography for us, he brought back saying people want content about stuff in their local languages. About local content in their local languages. That was one of the things. And I think that, you know, not only this is now, I'm speaking from my own perspective here, but I think that Wikis are not only about language, but they're about the culture that is representing that language and the culture of that language. And so there's huge amounts of information that is missing if everything is in English. That's my perspective. I can't say much more than that. I think it's a huge value to have many, many languages represented and I would love it as they grow personally. Yeah, I think this is definitely it's such an interesting question because there are so many things wrapped up in it. It's just not simple, right? Like there are the, I used the word, going out in the world and proselytizing English is, I think, a poor one. I don't think it speaks to our mission. I don't think it speaks to what we're about as an organization and as a movement. But I think it does give us, you know, a valuable tool in how we reach readers in specific countries. Another question. Just a clarification about language. Do you think from the experiences of interviewing the people that, is the issue more that they're so used to reading stuff in English that they're expecting it to be English or is it more that they don't even know that that language exists? Like do we have a wiki in their language but they don't even know about it or is it just they're not expecting to use it at all? I think it's the first one. If there are people who have used wiki and recognized it as Wikipedia, I think there's especially if they're a student or someone, I think people do know about the other language wikis and it's just more of an expectation of the content, the language of the internet, the language of technology. It's also the keyboards and input mechanisms that are in English and Roman alphabet. So I think it's more that than the lack of knowing about other languages. At least other language wikis. Looks like that's it. Wait another minute.


What's up everybody Jason here for jazby's case brace calm 2022 panini VIP national exclusive gold and silver pack break number 21 just sold out. This is a for random teams each break where features 25 gold packs 20 silver packs and again pretty loaded guys now remember this is a promo break So before I start I'm gonna just show you guys there of course you guys get to paste your name into the list right here so This is promo break number two that we just got done our second one of the day boom So we're gonna paste your names right here, and it's just the 21 names of course because of You know we're we're not gonna put in the 84 names. It's only 21 since it is a 21 spot break so that'll be you guys right there of course and Yeah, there you go guys you guys are now part of the promo there It's got to sell out a couple more of these and we have till Monday to do it So we should be able to get that done guys. I don't see why we can't But now here though, we're gonna quadruple your name. So that's one two three Four to make 84 spots because there is 84 teams now. Let's roll it. We got a one and a six seven times. Good luck one two three four five six and so Anthony Down to Robert now seven times here one two three four five six seven Red Sox to the top down to Falcons at the bottom Now remember also two guys, you know, this is a college rules, you know of teams apply so if You know, of course in their college uniforms and stuff like that I go to the teams that currently on if not they're retired out of the league I go to the team they play for the longest and then there'll be spots like Adam Alan Murdock I got all other not on this list. There's like an all soccer all NASCAR racing so that's how it came out first of all I'm gonna Reorder it by Customer name and then quickly show you guys what four teams you guys got so pay attention So there you go Alan Murdock got all other on this list Rangers Angels Clippers Broncos Chargers Jaguars Knicks Anthony with the Red Sox New York Giants Cavs and Sons Bradley with the A's Raptors Hornets Carolina Panthers past Patriots FC Barcelona Milwaukee in Arizona My it was the last box by the way.  Look at your Packers, man Marissa with the Eagles who would end this Football club on football team. Sorry soccer. I should say Wizards and 49ers Robert Mancini with the Nuggets Seahawks Blazers Lakers Robert Z has the Titan Sacramento Kings Steelers Bills Dodgers Codes White Hawks Falcons Sean H with the Nets Rams Magic Pirates and Steve Locke with the Washington football team Bears Browns Atlanta I'll quickly give it a quick trade window Like I said a lot of people usually really don't trade in this because obviously, you know It's tough to hit some big hits in general and I think people are kind of superstitious and they're like I don't know if I want to trade my teams But I'll give you guys a quick minute if you need to see your teams again. Let me know all right Let's just close it then guys Sorry jazz just the way it goes sometimes man. It's all multi sport Alrighty, so here we go So there's 20 silver packs and 25 gold packs So 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Let's rip them Actually, this one looks like a thick pack and look at that one of one Charles Barkley Three color patch That's nice Who has the 76ers? Logan, look at that. I won't do the train whistle because I just don't do that, but there you go Boonah Boonah Drake London, I'm gonna rip all these packs all at once as well now I'm assuming that's like a Phoenix Suns patch right cuz there's no other purple team you played for Here we go First one's a teal all Trevor Lawrence Number to 25 You got a Patrick my homes. These are number two one ninety nine Herbie number two ninety nine Tyree kill number two one ninety nine kid Cunningham CD lamb number two fifty You got a Jalen Duren Number two one ninety nine. You got a gold Henry Davis, and I think that's red 99 You got Garrett Wilson number two one ninety nine Lulu. That's definitely a gold Luga Donch is there with the Mavericks. That's five of ten We have Ben Simmons for the Brooklyn Nets tonight, and I Julio Number two one ninety nine a green. That should be out of five. Maybe yeah two of five Yolkitch for the nuggets solid Aaron Rodgers to one ninety nine. You got a deep look red to ninety nine and Jade and Ivy for Purdue rated rookie That'll go the team he's currently on Jade and Ivy there as well to one ninety nine Henry Davis to 50 I Have no clue Mike you'd have to look at the checklist and just injured out for the year of my corral That was rough. All right So one auto one one one Jane Ivy pistons. Okay, if that's pissed of that'll go to Eric Wolverton We'll call it rules team. They're currently on to me play for the longest gold pack now Go see some nice parallels here Hopefully some autos are one of one Here we go first one is a James Weisman their pink disco Number to 50 Yanis on to the combo four out of five nice one for the Milwaukee Bucks Who has the Bucks right there?  All right. We got a Bryce Harper hyper James Harden Which in green Numbered Jeff Gordon Number to 15 down the man Marino Jeff Gordon there again LeBron Crocodile that's a little Mar Jackson Let's go into the Baltimore Ravens and man you quickly cracked ice That's number two ninety nine Lamello the long donchus hyper Randy Moss and a tealaw little camel Pandora number to 25 Tealaw their hyper Mahomesies and a gold shimmer Tautis for the Padres number eight of ten Little crack guys Russell Wilson Jason Dominguez I'll be topping Lamar Jackson. Is that another crocodile? Yeah, I'm gonna get two of them That's crazy. Who has the Ravens? Logan, that's you buddy Donchich crack guys tonight, you know Devin Booker We're to 15 You got Peyton Manning pink disco number to 50 and a Magic Johnson zebra for the Lakers and Lakers would be Robert Mancini. So there you go guys That was pretty much the main stuff right here a lot of fives. We got an autograph one of one zebra a lot of good stuff here guys So appreciate it. The silver packed break number 21 now I will pose it number 22 that probably is our last one. I don't see any more silver packs after that anymore So 22 will be the last one now. That won't be a promo break, but hey you want to give it a shot at what we have left So appreciate it guys Perfect. Appreciate it guys. You ask me skatesbreak.com


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.  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.  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.  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


The multinational maritime exercise Phoenix Express 2022 concluded in El Alana, Tunisia on June 3rd. Phoenix Express 22 allowed participating nations to work side by side to better synchronize and rehearse for potential real-world scenarios. It was an opportunity for North African and partner navies to improve communications both shipped to shore and between maritime operation centers through realistic training scenarios involving human trafficking, drug smuggling, illegal weapons, and search and rescue scenarios that build interoperability and enhance the maritime security environment. Reporting from Tunis, Tunisia, I'm Petty Officer Connor Blake.