 Hello everyone. Welcome to just outside of Washington, DC, my hometown, so very grateful to see all of you here. My name is Andrew Nason. It's me. Hello. I'm Helen Hosendi. You might know us. We've both served as lead developers of WordPress for quite a while, although I've been inactive for quite a while myself at this point. We were release leads for WordPress for six major releases. I was actually the first release lead in 3.5, and we began the modern idea of rotating it every single time, and then inflicted pain on myself for doing every other one for the next two more. We also combined to have more than 7,000 contributions to WordPress core, and we've been around the community for at this point, both of us, more than a decade, which is really cool. Today, we're going to talk about, well, we'll start with some WordPress philosophy. You're familiar with great software. It should work out of the box. Decisions, not options. Striving for simplicity. Deadlines are not arbitrary. In this particular case today, we're going to talk about one particular deadline. The terms of the President and Vice President shall end at noon on the 20th day of January, which is in the 20th Amendment to the United States Constitution. In this particular case, it's really hard. All of us have had to do with deadlines in our lives and certainly in launching websites. It's hard when the deadline can only move with two-thirds of both houses of Congress and three-quarters of the states. That was a bit of a challenge. Today, we're going to talk about all the President's websites. We're going to start with, we're going to go way back. Some of you have used archive.org before. The way back machine, really great. We're instead going to go to the National Archives. Beautiful, amazing building. Let's see the Constitution, the Declaration of Independence. If you go to their website, you can even go take a look at old websites. This is one of the very first ones. This is President Clinton's website in the 90s. It is very 90s. I don't know the exact, I don't remember the pixel dimensions, but you know, this is like 640 by 480 kind of things. You can sign the guest book if you want to. It's very exciting. A couple years later, they did do a new one. We had to get this right. The flags actually were animated. You may not like it, but this is peak web design. It's true. It's downhill from here. This is another version of President Clinton's website, which despite being the 90s, this is pretty close to modern web design. We haven't really gone all that far in the last 20-something years. It looks very similar to Kubrick. Yeah, yeah, no, I can see that. The three column layout, very classic. Then we can get to President Bush. This is what his website looked like. This was, to give you a sense, we're dealing with a lot of HTML here, raw handcrafted. This is a lot of Pearl. There's some Macromedia Dreamweaver. If you really want to go back in the day and you take a look at the source, but it worked. What ended up happening is that towards the end of the Bush administration, the Obama administration was coming in. They did this. We have a presidential transition, which we'll talk about. As part of this, the Bush administration had really great, amazing career staff and contractors and folks who were doing this all the time. They ended up taking this site. They said, we built you a new CMS. It's in Pearl. It's amazing. It's super exciting. The Obama administration was like, well, that sounds great. We just did a campaign for two years. We're pretty exhausted. Here's a Photoshop file of what we wanted to look like. This is again 2008, 2009. The idea of slicing up a PSD, I'm sure. You feel that one inside. They did that. They ended up with another website, which didn't quite look like this. President Obama's website ended up looking like towards the end of his term. Certainly a nice big hero image, which feels pretty good in 2016. I should say, after about a year of that Pearl website, they ended up finally moving to Drupal, which started, I think, a bit of a renaissance in government, especially, for choosing open source software in a lot of ways. I particularly love it. I think Drupal was an excellent gateway drug to open source. I always joke, and I'm very close friends with a lot of the folks here in D.C. who do this stuff. I always joke, like, this is great. Convince them to use Drupal in five years when they need to migrate. They're going to come over to WordPress. This is the last administration's website. Quite modern. Looks like something that was done in 2017, 2018. This is not what it looked like on day one. This is the header to President Obama's website on January 19th. The very next day, this is the header to President Trump's website. All they did was they just took out all the content, changed the name, because presidential transitions are really hard. You have just now, you've run an election for multiple years. You're trying to figure out how to place thousands of political appointees in government. You have to make cabinet selections. You often have to figure out on day one, I'm going to have executive orders, press releases, an inaugural address, videos, photos, all these things that need to go. We need a site, and how does that work? You have this idea of a presidential transition, which is quietly operating for months before the election, both candidates, and then after the election, then there's like, all right, well, one of, ideally, one of you is ready to go. You don't have a whole lot of time to prepare all of this. We ended up in a very similar boat on the Biden-Harris transition. It's actually never been done before that we had to start from scratch. We did start from scratch. We were in a very interesting time where we were trying to figure out, you know, you probably remember the challenges of that presidential transition. You probably remember that it was weeks after the election before the government did a process called ascertainment to say, yes, you've won, and now you can talk to us, which is very important when you're trying to plan for things like rolling out vaccines or launching presidential websites, that coordination is really important. And so in this particular case, we had never before built a thing from scratch, and we realized that we might need to. And so we did so. What's fun about this is that I didn't need in any way to worry about the WordPress part of this, because that was a given. That was obvious. The incoming Biden team hired really great, really smart folks, and they're like, of course, we're going to use WordPress. And then they also, mind you, this is the Biden team, and many of them are from the Obama team, and a lot of them are familiar with really high-profile websites like healthcare.gov. A wildly successful story, you might have heard of it before. And as part of this, as part of healthcare.gov, we had to, you know, out of this created the United States Digital Service, where I was one of the first software engineers, and worked on making sure that these kinds of failures didn't happen again. So now we're talking about President Biden, this is his transition website, and the idea of making sure that we are ready on day one. And that's a real challenge for us to figure out, especially when we don't have a whole lot of time, and there's just not so much to do. So quite a lot to do. So we ended up needing to start from scratch in every way, including the designs. And then Ostraher, who's a wide-eyed creative, is insane, and created an entire brand for the White House in about, I don't know, 72 hours. And you can see some of that together. This logo you'll see all over the place. Very excellent. And, you know, we have an entire brand guide that moved into the White House on January 20, with colors like Joe Navy and Amtrak Gray, which I really enjoyed. And what I think is pretty amazing is that, despite the amount of time we had to do this, right, something to keep in mind here, we didn't have a whole lot of time. We got a brand guide. We had a color palette. These are all WCAG AA accessible. So I don't know about you. I've heard a lot of concerns about we can't possibly make the site accessible. All right, well, I had a constitutionally mandated deadline. And we made the site accessible, right? So it is possible. So I want to go back to the idea of what it meant to be ready on day one. And the idea that on day one, any new president is inheriting a very large government apparatus. This one in particular inherited a number of crises, not least of which was a pandemic, the idea of rolling out vaccines. And we didn't have a whole lot of time. Presidents end up using White House.gov and digital platforms and social media is an extremely important communications tool, perhaps the way radio was back in the 30s and 40s. And time was of the essence in terms of trying to make sure that we could do this. I think there were, you know, how many executive orders were signed on day one that ended up getting put out online. January was creeping up on us. We did this entire thing in about six weeks. So you heard a really great talk this morning from NASA. And I'm not picking on them at all because incredible work and frankly far broader in scale and complexity in a lot of ways than what we're trying to do. But they did not have the kind of deadline. They were able to take a number of years. They're able to put a beta tag on it, which is not something that when I was talking to people they thoroughly enjoyed. So not a whole lot of time. So I'm going to turn this over to Helen now who's going to talk through a little bit about what we were actually able to build in six weeks. Yeah. So that's really the question we get all the time, right? It's like, how did you accomplish this in six weeks? And what were your goals? So the reason why I ended up working on this along with fantastic people from WynEye and others from TenUp where I was at the time was because good old Nicen over here said, hey, I really want this to be a website that goes not just for day one, but all through this administration and into the future. What does that look like? How can we have a modern block based editing experience that moves at the speed that a new administration needs to move at? So what I really wanted to target was having this true one to one block editing experience, kind of fulfilling that promise of front-end editing, right? How long has it been? Like 10 years that we've been going on about this. This is where we ended up. I hope that you can see when it changes. It's very subtle. You might want to look at the top to see when it's changing. This is where we ended up. That's the editor and that's the front-end. That is the actual front page of the White House on day one flipping back and forth. So how did we accomplish this? How do you get there in just six weeks? And as he stated, that included having design within those six weeks. And the design is not just your web design. It includes print design, right? The branding, the whole nine yards. This was what we got in design. This is in Figma, you know, whatever design tool of your choice. This was a big part and how we were able to accomplish this in such a short period of time. Then was so detailed in his designs. You can see they're effectively sticky notes. They're Figma layers of his notes. They're color-coded to tell us what they were about. They include things like dimensions, intention, interactivity, character limits or hopeful character limits, all of these kinds of things. That really made our job that much easier. I don't know how he got this done in the space of a single-digit number of days. I have no idea. But he did. And that made our jobs so much easier. And what really ended up happening in technical terms, right, and how we developed this was we had a wonderful front-end engineer at Wadi who's sitting right here, Ravens, who's fantastic. Now he's at 10-up, though. So Ravens was working through blocks in terms of front-end components, right? So he's out here building the HTML, the CSS and PHP to get it into place. While we at 10-up, we're working through things like custom post types, making sure that the right plugins and all of those things were in place because we also wanted to be multilingual from day one. So as he's working through that, we're working through the other end. We just get going right away. We don't need to wait for design to know that we're going to need certain things. And then as he rolls through those, he hands them off to us over at 10-up and we translate those into blocks for the editor, the editing experience and how that's going to work out. So now you all get to see what that actual editing experience looked like. This is constructing a home page. You don't construct a home page very often, right? You typically are editing it. But this is what the editor looked like. We had pre-inserted blocks to give advantage of templates in the block editor and you are typing in place. I mean, even that vertical text you type in place, it is kind of weird to type that way, to be honest. But it works. And then we make it really clear in these blocks what's expected, what your maximums are, what you should do next, right? So here, you type in the things that should be links and then you add the links and then you pick a picture and it goes into place right there in the block editor. And then, oh no, I can see because it's, you know, WYSIWYG that that's not a good layout. So I can open up the sidebar, move that over so that it compliments the image. And then I get things like, you know, latest news, pretty typical. Sometimes the featured image isn't there or it doesn't work in that space. So we can actually assign custom images for that space, pop open the sidebar, move stuff around. Oh, because dragging around things of different sizes is always very awkward. And then we get into these things, your little blocks. And so these blocks are all custom blocks. And the reason why we made that choice in this case is because we knew what our priorities were, right? Our priority in this case was not flexibility. Our priority was being able to get stuff published and out there as quickly as possible. And custom blocks was the correct route for us. That doesn't make the correct route for everybody, but you have to know what your priorities are and what you want to build for. So that's what these are. These are all custom blocks. They are not patterns, but they do utilize the core React components under the hood within these custom blocks. So this is the same block. And what we can do is we can flip it. And then we've got the same thing. You just type into place and you really get your true one-to-one experience. It really gives you that sense of security. Like I know what I'm going to get, right? And that reduces that time to getting something out there, right? Because how much time have you spent putting stuff into your meta boxes? You hit save or you hit preview and like pray that somebody actually added meta to the preview and see what it looks like, right? How often have you had to do that? And how long does that take to just keep going back and forth and back and forth and oh God, I accidentally saved it or oh God, meta only saves live and now I've actually impacted the actual live homepage before I'm ready. So this really reduces that time to getting things ready, to knowing what you're going to get out there, to not making a mistake because we don't want the presidential administration to make a mistake. That seems really bad. So this is this is how it goes. You go down the page, you fill out your things. Again, in practice, you're probably, you know, messing with what's already there and then you hit view and it looks pretty much exactly the same. There are minor differences. If you are eagle-eyed, you might be seeing minor differences in spacing. That's something that should be improving actually as of the latest release in 6.3 which is where the editor can be, the blocks in the editor can be iframed instead of what it currently is and what that means is that the responsive design actually reacts correctly to the CSS. And what's big about that is where you see some of those minor differences is because that responsive design right is for your viewport, the size of your window. But if you pop open the sidebar in the editor, that doesn't actually change the size of your window. It's only changing the size of the stuff inside the window. And that's where you run into issues. And what we had in here and what made this so efficient and the big part of the reason why we were able to make it one-to-one is because this editor style sheet actually just includes all of the CSS from the front end because we use exactly the same markup, exactly the same class names, just a few overrides to account for things like different spacing or inheritance. And that's what made it possible to get this going and to make it one-to-one. It is one-to-one because it's using literally the same files in the back end. Six weeks, by the way. Six weeks. All right. I'll show you another little demo. This one is of publishing posts. So press releases. And this one I'm going to talk through how we thought about these custom blocks and where we really leveraged them. So first and foremost, you can see the title has been styled. It is the default title field, but it's inspired to match the front end. And here I'm actually picking a category because you are only allowed to have one category. You may not have multiple. We don't want you to use a default picker. And then we actually put the date picker also in place. And the reason we did that is because we actually thought, you know what would be great is if you never have to open the sidebar in order to publish something. If you can really, truly just leave it and get that one to one like you're editing in the front end. So featured image, date, category picker, all of that is directly in a top block that's pre-inserted into posts. And we can do a little minor formatting. You know how it goes. You're reviewing out of a Google doc or whatever, right? You paste it in. So I hit publish. It goes. Seems pretty good. I feel good about it. And you know, I can view it. Did you even catch that? I'll play it again. I hit view. It changed. That's really the promise of front-end editing, right? It's like, if we can make things fast enough, perform it enough, that clicking of edit, that clicking of view, should be barely perceptible. We are a little bit lucky in that the header kind of matches the toolbar and all of that, right? So there's a little bit of luck and flexing around in there. But that's really the idea, right? It's like you can barely tell that you've switched between them, because we want you to know what you're going to get when you're done. So I do have to credit WordPress 5.6. I actually was on the release squad for this release, which was a good time, but it didn't. I was not really involved in the editor. You know, there's an editor tech lead and they're doing things that like, honestly, like I don't pay super close attention to all the time. But I do have to credit that with our ability to build this, the way that we did in the first place. And the reason for that is because there was a version two of the block API, which introduced these block props, where now you don't have as much wrapper stuff built into the editor and you can be more declarative yourself as a developer about what is the markup? What are the class names? How does this get saved right back into the database? And that is a huge part of why we were able to do something like let's just slurp all the CSS and the editor styles and use exactly the same class names, exactly the same markup. That's what made it work. And it was huge and our ability to do this. And I also want to shout out a couple other people who are up here in the front, Aaron Jorbin and Jeff Paul, who are also a big part of us being able to do this. They jumped in, helped us get stuff done, stay organized, training editors who were delighted to use this. I'm going to say those training sessions were real short because you could just get in and it made sense. There wasn't a lot of mystery to the editor, which again just told us we had accomplished our goals. And we had kept our eye on the price, right? Like we are united. We're not fighting with each other. There's no competition. There's no egos. There's none of that. We have our eye on the price. We want the new administration to be able to communicate at the speed that they need to from day one. So I'm going to talk about hosting. Basically look like this. No. So one thing that's really cool and Helen was talking about WordPress 5.6. WordPress 5.6 came out in December of 2020. 5.6.1 didn't even come out until February 3rd. So we were developing on trunk launching on January 20th at noon on 5.6. And then upgraded to 5.6.1 when it came out shortly thereafter. If the White House can do it I bet you can too. So on hosting. So we had six weeks. We had a lot to do. A lot to build a lot to design. And then we had to figure out where to put it. And I don't know how often you've ever done a build in which you have no idea how it's getting hosted at the end of the day. But if it's complex like this again you get a little nervous. So two weeks before launch day was the first time. So I was the lead on transition for all of this. And I was a volunteer like many others taking time off of their regular jobs to do this. It wasn't the government or anything else along those lines. And you know they brought me on because like well you know how to prevent health care dot gov and you know wordpress. So like please go make sure that we can launch a wordpress thing that's not health care dot gov. And in this particular case like the first opportunity that we had to sit down with the government to talk about. So by the way you might have think you've been thinking we were going to provide you some photoshop files and some slices but like we actually just went out and built the whole thing was on January 6th two weeks before launch. There were a number of things that happened that day of course mostly focused on eight hours plus of meetings with making sure that we could get ready. And they were surprised and delighted that we had built them a thing. And the previous administration was actually already using wordpress and they had some options and we had to figure out like how is this going to work how are we going to put all this together. And how are we going to make sure that this can scale up. So we had to launch a site. You know I mean imagine a scenario where at 1159 am it's one thing and 12 noon it's another thing. You're how you have you know you have called caches. You've never really tested this at scale. If you're going to get the most traffic then you'll probably ever get any other day ever again. Until 1159 at some future point in the future while everyone's clicking refresh waiting to see what happens. And it's a little nerve wracking a little terrifying can't have a do over. But nonetheless we were able to come up with a strategy that that worked. And what was terrifying in November and December were like you know what if what if we never get a chance to talk with them. So we started talking about other ideas of like well we can make it a static site and like call someone at 12 o'clock when we're in charge and say hey can you redirect the domain. We gained out all of this and we gained out even more of this for right after the election with transition in the and build back better dog of the transition website but we had to think through every possible contingency plan and we didn't need to use almost any of it which is really great we were able to instead have this site get launched hosted ready to go on that day. So that brings us to an on duration day. And this was if you've ever you know if you've ever worked on a major release of WordPress this is very much like the stare at the download counter and drink kind of thing at the end of the day felt a little bit like that because it exactly 12 noon it was an automatic timer and a config somewhere that said serve it from this place instead and boom automatic ready to go. Hopefully the cash was a warm. And we did actually have some some small we dealt with a bit of an incident it's kind of fun maybe I'll tell it some time. It stayed up so that was fine but we'll freaking out a little bit involves it involves SVGs a CDN a 404 page and permalinks it's great it's actually good but nonetheless we worked through it had you know an incident commander in charge certainly would recommend that for any big bank launch. Maybe the one number one lesson here is don't do a big bank launch. But unfortunately that's what the founding founding fathers decided to do. So here we are. And so this is the original site and this is exactly what Helen was showing later. And I'm really proud of the work that the whole team was able to do in terms of making this happen. And and it's it's just so critical to make sure that that truly the team could be ready on day one to to lead to take over. And this is a very very very small part of that. But it felt really good to be pencils down at noon because I was no longer I was not working in the government. And I was like well can't touch it anymore. It's great. Hopefully there are no bugs. So with that I would like to thank you all for coming today. And Helen and I would absolutely love and be delighted to take some questions. Thank you. There are mics over here. I think we started a little late. We'll give it ten minutes. There is a break after this and then you know we'll be around. So we're also happy to take questions one on one. My boss saw this presentation and say oh they didn't six weeks so can we. Sorry that was not our intention here. Resource allocation did it take to get this done. Yeah. That's that's a big part of it. That's what I meant by like not having egos right and being able to collaborate together right. Because we so just on the agency side we had wide eye both creative front end and accessibility. And then we had set up doing primarily like I guess what you might call back end development. So the the development of the editor things that go into like plugins themes heavily on the PHP side. A lot of this worked because we had 24 hour time zone coverage. So a bunch of us are in US time of course but one of the engineers at turn up is in Vietnam and was able to work when we were not. Some of us also work just worked 24 hours. Yeah. Do not advise by the way but if it's a thing that you feel passionately about right and I think that was a big part of it too is we felt passionately about getting this done right. Right. And that we made that choice for ourselves to do it that way. There was nobody being like you have to do it this way. Right. It was our own sense of pride in what we wanted to accomplish that got us there. I guess I'll also just add that it was a small team. I mean we're talking maybe 10 12 people total for all of this. But a ruthless prioritization of what we really need to do. You know you can figure out you could deal with quality you can deal with time you can do with scope quality and time that limited scope. Of course we had to really be careful about. And we also knew that at the end of the day the site needed to work on January 20th there was going to be a team that was going to inherit it and that that they could then go ahead and build more things on top of it. So in a way you know it was a beta which didn't put the logo on there but that that ended up helping quite a bit. So I mean it wasn't all that complicated of a work site. I mean many of you probably saw they're like all right you know we've done this which is great. The blocks are of course extremely impressive throwing it out there. But at the end of the day like what really made it complicated was the White House presidential transition a complicated presidential transition and heading into government and and if this was you know a much less high profile launch then like honestly you can do an awful lot in six weeks. So on the block editor one of the things I noticed in the top right corner was the Yoast logo. What large established projects did you find were worth leaning on and made significant impacts to the workflow for the build out? You know we were talking about this I don't honestly remember what all of the points were on this site. So yes Yoast was there. Yoast was there. A multi-lingual press. So first the first White House website that was launched like on day one in English and Spanish and that was I mean that's an obvious one certainly to use that solution. But a lot of it was also just like less is more like let's get this. Where did you go? You already sat down. Oh thanks George. Appreciate it George. No, I don't know like I mean a lot of it was like less is more because like we you know functionality ultimately was like the thing that we were constraining the most. We didn't even talk about like in the editor itself we removed most of the functionality in terms of you know font colors, sizes all those things was just like we turned it off because we wanted it like you know exactly what you need to do. The last thing you want to do is copy and paste an executive order out of like Microsoft Word and like get some random font thing in there like it's fine, right? Like we can strip out all of that which is really impressive. So I think a lot of that was more what was a lot what was in there. I'm trying to remember the rest of it though that was that was the bulk of it. We did do a fun thing though we took I don't know if this is ever otherwise been done but the on for WordPress VIP which the site was not on they have like the VIP Go has its own like huge bundle of like plugins and code and things like that and the transition website buildbackbetter.gov was on WordPress VIP and that's the codebase we kind of started off with a little bit and so we ended up using in production on day one the entire VIP development codebase that you normally use locally but we just didn't production which was fine and it worked and so like there was a lot of that functionality that we kind of like got for free from things like that that was obviously very helpful as well. I think that also speaks to like how we could get it done fast is like yeah again aggressive prioritization like is it important to get it perfect on day one? No, right? Some of us are walking around with little pins that say hello, I'm waiting on content. So what was the content development process like? Because it sounds like maybe you got that on January 19th. I don't know. So I'm a software engineer. I wrote very low code for this project. I spent most of my time wrangling as you can imagine not only talking with the government but also all the other transition team and we had a fantastic amazing team on transition that focused specifically on content on everything from like what to the president elects bio be and which photo does the second gentleman prefer? And I'm kidding but you get the sense, right? Like every single aspect of this needed to be very precisely looked through and ultimately while that team was happening we missed probably every single self-imposed deadline on content, certainly. But at the end of the day like the site itself didn't have a ton of content on day one. It certainly had, you know, important, you know, what are day one priorities? Who are the members of the cabinet? Who are being nominated for positions? But really, a lot of the content didn't exist yet. It was all the executive orders that still needed to get signed, finalized, published all of the press releases, all of the addresses, all of everything else. And so I won't say that we got lucky because certainly there was a lot. I think we were we were making content updates certainly up until the morning of January 20th. And then about 20 minutes later we started pushing them up onto the site. So wouldn't recommend that general rule of thumb. But it was able to work. But it was a really great team behind all of that, making sure that that can. So that was a totally separate allocation of resources to get the content together. And I'm saying this for my agency friends because there's like the development side. And you guys are doing amazing work. And then there's this content side that's separate. Yeah, I mean, two people is team, right? We can say team if it's two. Yeah, not, you know, it's it's it's we're bootstrapped here. We got to know it was very I mean, it's obviously a huge operation to get all of this done, right? The nice thing is that like the content team for the website isn't the one right in the executive order. Someone else is doing that. So a lot of the content is is ready to go with a very large team that is all landing in the government jobs on day one. So it's it's nuanced, certainly a lot of ways. Yeah. Curious, what's next to this project? You mentioned that you build custom blocks. Are there any inclinations, including full site editing or transitioning more towards more flexible architecture? Like you said, you remove most features like fonts and everything. Are there any plans to use the recent features of WordPress? So what's particularly cool about this is that after January 20th, it wasn't our problem. There are two people here, though, who's probably it is. You can find them. There are a few folks. I think Doug Axelrod and Kurt Schaener and a couple of others can probably if you want to find them, I'm sure they can talk to you about what the government now what the White House is currently doing now with this. But our job was really like get something ready for day one. I am in particular, I insisted on on Gutenberg, which everyone was like, you're crazy, not Helen, but that was before we had Helen. And I was like, no, really, like this has to be a thing that can then work on day two, three, four, however many. And so that was I think that was really critical of like making sure that we are absolutely ready to go. And not just with like a bare-boned splash page that two months later we got to completely redo, but rather like allow the team on the inside, which would not be us, to then make those incremental improvements and incremental changes, but being able to say like, all right, great, let's go figure out what the needs are over the coming months. Thank you. Yeah. I think this will have to be yeah, the last two. Let me give them a break. So I work with a lot of clients who are certainly not the president of the United States and we go through discovery, wire framing, whole nine yards and they're like, it's a good start. Like how do you get through this in six weeks or however long it took and get Otis to say cool? Well, I mean, the nice thing is that like everyone knew what the deadline was, right? So we were all working in the same direction of like this needed to happen. And you know, the president-elect is of course going through and approving how many day one executive orders and how many appointments and also like I though what the website will look like, right? So this was honestly in a lot of ways quite easy because, you know, it followed a lot of the a lot of the design inspiration that was set originally by the by the by the Biden-Harris campaign and ultimately that was designed during transition and that was, you know, ready to go with our, you know, Joe, Joe Navy and Amtrak Gray and on on day one. And so, you know, I don't know, maybe people just really love the hero images. I'm not entirely sure. But the actual approval process for that was relatively straightforward and was done honestly like within days. And I think it really helped, frankly, for the in the incoming administration, you know, the folks who do this, they're like, you're the experts here. We need a platform because we need a voice. And you heard about that this morning from NASA. We need our online voice. And so here we were able to really think through, you know, at the end of the day, like, does this get across what we want of, you know, restoring American leadership of being ready on day one of confronting a number of prices. And it checked all those boxes. It looked great. We were able to then very quickly move on. I will say like one thing about that that is really important is that this was not a web design that people were approving, right? People were ultimately approving an entire brand. And this was like the brand that the White House would use if you see the president giving, you know, hosting a video or giving a talk or something like that. Like that White House, that drawn White House is used everywhere. And so, you know, for it was less about approving like what is the homepage going to look like? And it was more about like, is this what you want to articulate? So yes. Thank you. Yeah. Great talk. I'm not gonna ask about performance. Don't worry. No. But you talked about brand. And if I, I don't know if I read this somewhere, but I believe I did. I know that this administration was keen on accessibility. Did you want to share any of this sort of work that you did there? Because that tends to not take short periods of time. So... Right. I think that we had two big things that worked in our favor. One is, again, like we had very clearly, you know, directly responsible individuals for different things. And this was the area of Erika who was at WIDI. She is an accessibility expert and was keeping an eye on things as we went. I know Reven's, you know, was building with that in mind from the start, right? So as we're building out these different pieces, right? Starting from the front end, starting with HTML and CSS, right? Getting it right then, right? It is not an afterthought. It is a part of how you build from the start. And that is a big part of it, right? Like a lot of inefficiencies, I guess, right? A lot of, you know, the reason why things drag on so long is when you have to go back and forth all the time, right? You're waiting for somebody to look at something, waiting for them to approve it, waiting for them to come back to it, right? That's where a lot of things get hung up. And I think for each of us to take that personal responsibility and make sure that it was baked into what we individually were doing as well as having that directly responsible individual for it, really allowed us to have it right from the start instead of having to revise it later. Yeah, I would, I mean, I would add just in terms of like a very clear commitment from the top was that, you know, at the end of the day, like he is the president of the American people, all of them. And it's important for anyone to be able to access the government's resources. And that goes not just for White House.gov, but for every government website. And they're increasingly getting very good across the board, which is fantastic. And the culmination of hard work of thousands of people over at this point, more than a decade to really bring substantial change. I will say like, you know, to Helen's point, having even just basic things like everyone understanding what our goals were from the very beginning. So we're not repeating ourselves, making sure that we have color palettes and fonts and everything else that are aligned and ready to go. The site had, and people surely noticed, toggles for high contrast and large text, which is unusual on most all websites. But that was like, that's gonna be a prominent thing. Has an accessibility statement describing like, look, WCAG 2.0, please contact us if you find something that looks a little off. And at the end of the day, it's fundamentally, it is a website with HTML, CSS, and JavaScript. And if you do that well, you're gonna hopefully set yourself up for success. So it was, I take, I mean, I certainly great pride in the idea of multilingual, highly accessible performance, I will say, not that we talked about it, but we did not use that little HP machine from the 90s to host this thing. But yeah, so I was very excited about that. Cool, thank you. Thank you all. Thank you all.