 Thank you. I have the tough task of being before lunch, so thanks for that. This is also the first time I have ever spoke at a conference, so sorry if this goes horribly wrong and you are all hungry. I wanted to get into this with just a bit of background on me. I've been working with WordPress now for about 15 years, mainly in the agency space. I ran an agency for about 10 years, and then moved over to my current role, current role, which is Head of Design and UX at Bigbyte. For those who don't know Bigbyte, we are a WordPress agency working primarily in the enterprise space with mainly publishers, but that sometimes varies. We work with a WordPress VIP goal partner, which allows us to work with some quite big names in publishing, which is really cool, and a lot of global news teams and enterprise brands. Now, obviously, everyone in this room understands what I mean by that, but I have struggled recently to describe what I do. In the past, I would say I'm a web designer, which covers a lot of ground, but now explaining this to outsiders or friends, family, new people I meet. I'm not really sure how to describe what I do, so I'll end on something like I make websites. I'm more broad, but yeah, or even more broad, I work in tech. Now, this doesn't really matter, but it's kind of got me thinking a little bit about how we actually make websites these days in the kind of modern era, and in the past, when I worked in an agency, the process of making a website would kind of look something a bit like this. A client would give a pretty bad brief, and then I'd throw a design together and make it look pretty, and then we'd put some lower mipsum in where the content goes. We'd kind of put that together in HTM on CSS and JavaScript, and then there'd be another process that we'd define as something like put it in WordPress, which would basically mean making a theme, putting in some custom fields, asking the client to log in, and then we've got a website. Now, obviously, that's not the best way to make a website, but we kind of all got by a little bit using that method, but thankfully it doesn't really look like that anymore with kind of modern technologies and JavaScript and React and Gutenberg and headless architecture and agile methodologies. It's kind of, it doesn't look a lot like that, and thankfully we have kind of evolved a lot since then, and especially in this enterprise space that I kind of work in now. But in truth, when I look at it now, I don't really make websites, and this is why I give a shout-out to Aruba Ahmed at WordCamp US, who gave one of my favourite talks there just recently in Washington, DC, and she said, you're not building a website, you're empowering someone else to build a website. And that kind of stood out to me as quite a powerful message, especially in this modern era of working with WordPress and Gutenberg and full-site edit in particular, where everything's a block and we're always breaking things down into component parts, and I think we look at the web differently now, at least I do. And when I see everything in that kind of reusable components and patterns, and that's usually appealing to me, obviously, as a designer, coming from a design background, because there's an obvious correlation there between block-based editors and design systems, and that kind of covers a lot of my client-facing role at Big Bite, working with brands, and typically clients that we work with were brought in as a development partner, so these organisations will have big teams already with a lot of UI designers, UX designers, researchers, QA testers, even sometimes developers, and were kind of brought in not to design a website, but integrate into their teams and use WordPress as another tool in the arsenal, really, of creating content. And I think the changes over the past couple of years to the editor has made really WordPress the best CMS on the market, I think, and I often find myself in pitches to potential clients against other content management systems, and I always like that, obviously, because I enjoy speaking about WordPress, but I do truly believe that WordPress is kind of best place to integrate into any company of any size, so we often see organisations on legacy platforms, often custom-built, and it makes it so difficult for them to complete simple tasks, even something like putting an embed on a page, it's often very difficult, and their editing experience is kind of a lot of fields, it's not flexible, the zero flexibility when it comes to layout, custom post types, things like that, so we worked with Gumtree a couple of years ago, and you can see here we've kind of got an overview of a design system on the left-hand side that we kind of worked with their teams to produce and worked out how we would kind of take that design system, build that out as WordPress components, which you can see in the middle here, and then how that will render on the front end. In previous to this, they were kind of, they were obviously a fairly big organisation, but it was actually taking them like three or four hours to create a blog post even, which is just crazy, and often they would need assistance from developers, and I think the best thing for me working on something like that is to kind of empower users to be able to create dynamic content really quickly and easily, and I think that's where the flexibility of the editor kind of comes into its own, especially at this enterprise level, because it's actually, it's unusual to have this kind of freedom and flexibility at this level, and why shouldn't someone in a marketing team be able to kind of pick up a system and build out a post at a landing page with this kind of level of flexibility, and that's why I think WordPress is kind of best place to do this, so we've used WordPress, we've used Gutenberg from the start really, and we've made, we've probably made quite a few mistakes along the way, and I think one of the things that we've learned particularly recently is this idea of kind of working with the core platform, and I'm really glad that this talk kind of comes after Tammy and Sarah, because they're kind of like hit on a few points that I was going to try and get to, and they probably did it a lot more eloquently than me, but basically the core platform now is so good and so powerful that it really gets you most of the way there, I think, but in the past, particularly when we started using Gutenberg at the beginning, we were building custom blocks for absolutely everything basically, we were struggling to do kind of complex layouts, so we built something like a column builder, or we struggled to make that into, you know, semantic sections, so we'd make a section block, and you know, basically what we've got here isn't too far away from what the core platform looks like now, but it just goes back to this idea that we want to work with WordPress and not against it, and I think the problem where we see clients getting into is when they go against this idea, and that's always where people trip up, and that's not necessarily just the editing experience, that could be anything, it could be the architecture, it could be, you know, not working with post types correctly, or taxonomies, or URL structures, that's always where people trip up, so a big bite, like I say, we work a lot with publishers, and oftentimes that means the front end of the website is completely decoupled from the editor, so in some cases that means a single article could be popular in multiple different websites, could be apps, magazines, it could be even prints sometimes, so in these circumstances we're really only solely focused on the editor, and making that as powerful as possible, with kind of this idea in mind, how do we make creating content easier, more efficient, and faster? So we've worked quite a lot with The Times recently, and obviously the previous talk talked about Headless, and this kind of, this is a Headless system, so again we're kind of, how we use it isn't someone who is, you know, editing the homepage and templates, and you know, custom, you know, editing car features, the journalists who want to write, edit and publish stories, so given this, what can we do to make that car edit an experience of WordPress better for them, so if we take a look at, this is a typical article on The Times side, there's nothing, you know, too scary though, we've just got headline, stand first, featured image, tags, taxonomies, content, so if we kind of take a look at the editor and look how we could use this to kind of get pretty close, I'll be quick, so we can get, you know, quite a lot of the way there, but actually if we take each of these individual elements there is a bit more complexity to them, so for instance this headline at the top, that's actually displayed in numerous different places across the site, so that could be on the homepage or a sidebar, and sometimes that needs to be shorter, so that title actually needs to be shown in multiple places, so we've kind of taken this core platform, and I think that goes back to what you were saying, tell me about understanding this platform and how you build kind of correctly on top of that, and we've kind of came up with this block called the multi title, where you can see at the top, we can switch between article, homepage, SEO, we can shorten that down in the homepage, and then from there, there's other things that we can take from this to kind of make this edit an experience better for them, so you can see that we could maybe take some of the typography, some of those colours, and this is actually what the edit looks like on the Times now, so you can see that you're starting to bring in some of the styles, and you can see how that is more empowering for a journalist to create content in there, because then if we just start putting in blocks and images and text and links, even embeds, as you're building up that article, you almost don't even need to preview, because you're getting a very good idea of what this looks like on the front end, and you can imagine how refreshing that is for a journalist, especially compared to what the word used to use it. Now obviously on top of that, working with a lot of these brands, there is a need to create more custom functionality, we talked a little about revisions earlier, now revisions is something that we've had to put quite a lot of work in, this is what revisions look like now, and you can see going from this kind of very pretty visual editor to this, it's not quite the same, it's almost made more for developers, a journalist is kind of going to struggle to go from there to this to understand what's happened, so we've had to kind of build our own revision system over the past couple of years, and you can see we've taken that idea of that visual editor, brought that into revisions, and we're able to kind of render those in here. Now as I was talking earlier about the columns and going back to kind of using core WordPress, obviously with the phase three things coming, in an ideal world, what we'd like to do is be part of that development of that revision system, bring in some of these learnings, and then hopefully use that as a base back to that idea of working with WordPress, and then if we need to build on top of that we can. Just finally quickly, there is other things that we do that are completely custom, probably never will be in core, or frankly should be, so we do quite a lot of work on the New York Post with Ali, who also work on this site, and you can see the images on this are generally collages, and the process of doing that is kind of how you would imagine it to be, so someone would write an article, put in five or six images, they would send that off to the photo desk, they would take those images, put them in Photoshop, they'd have templates, put those images in it, send it back, they'd upload it to WordPress, it's a very long process, so they asked us if we could essentially do this in WordPress, so we built this collage career, it looks a little bit like this, so we have all the templates on the left hand side that the knees, a slot for each one, you can upload media into it, you can even do cool things like putting in overlays, you can change the position of that, and then we can save that out into the article. So that kind of covers quite a lot of ground, but there's so much that goes into this, and obviously I don't have time to go into a lot of it, but we have, along with some of our friends, these other agencies, produced a white paper recently called WordPress for Enterprise that kind of digs into more of this in terms of security, architecture, scaling, hosting, that you can read, and I think the key thing is the way we're building for WordPress now is probably not going to be the same in five years time, ten years time, and you can even see with things like AI coming at the minute that that's going to change things a lot, and all of us in the kind of agency space experimenting with this, and no one really knows what it's going to look like, but I think, again, going back to that idea of WordPress being this kind of flexible tool, and us being able to stay agile and nimble and adaptive emerging technologies, I still think we are kind of best place to grow with that, so thank you. You can also ask me at lunch if you want, if everyone wants to eat, in terms of the UX of custom feed, custom functionality. Yeah, one thing I was going to say actually, particularly when we're talking about revisions, and one thing I think I need to get better at, and we as a company need to get better at, is kind of contributing all that back into the core community, and I think, I do lean on a lot of that stuff, and even taking patterns and components from Figma, and being able to use that as a base UI, and I think we do that from a development point of view as well. We have some developers from BigBuy who might be able to go into that in more depth, but again it just goes back to the idea of using as much of the core components as possible, so the experience of moving from the core platform to something custom doesn't feel alien, and it feels like you're using the same software, even obviously it is custom. I love your revisions, because I use revisions a lot, a beautiful, very beautiful thing. So what's blocking you? Is it something the community could do to make it easier for you to contribute back, because I'm sure there's not just a BigBuy, but a lot of places that we could actually integrate into the core software, but we need to make it as easy as possible for people to do that. It's a tricky one, and it is something that I've been thinking about a lot, and obviously coming to events like this is pushing me more in the direction of being able to do that, and obviously meeting people and having these discussions. I do quite honestly find it quite daunting a lot of the times to kind of, if you're not already part of that, making that first step in there. So maybe something like revisions, because I know that is something that's high on people's minds. Maybe I think we just need to talk to people who are involved in that process and bring some of our knowledge and learnings. That can be for me from a product angle or development, because with that in particular, we have ran into a lot of problems. It's a very tricky thing to get right revisions. Obviously everything that I've gone through there is around this idea of it being flexible, but actually, a lot of times when you pitch that to clients, you show that to someone who's not in market and they're like, whoa, that's too much flexibility. We don't want people messing about with stuff like that. So yeah, I mean, there is a lot of stuff that we have to do in terms of permissions just on a technical point of view. But I guess it's also getting companies to buy into that vision, because I think people are just not used to that. So I think there is a challenge there of just getting companies to trust that process and trust their users to use these tools that are obviously very powerful. But I think a lot of people's first things think is, well, that can only go wrong. But yeah, there are obviously safeguards that you can put in place there. But yeah, it is quite an interesting area and something that we always come up against with clients.