 Welcome. This is Gutenregge for the Gutenpocalypse. My name is Jen McFarland, and this is my colleague, Brian DeConnick. I'm actually going to pass this off to Brian right now because this is his favorite slide, and I cannot deny him his joy. This is my favorite slide. So if you get nothing else from this talk, I want you to get these two very important definitions. The first definition is portmanteau, which is a word or a morpheme whose form and meaning are derived from blending two or more distinct forms together. So you take two words and shmush them together. So like breakfast and lunch become brunch, smoke and fog become smog. And then the second definition is portmanteau. This is something that if you listen to the podcast The Illusionist you may be familiar with. It's a portmanteau you should feel bad about. So that's something like bromance or edutainment, or every single word we're going to use in this presentation, like Gutenpocalypse. We know, we feel shame, we are aware, but we're going to do it anyway. So let's get to it. Yeah, okay. Our Guten direction? Guten production. Okay, he loves these things, and I'm terrible at them. We're going to talk a little bit about us. We're from NC State, and we're going to give you sort of the breakdown of the day the music died when the Guten shit got good and real. Our user testing, talking about what we're doing on our campus to get people on board, some of our planning and scheduling and finish up with why we're Guten excited. So a little bit about us, we're located in Raleigh, North Carolina. We are a land grant institution that's been around a long time, 40,000 plus students, faculty and staff all across the state. And we also have a satellite campus in Prague, and 11 colleges in our graduate school. And we made it up here because, number one, Brian works for us, but he works remote from Boston, and I have family here, and so we're like our second home. So we thought we'd come out and share our talk with you guys. So more about us specifically. We are OIT designing web services, that's our name, and we're housed in the central IT. We maintain several major campus multisite environments. If you were in Rachel Cherry's WordPress education talk, you heard lots of themes including multisites, a big deal for our higher ed. And we support, like I said, three or four major campus-wide multisites. We also do website design development support, training, maintenance and support for our campus-based clients. We're all over the map with WordPress on campus. We're delightful. This is us. You can see that Brian is remote here. He's our bri-pad. And then we have Lauren and Miles. And for those of you who are attending Hy-Ed Web, which here's another plug, that's a great conference. It's in Sacramento this year. Lauren and Miles will be there. So go up and give them a hug and they'll be like, who are you? So if you are in Hy-Ed and Quick Show of Hands, how many of you are Hy-Ed people? There's my peeps. All right. Big institutions, lots of moving parts. I don't have to sell you on this. But WordPress is fantastic for that. We're really sold on it, albeit it's not a campus mandate for us. But we think it's a wonderful tool and it is used all over our campus in various pockets. But change is scary, especially in Hy-Ed, especially when you're dealing with 40,000-plus people at a time. And we feel like we're uniquely positioned in Central IT to be able to solve some of the problems that we foresee, both with Gutenberg and with other sort of situations. We have the flexibility to try both technical and non-technical solutions with our campus. And we're very lucky that we have a lot of support from our management who agree with us, that the top priority is to serve the university and our community as a whole. So whatever we build for us, we know that we're really building for the rest of campus as well. That's a large group. So this is actually from our mission statement. Our goals are to work in collaborative IT services, solutions and strategies to assist the state, the university and the nation. And that is something that we carry with us whenever we're planning ahead and doing our work. All that is to say, we are a four-person team. We're incredibly busy already. The last thing we needed was some sort of major crazy WordPress change. But we know when we are planning something that we're going to be focused on, the long-term health and solution of that solution being used for both our campus and beyond. So, Brian. Right. So we knew Gutenberg was coming. We tried to stay abreast of all the WordPress news out in the world. We tried to pay attention. We hang out in the Make WordPress Slack channels. But we didn't know when Gutenberg was coming. And in April of 2017, I spoke about something we were super excited about at the time, our fancy futuristic short code strategy at WordCamp Raleigh. And right at the end of the talk, I mentioned Gutenberg and I'm going to try to play a little video clip of that. So I'm not going to play anymore. That's plenty to show that we did not think Gutenberg was going to be a thing we would have to think about in 2017 or 2018. We were thinking it was going to be more of a 2020, 2021 sort of timeframe. It's going to take a few years for things to happen. Lots of time for us to figure out what's going on. Lots of time for us to play with our fancy short codes and a short cake and all that. Then I went to WordCamp US, which was in December of 2017, and Matt Mullenweg spoke, and I'll play a little clip of that. I was thinking about it. I think it's about 12 more versions, but we're going to be on 18 so far. It's about four months. So cool. Is that going to stack into around April for when I think that this will be ready for the widest audience? And why are there things seeing it now? So I love the way Matt says, cool, like it's no big deal. You know, just this major change to WordPress. It's going to be ready by April. That was not what we expected. And in that session, I was on my phone and I sent Jen a message in Slack, and this is the message I sent her. Oh, darn. Spoiler alert, I did not use the word darn. Sometimes state employees use bad language. Sometimes we have feelings. Matt Mullenweg says he thinks Gutenberg will be ready and out for everyone in April. In hindsight, using the word ready is a nice little wiggle room. There's a big difference between ready and merged into WordPress core and 5.0 is released. But that made us feel a little panic. It made us feel a little like this was happening to all of our plans for the next two years. So when we say the Gutenpocalypse, this is what we have in mind. So everything changed all of a sudden in a dramatic way. And initially we had this day or so of feeling like it's going to be all right. We knew this was coming. We just have to think through the problem and move on. Then we realized this is not fine. This is a major change to WordPress that we have not even started to think about in the way we need to think about it. And we need to learn JavaScript real fast. So there's a little bit of panic and then we got to work. And so we're going to talk about what we did to get our campus ready. He sort of glossed over that part where we jumped into it and started doing some work. There was certainly some panic and some phase where we briefly just considered really what we were getting into it. And in a case for denial, I'm part of the first person probably that you've heard talk about putting your head in the sand and pretending like this isn't happening. There are certainly technical challenges. Again, Matt talked about JS and learned it deeply and we were not that we weren't doing that. Big changes to all of our existing themes and plugins. We are none of the four of us developers at our heart. There's no computer science degrees there. We have some sociology. There's like some history. There's weird stuff in there. We're not getting by with a little bit of PHP and Googling anymore. And we're also going to be learning this in a changing environment that doesn't really have tons of documentation for what's coming out of Gutenberg. We also have conceptual challenges of changing how we think about what we're delivering in WordPress. We also teach classes so it's not just learning in blocks. We're also teaching in blocks. And we have to think about how we are developing things for our clients, how we're explaining our things for our clients, how, as Brian mentioned, we're deep into short codes. I thought Shortcake was going to get rolled into that core. So we're reworking our content and our content strategy that we sort of been focused on. And then also for us in higher ed, organizational challenges, which as many of you in higher ed know is some of the biggest problems. Educating campus developers, we have lots of developers spread across campus. Training site admins and the content editors. Giving the campus IT help desks resources to help with this transition. Talking about working on support materials. And all of this is an extra challenge for us as a very decentralized campus. We have IT help desks in most of the colleges. Again, developers in most of the colleges. So we have a lot of organizational challenges. Plus it's hard and I don't want to do it. I've got other stuff going on. But then there's lots of good reasons to do it. So I had to get the line in. As we mentioned before, we want to be informed. We want to make smart choices about how and when to make this upgrade for our campus. This is a great opportunity to learn JavaScript. And as it happens, we do have a little more JavaScript expertise than we thought we did. Surprise, it's hiding there all along. And you probably, we certainly did have developers who are interested in learning about that. And our thought is that, you know, Gutencoting in 2018 means 2019 will go that much smoother, presumably. Some of those conceptual opportunities, you know, if you went to the great talk that, John, thank you, John did, my brain just went totally blank, about chunky versus blobby content. We think this opportunity to jump into chunky content is fan-freaking-tastic. And so we're really excited about finding some new solutions that can make our content more multi-purpose. And then, you know, using that and teaching that to our users across campus. It's a great excuse to retire some old code. I know we all have some of that laying around. And again, for organizational opportunities, it lets us control our timeline and priorities by getting ahead of it. It lets us be a resource for the rest of campus. And it turns out a lot of other folks in the community, which has been great. And WordPress is built on open source and community. And we are happy to contribute back to that to provide meaningful feedback when we can and to give useful documentation and tools. And we'll talk about some of those as we go. So all of this to say, there's never a good time for a big change, especially in higher ed, but we think that this is a very good big change and we're enthusiastic about embracing it. We know that we as a campus will not go live with Gutenberg the day 5.0 is released. It doesn't matter if it's, you know, tomorrow or a year from now. We're, you know, we're going to give it a little bit of time to settle. We're going to still have to transition some people. But preparing with an aggressive timeline is going to help us do this right and make sure that everybody's ready, if not the day of the next day. So the first thing we wanted to figure out is this is a major change to WordPress. Was this actually going to look like? How bad is this going to be for our users? Or maybe will it not be bad at all? So we started with some user testing. I want to have a disclaimer up front. We did this in January. There have been a lot of very big and meaningful and good changes to Gutenberg since January. So some of this has evolved. I think a lot of the things I'm going to mention are still relevant, but maybe less so than they were at the time. And also if you are supporting a large organization, whether you're in higher ed or somewhere else, I 100% recommend you do your own user testing. You learn a lot from watching the people you support work with a new tool, figure out how they problem solve, and, you know, come up with support strategies that you think might be useful for you. So we conducted this, like I said, in January 2018. We mainly focused on power users. So people who use WordPress every day, and people whose, you know, regular day-to-day activities are going to be most impacted. We gave them a 30-minute exercise where we gave them some content to recreate using Gutenberg. We wrote a long blog post about it, and it was probably longer than it needed to be. I get a little wordy. If you're interested, you can read all about it. But don't read right now because I'm going to tell you about it. So the first thing we discovered is that no one knows what to call anything or where anything is. The big thing there is, like, this little three-dot button that shows up on the right-hand side next to blocks. Our users weren't really sure what to call that. And so when they were trying to say, I'm looking for this thing, they would get to a point where they were trying to name it, and they didn't know what to name it. We had somebody come up with mini hamburger options, which is not what I would choose, but we figured out what they meant by that. It's not always clear when to choose which block. So this whole idea of blocks is a new thing in WordPress, and knowing whether something is a quote block or a full quote block or just a paragraph block has some styling associated with it. Some formatting is a big question mark for a lot of users who are coming in with preconceived notions about how content works in WordPress. Of the users we tested, and again, this was in January 2018, of the users we tested, nobody noticed the additional block settings in the right-hand sidebar without getting it in from us. There is a lot of power, there's a lot of tools in that sidebar, and it took a while for people to catch on that they could use that to do things to their blocks. And then this is more of a subtle point, this question of whether or not they needed to highlight the text that they were trying to format when they were using the options in the right-hand sidebar. There's something sort of intuitive about that, the way we highlight text to go to the top toolbar to make it bold or italicized. If you're going to change the font size for a paragraph or something like that, you need to highlight it before you go over to the right-hand sidebar. The answer to that is no, and it's not a big deal if you highlight the text, it doesn't change anything, but what this tells us is that there's a lack of intuition about how this new user interface works. There's just lots of things that people are going to have to spend some time figuring out, and we need to make space for them to figure that out, and we'll talk about that more in just a moment. And then really our big takeaway is sometimes you have to remind users, try a different block. The block that you are trying to use right now isn't doing the thing that you think it should be doing, try a different one. WordPress is forgiving, there's a revision history, you're not going to break anything too tragically, it's okay to experiment. And that's, I think, maybe a key message to take to any users that you support is just try it, take the time to build that intuition. So with the users that we tested, it took them generally about 20 minutes and a lot of trial and error, a lot of that space to play and explore to get and hang the new editor. Not perfect, not like Gutenberg Masters, but people who could create content and publish it pretty comfortably. The problem for us on a campus of 40,000 people is how many support tickets is that going to generate when you have 20 minutes per user to try to figure this out. So we knew we needed some sort of a plan for how to transition people to make that go as seamlessly as possible for us, because we're four people and we don't have all day long to answer support tickets like this. So I mentioned earlier that we mainly tested with power users. What's interesting is when we did test with people who were less familiar with WordPress, they also tended to be people who were less familiar with sort of web interfaces in general. They didn't spend as much time using applications online, and we expected that they would sort of pick it up quickly because they didn't have any preconceived notions about how WordPress was supposed to work. We didn't really see that. Instead, we saw people really struggle with Gutenberg at first, and what we're chalking that up to, our guess is it's the shift from what we don't even think about how wordy the classic editor is. There's a lot of text on the screen to tell you what different things do. And then you make the transition from that to Gutenberg, and this is an older screenshot of Gutenberg, but you make that jump to Gutenberg where there's just a lot less text on the screen, there's a lot more iconography. Now, a lot of text shows up now when you hover over buttons, when you hover over these icons, but that's a jump that people who maybe are less familiar with this kind of interface are going to have to get used to. So again, making that space for people to gain that intuition. So, next comes training. Yeah, so we had a lot of work we knew, as Brian alluded to, that 40,000 years of time is 20 minutes, and we have to try to figure out how to communicate with people and give them that space to play. We knew, again, Gutenberg is replacing the classic editor. It's been around for 12 years. That's a long time. That's a lot of love. That's a lot of habit. And preparing for that kind of big change for all those users is tough. So, we were prepared that there may be some need to overcome resistance. I will say there's a little more resistance, I think, in the community than there is on our campus, which is a little interesting and not quite what we expected. But again, those power users have a lot of habits, ingrained habits, and they're sort of struggling with making this transition sometimes. So, you know, they made me a manager, they sent me a training, and they gave me stuff like acronyms that I feel the need to share and use now. But this was one of the things in our change management discussion about overcoming resistance to change and how we make an effort to move past changes, big changes or get people on board. So, it's an equation, and Brian lives this because he's a math major. You have to have or explain or address some of the dissatisfaction with how things are currently. Provide a vision for what's possible and describe some of the first steps to give people some comfort with, you know, beginning that process to change. And in theory, these things together will overcome resistance. And so, for us, we decided to take a step back and look at our campus and we kind of broke it into three audiences we were going to need to address these things for. And those audiences first are content creators. And, of course, that's the largest chunk of campus. And we started by preparing for training for them and addressing some of these things, like why is WordPress changing? A lot of our users have no idea this is coming and certainly don't understand why. How it's changing, what's not changing, which is almost as important as what is changing is sitting them down and saying, hey, don't panic. These things remain as they have been. Here's where you're going to see changes. What are blocks and what do they mean to me? And these things, in part, address some of those issues to overcoming those obstacles for change, right? Like explaining, not necessarily that they're dissatisfied with how things are, but explaining why things could be better, right? And then also providing some examples of blocks to give a vision of what's possible. For our site admins on campus, again, we wanted to talk about the same things, but also what are my options for choosing to upgrade? I am a site admin. This is a huge change for me. I really want to have a good handle on making this transition. And then again, will my theme work with Gutenberg? How is that going to affect my day-to-day processes? And our campus developers, who again I mentioned, we have developers in units all across campus. Their questions are more, will the themes that I support work with Gutenberg? And if not, what do I need to do to be fixing that? How do block templates work? Should I be building my own custom blocks or how do I, if I need them? So addressing all of these issues, we decided that we would work on training and all these other things for all three of those groups. So first, being hands-on experience, again, these things help to explain first steps and give people an idea of what's coming. Hints and reminders give that vision of what's possible and examples of what they can do. And then time to prepare, as we mentioned before, it's going to take a little bit of working through things to be comfortable with it. So for this training, we started with what we called Guten Day. We really can't get away from the portmanteaus. I mean, that's not even a portmanteau. That's just a prefix, right? Like, there's something wrong with my whole team loves me. So we did this for campus developers. We had about 30, 35 people there, including some from off campus, so others in our community. And that was March 2nd, so we were really rushing that in. We shared all the stuff that we had done up to that point. We also set up time for a React crash course, which failed utterly because, guess what? You have to have node installed first, and we just weren't prepared for this thing. But it was also a good opportunity for us to kick off our NC State Blocks plugin. And Brian's going to talk about that more, but this is a great opportunity for us to help, again, lead change and work by example. We've been using short codes, but we're, of course, like, hey, short codes can be blocked. Let's make this happen. And so we're well underway with that, but that was when we got that started. After Guten Day, that in part gave us a good sense for some of the questions that we were going to get, even from the less educated users. And so we started teaching the classes on Gutenberg for contact creators and Gutenberg for site administrators and offering basics and then hands-on exercises and working through sort of upgrade scenarios. Some of the hands-on experience that we wanted to offer, and you are welcome to use these as well. You can use those links. We have a Guten site. You can really use it everywhere. At OATdesign.ncsh.edu slash Gutenberg. This does require that you are an NC State faculty staffer student. You have to log in. It's locked down. But it gives people just a plain WordPress site that is going to have Gutenberg installed so they can build from scratch. There's a few pre-formatted pages in there and they can start playing around. Even more useful is we used Frontenberg by Tom Jinn. I strongly encourage you to go check that out and set this up for your campus. But you can also use ours. This is not locked down. And if you go to that page, it's going to take you to just, it's basically a back-end interface for what Gutenberg looks like. And we have that pre-populated with content, walks, you can move stuff around, try stuff out. Very good for demonstrating for our users. Very useful for taking to meetings, meetings with clients, meetings with administrators, anybody to explain, hey, this is what's coming. Here's what you, you know, here's an actual physical representation of it so you can understand what we're talking about. Addressing hints and reminders. We have been documenting this from day one and we have all these resources available at go.ncsu.edu slash Gutenberg. We've started our video tutorials. We only have a couple so far and knowledge-based articles. Those will be in our campus-wide ServiceNow repository so that, again, we and our central help desk and other campus satellite help desks can use those to communicate solutions for this change in the transition. Links to external resources and we've been blogging about our Guten journey. And we're really excited to see dot-tips show up. We think that's a great way to solve, as Brian addressed, there's sort of sometimes a lack of language in the new interface. And I love the new interface. I'm happy to not have all the verbiage, but the dot-tips are really helpful. And we encourage you to grab as much of this stuff as you want. So, that's you. So, at this point, everything is sort of this theoretical Gutenberg's going to happen someday. We're trying to get ready for it. At some point, we're actually going to have to start upgrading websites to Gutenberg. And that's where the hard work starts to begin. So, spoiler alert, contrary to what we thought after WordCamp US, WordPress 5.0 was not released in April of 2018. And that's okay. That made, I say here, more time to prepare is more time to prepare. And that's really what it comes down to. By getting started with this really aggressive timeline of we're going to be ready by April 1st, well, we were not ready by April 1st, but that put us in a good mindset for we want to hit the ground running and learn as much as we can as quickly as possible. So, everybody that we talk to wants to know what's going to happen to their website. And so, we started mapping out upgrade scenarios. The thing about mapping out those scenarios is that WordPress is used in a lot of different ways. And every site on campus is a little bit different. But that being said, we've identified sort of four typical scenarios for NC State websites that have sort of their own special pain points associated with them. So, these may look sort of familiar to you. There's the vanilla WordPress scenario where it's just using WordPress out of the box. There's not a lot going on that changes how the editor functions. There are sites with lots of short codes. And we've mentioned a couple of times we were all in on those short codes. They were the best thing ever for us, especially when combined with short code UI or short cake. There are websites that use advanced custom fields for less for metadata and more as a templating engine. There are themes that we have on campus that were either built on campus or by external vendors that never even used the content function. They just used ACF functions to pull in metadata content and display it as these sort of proto blocks in the ACF world. And then we have sites that use these page-building plugins, Visual Composer, Divi, or Beaver Builder. Those three are examples of page-building plugins or plugin-type themes, I guess, for Divi. Those are examples of things that are very well supported by some sort of a company that makes money off of WordPress. But then we have people on campus who somewhere along the way went out and bought something from Code Canyon or Theme Forest that's not supported anymore and hasn't been updated in six years and probably won't be updated when WordPress 5.0 comes out. And so that's a whole other scenario that you have to sort of plot out and plan for. We are not going to run through those scenarios because that takes a long time and every website is different and we can get mired down talking about those scenarios for a long time. But come talk to us at Snack Break if you're curious about sort of what we've learned trying to figure that out. What's more important for you to take away is take some time to think through what are the commonalities and the differences between the websites that I manage and what are some of the pain points that are unique to those types of websites. So we're responsible for thousands of websites some with more responsibility than others. We have about 50 departments or units on campus that we directly manage anything from building custom work like custom themes and plugins to they send us PowerPoint presentations with the changes that they want to make for their website and we make them like I don't know what it is about PowerPoint but anyway, so they send us the changes that they want to make. We have open registration multi-sites for student blogs and faculty blogs. We have student orgs multi-site club for whatever all in a multi-site that we manage and then another multi-site that's sort of somewhere in between the sort of open registration services and the really hands on clients. All that adds up to thousands of websites we are not going to upgrade all of them at the same time. That is a bad idea and would make for a very bad Tuesday. Instead, we are going to try to plot out how we can sort of take all these websites as different puzzle pieces and put them together into the smoothest path for us that we can make. So some of these websites are going to upgrade very quickly some of them are going to be on the Classic Editor plugin for a while because that is just how we are going to have to schedule them out. To do that we need to start evaluating gluten pain. Sort of, you know, how what are the pain points going to be for each of these specific websites. And so we created the GutenDex which you really have to want. GutenDex is the Gutenberg pain index and just mash it all together into GutenDex. And so this is an opportunity to number one, roll Gutenberg work into any new work that we are doing for them. And then number two if there are websites that just haven't had any recent updates or haven't gotten the attention that they needed for a while Gutenberg is a great opportunity to update them to the latest canvas brand or something like that. Do some of the long needed work that we just have been putting off. So as we calculate our GutenDex so we are really looking at three main things. We are looking at what theme they are using whether it is one of the standard themes that we like and support or whether it is something else or something bad. We are looking at the plugins that they are using and then we are looking at the users that we are supporting for that website. Some of them are going to handle this a lot better than others. Some of them are going to handle it fine with training. Some of them are going to be gung ho about I am going to learn this and dive in and I am excited about it. And some of them are going to give us the deer in the headlights look. So we are not going to show you how we come up with our rating and our schedule because this is all very specific to our users and our environment but these are the sorts of things that we are thinking about. From that we end up categorizing each site so Jen wrote these category names we are cool, we got work and panic mode and then we put them into a timeline. So this is our original timeline of May through July as sort of early adopters people that we want to have giving us feedback early with the Gutenberg plugin. So remember August being sort of a moving target of whenever WordPress 5.0 is released sometime this fall we think as people who are going to be ready to hit the ground running relatively quickly next year for the first six months for people who are going to need a little more work and then after that for the people who are really going to need a lot of work and a lot of handful pulling. So this is a screenshot of Jen's master spreadsheet I was not joking about the category names panic mode we got this okay with some training they don't got this this is how we function as a team it's all very like rigorous and scientific. So I mentioned earlier new work for 2018 is being done in Gutenberg as soon as we can or if it's not being done in Gutenberg we are thinking and making plans for what it's going to look like when Gutenberg does happen for that website. We are offering this custom training to all of our clients in addition to the workshops that we are offering to all of campus. I was trying to think yesterday about how many people have we put Gutenberg training in front of so far and I think it's somewhere between like 100 and 200 people on campus mainly focusing maybe even more than that mainly focusing on the people who are going to have their day to day jobs impacted the most not so much students or faculty but really the staff who keep the university running. And then so existing sites are going to be scheduled to upgrade and we are going to try to balance easy sites and hard sites as much as possible again so we don't have one really bad Tuesday and then lots of easy days I don't know why Tuesday. So from all of this we think that from the day WordPress 5.0 is released we can have our entire campus or at least the sites that we support using Gutenberg in 12 to 14 months that is a very aggressive schedule for us especially with the size of our team it's going to take a lot of work and a lot of focus but we think we can do it. So I'm going to talk a little more also about some of the tools that we're developing to try to make this happen so if you combine Johannes Gutenberg with the NC State Wolf mascot you end up with Johannes Wolfenberg he is the unofficial mascot of all of our Gutenberg preparation and all credit goes to our colleague Miles Elliott for drawing this beautiful beautiful Johannes Wolfenberg so Johannes Wolfenberg is the plugin icon for the NC State Blocks plugin which Jen mentioned earlier this is a collaborative project we're working with developers all across campus which is super exciting because our campus gets very decentralized and siloed and sometimes we don't talk to each other very well we're building some new Guten blocks in addition to the core blocks we've also ran some of the things that we really like to see on campus websites that our communications group likes to design and then some blocks that are designed to interact with other campus APIs and systems like the campus directory or things like that we are super excited about block templates and people should talk about block templates more block templates are the best thing ever come talk to us during the snack break about block templates and then again our colleague Miles Elliott wrote a simple plugin that runs through every block that's available on a website and creates a block attributes glossary which is extremely helpful when you're building block templates and also when you're just trying to figure out how do blocks work when you're trying to reverse engineer an existing core block and trying to package that up or take lessons from that and package those lessons up into a new block that you're designing we're going to share the links to the slides at the very end so go check out these things that we're sharing we're really proud of the work that we've done and really what I mean is we're proud of the work that Miles has done we'll just keep mentioning his name over and over again yes so as I mentioned earlier we really are excited about Gutenberg we know that it's a lot of work but we are genuinely happy to be doing it and we think that it's an excellent step forward for WordPress and it solves a lot of problems that have been solved with hacky work arounds extra plugins and themes now are being solved with some native solutions again I'm super excited about block templates can't even change and we're excited to be sharing our knowledge again WordPress is successful in large part due to a great community and how easy it is to find solutions to our problems or at least find someone else who has the same problem just by Googling and so we're happy to be able to embrace this change and make cool things and solve problems and document them and share all that with the community and Miles said this Miles is not the only part of the team I'm just saying he gets a lot of mention here but he did say we have this great moment of chaos to take control of our destiny and I had to give it to a stormtrooper to shut that out so for you guys when you decide to dive into Gutenberg no I'm sure you already do that it's going to take some hard work especially for those of you who are the organizational management coordination it's going to take some time it's going to take some patience but it's going to happen this is not some emerging technology that's going to disappear tomorrow this is happening and I strongly encourage you to embrace it sooner rather than later and you will get through it some of our resources again slides from our Gutenday are available online our blog posts where we lament and share organizational difficulties frontenberg we strongly encourage you to try that out on your campus or in your environment but you're welcome to use ours again we're part of the WP Campus Group which is a great organization for higher ed institutions using WordPress and Brian runs that podcast he lets me talk and say a few things our blog attributes glossary and you can tweet us or email us anytime you want here is a link to the slides look at that, 79 slides woo, we got 2 minutes, alright it's also okay if you don't have questions we answered everything there's a mic that's winding around if you just want to do some karaoke Rachel here okay, so in this whole process what was the biggest surprise and what career you all promoted and what was your biggest surprise so my biggest surprise is that I knew more JavaScript than I thought I did so I guess one of the things that we didn't talk about in the presentation but I've been thinking a lot about is Gutenberg is a big change for WordPress but as a developer there's sort of lots of on ramps into doing Gutenberg and block development you don't have to dive right into writing your own custom block you can start with theme work the changes that you're going to need to make for the block styling you can have custom color palette and then sort of grow from there so in some sense maybe a surprise is that it's easier than we expected to get started yeah I would kind of piggyback on that and say my biggest surprise was that it's actually going to be okay because he wasn't lying, we had been paying attention and for those of you too who tried at Gutenberg like last fall, maybe I think the last time I tried it was October and I tried it and I was like oh this is not going to go and I was already like let's find some code to hide this this is not going to happen and then I tried it again you know come January so when we really started to get into it and I was like okay we're going to be okay there are a lot of brilliant amazing incredible things here and I'm not just talking about the gallery there's some accessibility like the color contrast which got mentioned in the accessibility talk before this the ability to set your headings and then preview that your heading structure is right and we were telling people that all the time from an end user perspective and educating people to use the web the right way there are some great things that are core to that and I think dot tips will also help with that so there's a lot of end user improvements here if you can get it in front of people Hey do you guys have any ballpark percentage that are going to live on on day one? On day one actual date like literally in the first 24 hours probably zero I'm going to wait for five zero one and then I'll do it I don't know if I think probably I would say between 10 and 15 percent of our sites so pretty quickly and then it's just going to be working down the list from there but we truly do have it turned on at least alongside the classic editor we're out of time sorry in several places so we're using it come talk to us you guys got a snack break so we'll be hanging around for a while thank you very much guys