 Hi, thanks for coming out bright and early to the first session of DrupalCon 2022. My name is Greg Dunlap, and this session is called Structured Content and Flexible Layouts, a case study of the editorial tools for georgia.gov. We have three people speaking here today, we'll do some introductions. I'm Greg Dunlap. I'm the director of strategy at Lullabot, and yes. Hi, I'm Marissa Epstein. I am a senior user experience strategist and CPAC for accessibility also at Lullabot. Hi, I'm Rachel Hart. I am the UX UI designer with Digital Services Georgia. So we did this project a while back. So about 10 years ago, Digital Services Georgia, who is the agency that controls all of the web presence for the state of Georgia and its state government agencies, kind of recognized that maintaining a more consistent user experience for their constituents would be really helpful for getting people to find things and use their websites. And so to this end, they had created a Drupal 7 platform for managing the websites of all of their government agencies. And it provided the agencies with a common tool set for managing their content, which would in turn help increase consistency for constituents who are trying to find content and create a better user experience for them. Now Georgia has about 120 agencies, and despite there being no mandate to join the platform, about two thirds of them did end up migrating in. But what didn't change was the governance model for this content. So the authors at the agencies are subject matter experts, and they know their content and their constituent needs better than anybody else. And so it didn't make a lot of sense to have a ton of process getting in their way. They're sitting there creating the content that they know every day. But the wide variety in web and content skills across those agencies and the people who created the content within them made it really difficult to establish or hold any content guidelines or standards or guardrails or anything like that. And the ones that they did were kind of controversial. And it was tough because those agencies, since they weren't mandated to be on the platform, they could just jump ship and launch a WordPress site any time that they wanted. But that's not very good for their constituent experience because the platform helps to bring consistency, as I said, but also better accessibility, better mobile experience and things like that. So digital services knew that even if the constituent experience wasn't perfect in the system, if the agencies left, it would get even worse. This quote really sums it up from one of the stakeholders at Georgia when she was explaining this problem. We don't have any carrots. All we have, I mean, we don't have any sticks. All we have is carrots. Oh, I'm sorry, I had it backwards. All we have is carrots. We don't have any sticks. They can't establish any rules or negative effects to get the agencies to stay. All they can do is entice them in. So there were a lot of problems to solve here, but one of the biggest ones surrounded how to manage the content authoring in the new system. So the agency authors have a wide variety of content to meet their needs, and those needs are really, really varied across the different agencies. Now some strides had been made in that system on landing pages, which allowed them to assemble flexible groups of blocks and things like that. However, they were tightly controlled, and authors weren't empowered to change them directly. The updates had to be passed through the ticketing system back to digital services. At the same time, the main content pages had few options available other than basic formatting and imagery. So all of these content authors weren't particularly happy with the situation that they had. At the same time, digital services wanted to establish more consistency and predictability. There were too many ways to do the same thing across all of the agencies, even with a centralized system, and it was causing a lot of dissonance for constituents as they jumped from agency to agency finding different kinds of content. A new common design system was going to help this, but there also needed to be more common content patterns and common ways to create pages to serve more common use cases. And then finally, the constituents, they just want clear, findable content. They want to be able to get to the sites, figure out what they need, and get to it quickly and easily. And so we created a process for doing this, and I'm going to pass this off to Marissa to talk about that. All right. Thank you, Greg. And apologies. I've been having a little too much fun, so I'm losing my voice. So yeah, jumping into the process of what we did to actually tackle this problem and also how we uncovered some of the problems Greg's described. This is a process that follows roughly four months of research and content strategy, and I've gone ahead and broken that down into three phases. First is research. This is to understand the problem from all of the perspectives involved. We had different kinds of people experiencing the pains that Greg discussed in very different ways. And so we did conduct research with Georgia residents. However, I wanted to focus on the flexibility for authors here. So I'm going to talk through our process just with the authors of state agencies. Our first interactions were what we call contextual interviews, and the reason for this is to just drink from the fire hose and absorb so much information about the current editorial experience, how it's going, what could be better. We learned about authors' goals and what complicate those goals, and we also got a sense of their comfort levels with the CMS and technology in general. So why are they contextual interviews? Because we physically went to each person's office and often desk, which was lovingly coordinated by Georgia, so we ran around hot Atlanta for two days and got to see where the work actually gets done, which was very useful to bring back to our team. So I really like some takeaways from this first step, and they capture some of the lessons learned. Please enjoy. Some people know that the site is inconsistent. Some people know that it doesn't look great. Some people know they're doing things that are not encouraged. And so to this, I wanted to say why. It seems like there were some things to dig into deeper. The next step of research was a heuristic design audit, which sounds a lot fancier than it is. This is kind of an informal, usually solo process of reviewing the website, understanding how the content was structured, and also how design patterns were currently being used. There's what the system is and then how it's actually being taken upon by authors to get around some of the editorial restrictions. And this helped us see what patterns might be missing that we would build in the future. So I often suggest to take a breath before this one. So just some delightful examples that we captured from the georgia.gov umbrella. So real sites that were intended to share a design system, but as you can see, the authors were creating workarounds for those site restrictions. So this presents some issues in accessibility and compatibility with screen readers and all of that, but also essentially ends up in the situation that the restrictions were put in place to avoid. These workarounds end up with inconsistency in the design and can lead to some trust issues on the part of the constituents. So we got a lot of inspiration here on things that we could provide as far as buttons and layout options and other things that authors were making themselves. So to recap the research, we knew that we needed to make content creation more intuitive because if something wasn't comfortable for a user or familiar, it would just be ignored in favor of the tool they knew. And we needed to provide templates with much more customization to meet a huge pool of agency needs. And we knew that authors would find a way if we didn't. So the proverbial using any tool as a hammer when they saw a nail was what we wanted to prevent. And to this end, we believed that providing best practices and celebrating real examples could be one of the carrots in our tool belt. Okay, so now we're equipped for our second phase, sharing informed recommendations with the team and refining them together. So we did present this in an in-person workshop and it was a little longer, so I'm going to try to give a shorter pitch. I'm missing some images in my slide deck. All right. I'm not sure if we can do one take a moment and see if we can. If we just shoot. And we haven't even come to the live demo. So I can actually see what I'm doing. My next couple are blank. I think I might have screwed that up this morning. Where the slide's ended in? I was just trying to make it available offline and I just kind of messed it all up. I like where you were going with it. I know right. Are you not on the wifi right now? I should be. It might be a bit spotty. I can try using my hotspot. Yeah, I should know nothing when it's still in. Maybe there's some level of local tech problem and some level of not being able to get on and not getting the wifi to load. Looks like we're connected, but nothing is coming up. I'll see you see. Try that one. I think that was because you switched wise-wise. Yeah. OK. I think you still need to select one. But if it works, great. You see what I mean? Scroll down. It's going to walk in. If you need to switch back to the other one. I'm going to my hotspot. That's what we were on. OK. Is this offline? This is the wrong talk. That's going great. I'm just going to tell everyone to picture it. It looks like these are trying to load. OK. It's going to be worth it. Do you want to try? Oh, because you're going. I see you're trying to go back. Yeah, we'll see. Do you want to try and get back on the Drupal Wi-Fi? So that the image is full? I just don't. I mean, I'll go to it. I was going to say that you'd like to get it from my phone, but I don't think that's the issue. Right, that's what I was saying. Is it like should we restore an old one or something? Well, if it's actually the same. That's what I'm wondering. This is from a week ago, and it's still not showing the images, because it's the offline mode. I don't know. I'll go back to that and change it. Well, can you make it? That's not what I want. I just switched back to the Drupal Con. We've been floating between of you. OK, let's get down to the OCC Wi-Fi for a second. Yeah, the OCC Wi-Fi isn't open. It was given us a login screen and sent by my result. And following the same OCC Wi-Fi script? Well, we have to have the login. So he's asking somebody for it, so that we can get on to it, because the. So we have our presentation on Google Slides, which is great when you have internet. And the internet, we're on the Drupal Con Wi-Fi, and nothing's loading. And so the tech is going to get us a login for the greater OCC Wi-Fi so that we can get back up. But for the moment, we're a little stuck. I'm sorry about that. Thank you for your patience. For some reason, on the laptop that we were using, every image in the entire deck disappeared for no reason, despite the fact, even when we were loading on the internet. It was very strange. So here we go. We're back in business. And I'll hand it back to you. Yeah, thanks again. OK, let me give you my hypothesis pitch now. And we'll see if it cuts out, make lots of noise. OK, so each content type in Drupal can be displayed in a variety of ways. And these are called our display modes. So example, a full page versus a teaser are default display modes within Drupal for content. And we started talking about this and how we could leverage additional custom display modes to create pages that are essentially assemblies of different pieces of content displayed this way. This eventually made its way into two broad concepts. So on the left, you can see topic pages, which are standard long form text pages, except content can be embedded into the text in different ways. On the right are landing pages, which are only an aggregation of that content throughout the site. So just pulling those different blocks that you can see there. There we go. And key to both of these solutions is a third, which is what we've been calling microcontent. So these are small pieces of structured content. And I have a ton of examples up for you here on this flickering slide. And the main way that it differs from normal site content, the microcontent, is that it does not live at its own URL. It's only meant to be featured on another page and not linked to and visited separately. So for example, we have link collections, calls to action, and icon lists. So one of the things that we like about microcontent is that it's structured to be easily reusable. You can see here we've labeled some of the fields that specifically define how it will be rendered in terms for the user. So this is a small tile set microcontent type. You can see the title, the series of links and icons and images, and the URL at the bottom in the button that can take people to information. So a nice feature of that is once we have that structure, you can see we can easily go from one column to two to three. And another great feature of microcontent is that it's reusable. So this promo that you can see here was made once and then used in multiple places throughout the site. So if you need to update that link, you can do it one time on the microcontent directly, and then that updates everywhere. And so this is a really big help for maintaining pages over time. But I'll save the cons for Rachel. Now, we have this great idea. We thought this was solid, but we needed the author buy-in. As we saw, it doesn't matter if they have a good tool, if it's not comfortable because it won't be used. So when I say testing in this third phase, I don't mean the comprehensive usability testing. I'm talking about testing our hypothesis with authors. So specifically, I'm gonna go through a few examples that brought the highest impact for providing more flexible layouts. So I'm really excited about this first step of testing. This was paper prototyping. It's a great way to engage participation and it's a low-fidelity workshop. So it doesn't require a lot of coding and setup. The goals here, we wanted to validate the page builder in that landing page sketch that you saw before and see if agency authors would be happier with the drag and drop, or if this was not cohesive with their workflow. And we also wanted to test it against real content. So if we went to an agency website, are they able to recreate all of their content there and also make content that they want in the future, essentially with the framework flourish or flounder? So here's an example of that paper prototyping that I described and this was a workshop that we did with I believe the Environmental Protections Division. So you can see in the image here, we're kind of working together and they're calling out some components that they like to build into their landing page. So the components are sketched on flashcards on the right and you can see just some very basic components from the design system we were using. In the center, we have just a laminated piece of 11 by 17 piece of paper. So we could stack the flashcards on it and we could also do some sketching if we needed with dry erase markers. And from there, we just kind of selected the cards and ordered them on the long sheet and then drew in any custom details. So this process allowed us to start with the proposed components that we came in with but then see things like which of the components were important to different agencies, which ones weren't quite working for everyone because they might need an additional presentation or if anything was just flat out missing and that we needed to create additional components. So you can see an example of that with this finished homepage and we got pretty close. We had to write in some titles of lists and change our icons from four to eight but they were pretty happy with the system. The second testing step that I wanted to discuss here focused on actually naming the content types. So the landing page was just one of the many content types that we were working on and there was a variety of ways that we approached this. Some of them we felt were working as is, some were added, some were consolidated that were very similar and now we just wanted to make sure that the authors understood them. We thought this is a pretty important barrier to entry right up front and so we were able to essentially start with a survey just asking if you were creating this which one of these would you use and then we were able to dig in a lot deeper with interviews that we paired with that paper prototyping to look at specific content or understand why they wouldn't use a content type for example. So the task here firstly was to correctly identify the best content type for a particular piece of content. Then we reviewed the create new content page itself and made sure that that was clear in the way it was laid out and then again we asked them to map a couple of their content pages so if there's a page that you wish you had which of these types do you think you could use? So I think this quote sums up nicely our findings that we saw a positive response to the content model and the layout builder functionality. Nothing was broken, everything's a step in the right direction, a lot of options, a lot of flexibilities what we wanted to hear and then that second thing there everything could be reproduced was one of our successes that we wanted to measure as well. So finally, one more testing visual for you. This is the area where you do create that new content. This is what Georgia calls their type tray and this is where I was talking about we just printed this out and asked them to imagine that they were using the site and it was nice to get some UI feedback and some features like pinning content types that authors would use most frequently per user and things like that but one of the findings I wanted to share for example is that we had created an amalgamation and aggregate of different news posts and we had called it update as in you're sharing an update with the constituents and the first couple authors that we shared that with asked us update what and heard that as a verb so we quickly changed that to news for the rest of our tests and saw that that was successful so it was really great to just iterate right off of this on paper and finally I'll note that the Lullabot developers have contributed this type tray back to the Drupal ecosystem as a module. Yeah, I'm very excited to hand things off to Rachel now. We are gonna dive into a real demo at the end hence all the tech setup but she's going to give us an overview of our changes and what's happened since. All right, so real work with tech issues, right? If it's not turn it off and turn it back on then what is the solution when you can't get things loading properly in your browser? Clear the cache. Clear the cache. Got it working. Oh no! And how do I get... I want this over there. Can. Can you just double click, no? On the top? No, cause we need to get the presenter stuff. Oh, fun. They should be back over there. Where's the presenter now? Oh, because I don't think you did presenter but you just did. Right, it's just next to me. We're so close. Okay, I'm happy with that. Yeah. All right, so sorry. All right, so I'm gonna talk about the results and what we've seen. So for example, on the left you see what landing page looked like on the old version of the site and then on the right is on the new version of the site. So of course there are some stylistic changes here. We have a new design system that we implemented along with the update but the new system also with this using layout builder gives us the flexibility to really make the page whatever it needs to be. We have different block types and then just all these different layout options that you really can build and put together however you need it to be. And then we also see a benefit with our more text heavy pages. So again on the left side is what it used to be and really it's just a vertical column of text. You can add in some images and maybe a block quote but for the most part it's just one big wissy wig. And then on the right side we are making use of that reusable micro content. So rather than just all being fully unique content on the page we can have these blocks that we can reuse elsewhere and then also embed within the wissy wig on this page specifically. So we launched our first sites in Gov Hub in this system in 2019. So we've had a few years now to see how editors are actually using it and see what has gone well and what not so much. So first off we do have more editor control. So like Greg said in the previous system the ability to edit landing pages was pretty locked down. They could swap out content in the blocks but they didn't have access to add new blocks or to move them around or really change the layout in any way and so we really just loosened the reins on that when we updated into the new system. Part of that was because we felt pretty confident that the system was intuitive enough that they could edit it with some training of course and with some pre-knowledge and with us still being available to help them we wanted to loosen that up and that's something that our editors have really responded well to. And then this also is really important for making quick and timely updates. So for example throughout the past couple of years of course every website has COVID-19 information and with the ability for editors to fully create and edit landing pages on their own without needing to go through us that means that they can make all of this information on their website available immediately and of course looking at these there are things that I would change. It's not perfect, it's not the most beautiful page layout that I've seen but it does get the information out there and that's the most crucial part for this is just making it available and then we can always go back later and make any tweaks that we need to improve the page. And this also opens up our ability to have real-time collaboration with editors. So for example last year we were working with the Georgia Department of Driver Services on updating their homepage and the editor, the primary content manager at this agency is very aware of what her editors or what her users need. She's always looking at the data and she's very in touch with her stakeholders so she comes into this knowing really what needs to happen with the homepage so she was able to within her site build this page in draft mode and she shared it with us so then we could provide some feedback and right again within the system send her back another draft and say well here are some changes like great ideas but this might be a better way to display it. She then gives us her final feedback and finally we land on the finished page. And so with her being able to directly edit the site we can have this back and forth and just working directly on the same page in draft mode right within the system. So Greg and Rosa have given a really great intro into the concept of content sharing so I wanna take a look at how that has gone so far. Now the ability to use one piece of content in multiple places has allowed authors to update and remove content in bulk and overall this has been a really big win. So for example every site has a primary contact so this is phone number, email address can have the role, whatever. So this information shows up on the contact detail page and with it being the primary contact for the site down there in the footer you can see you also have the option to add that information down there. You can also again if it's the primary it'll show on the main about us page. You can embed it within a wissy wig. You can place it on a landing page. And then it will also share to georgia.gov so all of our agencies have their own website but this information is very specific there's not really anything that is super editorial with the contact it's just phone number, email address. So we share that directly to georgia.gov and that shows up on their organization page as well as on any services that are associated with that organization. And all of this information, it's all over the place all these different placements of the contact are handled with this one edit form. So if a phone number changes they can go in there and change it in one place and that information updates everywhere that it's located. And we are continuing to update content types to encourage editors to reuse their content. So this is new for a lot of people who are working on the site so it's not always necessarily intuitive for them. So for example, editors will often add contact information directly into the wissy wig for a page that they're working on. And like we just saw, contacts are one of those types of content that can be really beneficial if they're reused throughout the site so that if anything changes you can take care of that all in one go. And from speaking with editors we learned that it's just an extra step for them in the moment when they're trying to put this information on a page to take a step back and think, okay, what contacts do I need? Now I need to create those contacts and then I need to give them certain taxonomy to organize into a contact directory so then I can show that contact directory on this page. It's just a little bit more abstract and a little more cumbersome for them to go and create that when they just want a couple of phone numbers on this page. And so this is one place where we're taking another look at the UX of building contact directories. And we really just want to make it easier for them to just grab the contacts that they need, stick them all into a table, put that on the page and it's still using all of that connected content. And this also introduces problems. So like I said, it's not super intuitive for someone who is used to just working on individual pages. They don't necessarily think of their website in terms of chunks. They think of it in terms of I'm on this page now and I'm on a different page another time. So they might forget or not totally understand that editing micro content will update it everywhere that it exists. And so for example, an editor might have a landing page and they created this for one program on their website and they really like the layout of it so they clone that page. So now they have these two separate landing pages. On the new page, they want to update the content there so they swap out the information in the blocks on that new page, not realizing that it also updated that content on the old version of the page, on the original program page that they had cloned. So really when you, with the way that it's currently built, when you clone a landing page it clones the layout for the page. It does not clone the blocks that are within it. That's all still fully connected which of course has its own benefits but if you're not aware of that then it can create these problems. And so that brings me to my final point which is that this is definitely a learning curve. So it is a different process than editing a typical page. Just it can be technically confusing. So for most content types, our editors are used to everything existing within the edit form. You just, you have these specific fields that you fill out and that creates the page and everything on that edit form is what is going to show up on the final page. And you're gonna see this in a little bit when Greg is doing the demo, but with something like a landing page it's really split into two sections. So we have the title and the summary on the edit form and other than that it's really just metadata. There's not really much of what you're doing there that's gonna affect what it looks like in the end. And most of the actual content is controlled on the layout tab. And so you're placing the blocks and moving them around and setting up what the page is gonna look like. And so that's just, it's two places for editors to go to and that's just not something that they're typically used to. And so this is, this gets back to the type tray that Marissa mentioned. Another point that can be confusing is understanding what content is versus microcontent. Understanding what a promo is versus a CTA. We have lots of things that are very similar but just different enough that we made them separate content types. And so we're continuing to look at how we are making these content types available to editors and providing them with visuals and descriptions to help them make the best choices. This also can be strategically confusing. So like I said, most editors are used to working with just a vertical column of text. They just have their wissy wig and they fill it out and that makes the page. And now they have an entire page to fully customize and build its own layout. And that can be confusing and overwhelming if you're not used to it. So again, you're gonna see this in the demo but so you create the landing page and it starts off pretty empty. You go into the Layout tab, you add a new section. Okay, now you have to decide what is the layout for this section. So you pick that. And now you have some more choices to make. Do you wanna give that section a title? Do you give it a background color, a background image? Okay, so you've got your section put together and now you have to put blocks into it. So what block are you gonna choose? You have all these options. You choose your block and now you decide some final layout options. Are you gonna put it into a card display or are you gonna give it an icon? So it's just one decision after another and this gives them the ability to make a wide variety of page layouts and make it look exactly how they want it to. It's just, but it does of course add that complexity. And we are still, right. We are still of course building out our guidance and supporting editors to put these pages together. So we have fully built out information on the technical piece of how do you do this? And then over time we are still building some more open-ended sort of like strategic pieces of how do you put together the best sort of landing page? And so one way that we're doing that is with these hands-on workshops. So we've done this a couple of times. And it's really just the idea of stepping away from the layout. So all of those options that I was showing you, save those until the end and start just with the content. Figure out what is it that this page is trying to accomplish? What do users need to get from it? And what content is going to make those goals happen? And so then if you start there, then you have a pretty good idea by the time that you're actually getting into the system and choosing the blocks that you're using, finalizing it with colors and icons and all those sorts of things. So we really encourage our editors to just start from the content level and work from there and not get too far ahead of it. And this is also a learning curve for us. So this screenshot is from a study that we did last year where we were just trying to get kind of a baseline of our customer experience and how they're liking things and so this gave us a good idea of what is going well for editors and what we need to dig more into. So now we're diving deeper into specific areas like web forms and document management and location lists and we are also continuing to think about what we can do with layout builder pages and trying to think about how we can give them all the flexibility that they need because of course, even though we have so much flexibility, it's still not enough. There's still more that they want this page, they have a specific idea in mind of what they want this page to look like and we can get so far, but it's that balance of trying to give enough options without making it confusing and overwhelming and so that's something that we're still continuing to work on doing more research. Of course, research always leads to more and just making these updates over time. So I'm gonna pass to Greg to get into a demo. And can I, yes. Oh, you wanted to just mirror. Oh no, okay. Actually, we only have five minutes left before we're supposed to cut and so I'm, and given our technical issues, I kind of don't wanna push my luck with a live demo and so, but if any, and I wanted to have time to take questions too, so if anybody has any questions, we'd love to get them. You mentioned that Lullabon contributed to the TypeTray module back. What's the name of that module? TypeTray. TypeTray. Okay. Like there. So the question was basically what are we using to do the landing pages and the micro content on the standard article pages, right? So for the landing pages, we used LayoutBuilder and that has worked out really well. We do have, actually most of the pages are more typical content types with a body field and different fields and stuff like that and for those, we used Entity Embed to bring the micro content into the WYSIWYG so that, and it's really great because you can use the same micro content types in both places and you can share content really easily and it works really well. If anybody is interested in seeing that demo, we also did this talk at Drupal GovCon and that demo is a part of that so if you wanna go check that out, you can. Of course. I'm wondering how some of that kind of work has changed. And we're all here now, it's the first time of the year, so I'm sort of wondering if you could talk a little bit about how that changed in your time. Yeah, our initial work was done well before the pandemic. I think we did this project three or four years ago, initially, but I'll ask Rachel about how things have changed in working with the agency since that started. Yeah, so of course everything has gone online. We don't have the hands-on with the post-its and everything. We are building out all of our training in an LMS so we have video tutorials, showing just some of the basics on how to edit it and then I guess the example that I showed for the Department of Driver Services homepage, that's really sort of the direction that it's gone. So I don't think that we've actually done any large group workshops since going remote but we will have projects where we're working directly with one agency and we have that back and forth and that's where opening up the permissions for editing these pages really comes in handy because we can have the back and forth with them and we can both be working on it at the same time. And so I think that's probably the primary way that we've gotten into this sort of thing. Does that answer your question? Yeah. I'll just add a PS that for non-Georgia workshops, we've been primarily using Miro and so we're using that for the stickies and you can insert images to use those components, sort of reusable. So it's not quite the same hands-on but we can see mice and draw and move things around in there so it does mimic some of that collaboration well. Miro, M-I-R-O dot com. I wanna, I'll take one last question and then I wanna make sure everybody has time to before they go to the keynote. I'm sorry, I can't hear you very well. If we were to do this project right now, which part do we think we'd like to change? I'll ask Rachel because she's had the most, I mean, we built and launched the project but she's the one who works around day-to-day. So it's tough to say. I would say the part that I would at least wanna spend some more time with is the concept of the reusable microcontents because yeah, like I said, it's on the one hand fantastic. On the other hand, it can be confusing and really just looking at what is the information with that microcontent that is fully shared from one instance to the next and what is controlled on a page by page basis. So there are times where we have a promo that we wanna show on multiple pages but maybe here we want the image to show and over here we don't just because of the way that it comes together on the page and so with the way that it's currently put together we have to create two separate promos and so that sort of thing, it gets a little tricky and I would wanna probably spend a little more time thinking about that as well as I think we have about 17 types of microcontent and some of them are very similar to each other. So if we were to do it again, I think that might be another place to spend some more time thinking about does this really need to be a totally separate type of block or is it something that can all be one? Can there be the promo and the CTA and text block all as one type of block and then maybe there's just some display options within there so that if you wanna change this link to a button display, that's a simple switch rather than having to now recreate that into a new block type. Thanks everybody, if you have any more questions, we'll be around throughout the conference. I will be at the Lullabot booth for a few hours following this and later in this afternoon or you can reach out on Twitter. I am Greg D. Dunlap on Twitter, Mars Toy Ship and Rachel H. Underscore Design. All right, got it. Thanks a lot everybody and thanks for your patience.