00:00

topics and so well welcome, everybody to the hallway hangout using site editor in production for client side. It has been so in the post, yeah, I wrote that. That workflow and tooling changes between classic themes and block themes. And because one of the challenges that data is stored in files, design is stored in files, as well as in the database when the user interface, somebody changes something in the user interface. It’s stored in the database. So that makes for an interesting, different way. And yeah, so I would like to go around the room with 20 people, it’s a little hard, but to kind of figure out what are the challenges, or the common issues that agencies on freelancers encounter when they work for clients site? And I just want to kind of, well, who wants to go first? How about in? And it’s next to me? In the, in the gallery view? Okay. Yeah. Yeah.

01:24

Good morning. Oh, for me, it’s Good morning. Hello, everybody. I’ve been actually documenting my journey, as I have just finished designing and developing my first blogblog (versus network, site) theme. And it was a great learning experience. So I have some pain points that I’ve made note of, and some blog posts and sharing on Twitter and stuff like that. But what comes to mind, the most recent stuff that came up to me was wrapping my brain around the difference. Forgive me if it sounds like really lame to some of you, but for me, it was quite a learning experience. So I finally figured out I think the difference between just a simple migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies., where everything’s still in the database, all the customizations that I did with global styling and custom CSS in the additional CSS field, that vs. Two different ways of exporting one with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. approach and one with the Create block theme. Export. I didn’t realize that there would be three different things that would happen. And now Now I realize that

03:02

I muted because I was taking notes, rudimentary notes, but I didn’t want the clicker. Clicker clicker comes right. So I’m glad you mentioned the thank you, and who else wants to go? wants to go next? I think Colin, you had some strong opinions or questions. And that you because it was one of the topics that you also found really hard to,

03:32

we have a long list, I think the biggest one that we’re facing right now is how to restrict the editor. And where that kind of comes in is that we, we need to be able to control brand standards. And there’s a lot that we’ve done in the past with, with GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/., to where we would actually everything would be version controlled. And I know on the last call, we kind of talked about that. And it sparked some conversations and some threads out there. We’ve been experimenting with some some different tweaks from our side. But I think the the other challenge is, sometimes I just don’t want people in the editor. But they still need to be able to edit and so we’re we’re trying to figure out exactly how to handle that. We’ve been playing around with some stuff we kind of built internally using, like the environment configs in you know, I would there’s this dream someday of maybe like a developer and agency user role in in WordPress, but it would be something to where they would have different privileges than maybe an administrator does because our clients they still want to be an administrator. They need to be able to add plugins need to be able to do change administrative settings, but don’t necessarily need them changing things. So we’re trying to access things like that. And so we’ve built a tool that internally, we’re testing, it’s really rough. But basically, if if we enable this, we the editors only available, or somebody that has a developer role. And it’s a role that we’ve added challenges we ran into is sometimes there’s a block or a pattern that’s in the page editor, that is still technically end up changing something in the site editor. And so there’s some overlap there. But that’s more like sync, pattern sync, things like that. So. But yeah, we just need, we need ways to limit control, because we will have like colleges, universities, healthcare organizations, financial institutions, things like that, we may have 50, or 60 people that are in the backend of the site, because they’ve all got their own divisions. But for the marketing teams, they are terrified of what these these people may change in the site. So

06:23

here, so who wants to go next, the challenges? Before we go into solution, I think I would like to have a list of things that are challenges. So we can,

06:36

I’ve kind of got one today, just something having to say is, I just don’t have, hey, I had, I had them, I designed a footer with an image that was part of the theme. And so put that into a tabular pattern. And then link to it from the pattern template. So it’s like a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher person. So I could do the, you know, get theme directory, uploaded it, and then the client or partner made changes to the footer. And then I asked to make some changes to the footer. And when I grab everything down, again, it’s all sort of got like, the links to all the it’s not like relative links anymore. It’s all been created, so like hard coded and stuff. And then I have to try and refix it all. To upload it all again. It’s just very cumbersome. And I don’t know if you know, I’m talking about oh, isn’t that a workshop as a? That’s interesting? I didn’t know about that. Okay.

07:35

So, yeah, Lisa, you raised your hand.

07:42

So sometimes, sometimes, it’s just hard to remember where to find the modifications I’ve done. And I know, I know, they’re all available. And after searching either, you know, customizations to, you know, all templates editor database, you know, there’s just so many places that theme dot JSON, that a change could have been made. And I know, sometimes you can do find it through the inspector. But I do find that while it doesn’t stop me from using the page editor, and maybe it will stop my clients from making changes that are unintended. It sometimes takes a little extra time. So that’s it.

08:31

Yeah, that’s definitely something and Fabian is here.

08:36

Yeah, and more, there are a couple of things. And the first one, if I quote, Brian, who’s also on the call here from his article yesterday, I believe one of the criminal offenses, always is that the navigation block doesn’t have a location anymore, and so that it always just stores the idea of the navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site., which means that there is no way to manage multiple environments, kind of a staging development, production environment that is very typical for kind of the agency world or for working on these larger sites. There is no way that you can say like to use to be able to in classic theme, a this is the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. navigation, this is footer, column one versus for column two, and then assign locations, kind of assign navigation menus to locations. Instead, you can still have individual navigation posts, which are now stored in the database. But the actual Navigation block stores the ref attribute kind of distorts the actual idea of the post in the environment. And that means that as soon as you actually go, you kind of you need to go into the header to assign the navigation. And at that point, you’re already creating an override for the header and therefore locked out of future get updates if you change the header template because the template is already kind of stored in the database now, and that that essentially means that If we’re locked out of get updates for the header and the footer all the time, because it already contains a navigation, and kind of that that is one large thing. Another piece is, I think, Nick, you mentioned that the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ team also has similar requirements where there can’t be any modifications to content on the live environment instead of needs to be pushed up. And so I think the process of having kind of that system where templates can read from file, but then can get overwritten, is, is cool, but it would be cool to have an additional mode where you can say, hey, don’t allow modification of this particular piece, kind of don’t allow override of this template part kind of have that locked down. So it’s, it is still showing up it is available as the preview and everywhere, but it may not be completely editable. And the final thing that I want, I just wanted to raise is with patterns. So I know, they’re really cool things coming with pattern overrides. And kind of synced patterns are so powerful. And now with the new UI where they’re editable, not inline, but you have to click on the Edit original that is a nice enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature., because it differentiates more between that local and global instance. But something that we’re often running into, kind of, for example, if we think of a query block, create a loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. block, we would want to be able to have the card actually be a pattern that we have in the theme that the client doesn’t necessarily need to edit yet, they can edit all the options of the query block, but they don’t have to edit the actual card. Right now you can already create a card pattern. But ideally, we would want that to be a synced pattern that is prompt coming from the theme. And so it’s not editable in there, just having the ability to have synced patterns that are coming from the theme and not from the database.

12:03

And you created an issue for that for the sync patterns coming from the theme. Right? And yeah, I’ll, I hope I’ll find it before the end. Otherwise, I would put it in the in some of those summary or notes. So Mark, I think you’re next.

12:26

Hi, yes, long time. I’ve spoken to a lot of people here. So it’s nice to see faces for a change. I know this is about saying the experience here, I just want to quickly say that we’ve built about a dozen sites so far with the full site editor, few custom blocks, but also a lot on core. And it’s working very well. The clients are understanding it, we’re battling a bit with an agency because they’re having trouble in understanding the concept as a side editor, and the Block Editor. The big problem that we’ve that we’ve rarely come across as come up a couple of times now is I think a few other people have already said is thinking back changes from the live website back into the code base. Especially now because we’re writing out quite a hectic phase at the moment of trying to close off a multisite project with six websites in it. And it’s getting to the stage now. Because when you copy the content out and from the parts manually back into the theme back into the theme, where if you use a creative block plugin, a lot of stuff that gets hard coded back in some of the stuff gets shifted out of HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and into PHP patterns, which I think is a good solution. But it also means that a lot of files get moved around, if there’s a lot of stuff that’s been changed. And then if the client then changes something into more than it’s immediately out of date. So that kind of whole process about tracking changes within the Tech because so much is in the Block Editor in the site editor. It is quite a challenge right now. I mean, I’ve we’re kind of getting rounded, but it’s not not really the ideal solution. On a practical sense, editing the content managing the site, absolutely no problems works really well, including multisite. With Polylang. We’ve We’ve pretty much just stuck it in and it works. So pretty much superbly positive feedback so far, but excellent. For me. My job is a little bit trite, a little bit challenging right now. But that’s what I get paid for.

14:13

Well, thank you. Thank you, Mark. Bryan. Yeah, you have put quite some thoughts on it. And you put it also in writing. So maybe you can, yeah.

14:25

Yeah, I did outline some of the stuff on a blog post recently. So you can see that all of these were all pretty good. So I’ll bring up one that I don’t think has been mentioned that specifically about patterns, which is pattern pattern management. So if you build patterns using the site editor, you can’t really get them into a theme very easily. If you build patterns in the theme, you then can edit them in the site editor, at least as far as I’m understanding. So a solution, for example, is pattern manager which is a great plugin but it doesn’t it’s just a it’s officially a It’s not getting updates. And so I’ve, I’ve kind of forked it to try to get it to work. But then I keep breaking other things. And they use TypeScript, which makes me struggle even more with it. There is an issue, I’ll put it in the chat for create block theme to handle patterns, like just, you know, just basically, I’ll like apart from seems patterns apart from pattern overrides all that stuff. It’s literally just can I build out a bunch of patterns and get them in my theme in a reasonable amount of time. And so I think that even just that first step would be super helpful. So that’s the issue that I posted there. And then I pre basically second, all the other stuff about tempo changes, global changes, global, the lack of navigation, menu locations, things like that. But yeah, that that’s I’ll add patterns in there.

16:02

I never get this right. I’m sorry. So we have a few. Yes, I hate that too, or have the same problem in the chat. The sync patterns we talked about, not we talked about, but we mentioned it. And then the block theme issue that Brian have seen. So we have two people who work on the grid block theme on the call, and I’m glad to hear. So it’s Jason, Chris and Sarah Norris. And you are just working on a new update? Do you want to share a little bit what what the updates are going to be or now that could take some of the pain that we just heard out of the process?

16:58

I’m happy to talk about it at length forever.

17:01

Yeah, you got 10 minutes.

17:06

So so we’re trying to get a release of create block theme. Out wrapped up as close to the release of WordPress 6.5 as we can, one of the biggest reasons is because font management kind of migrated from Crate block theme and into core by way of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. And so we’re attempting to make sure that that experience works natively. And you can use that in combination with great block theme to manage your fonts. So that the fonts aren’t handled by the plugin, the fonts are managed by core. And then you use create block theme to make sure all of those assets are gathered, and put into your theme when you export it or when you save it. So that’s one of the biggest pain points, that was kind of the biggest reason for the release of this time. And then some of the other things that you guys have mentioned, definitely on our radar, or in development. So the image assets kind of getting lost and stuff, we’ve cleaned up how things work there so that when you you know, when you use image assets, there’s there’s stuck in your theme folder where they’re supposed to be consistently. And then one of the other things that nobody has mentioned, but it was it was important for us at Automattic. For the way we have all of our themes are localized all the patterns and all the templates and stuff. And so that’s something that we have integrated into create block theme. Again, more kind of consistently, it’s something that anyway, strings that are in your templates and stuff are now converted to PHP stuck into patterns. And that is, you know how those things can get localized. My understanding is that down the pipeline, there are other plans for how to localize blocks and the content they’re in. But until that happens, we need other tools to do that. So So those are kind of the big things that we’re shooting for in this release. Once we’re kind of over that hump, though, the big thing for me is patterns, patterns, patterns, like management of patterns, being able to use patterns across right now. There’s there’s even in the work that we’ve been doing. What’s great blockchain I’ll do an overview real quick. Just to be able to use patterns as you guys mentioned as a pain point to say I want to be able to work on a pattern and use it throughout a theme user throughout contents. And it doesn’t, doesn’t jive well. And I don’t know exactly what that’s going to mean it for create block theme for Gutenberg for any of that as far as that goes. But it’s an important aspect of theme development. And for that reason, I think that create block theme is the right place to get that started. So that we can kind of work through the possibilities, and allow that to grow into whatever wherever that goes. Like we said, the minute or font management started really with great blockchain before it got into core. And so what we do here with great block team helps all of us early, and then eventually helps everybody. So that’s a quick 20,000 foot view of of the changes a create block theme, though. So you’ve got a link. But it’s really just I like to think of it as like development mode. Like you, you open a browser window, and you can open development mode, gray block theme, to me is is a place where we can add a development mode for for themers for theme development of using WordPress, so that you can use the native side editor tools to build your theme. And then export that. As zips. As you know, with whatever your development workflow is, I don’t export zips, I don’t use those, the development workflow that I have is get. So I want all of my stuff saved, where my thieves themes are and be able to work through that. And so want to make sure that that work workflow works, but also exporting zips. One thing I wanted to mention with this next release, we’re actually planning to probably eliminate the WP adminadmin (and super admin) interface. Most of you’re probably most familiar with that. But we’ve been migrating all of the capabilities of a black theme into the site editor itself. So that’s where all future, everything’s gonna go. So there might be like some, some some documentation or maybe some wizards and like, Intro workflow in WP admin, but it’s just a whole lot easier to develop directly in the site editor, we’ve, you know, right at the source. So that’s where it kind of everything’s gonna grow. From there. So.

22:28

Well, thank you so much, Jason. Any questions for Jason now that some of you already use the Create blockchain quite a bit. Mark mentioned it. And Brian mentioned it and n as well say anything that you would like to ask all kind of have a feature requests? I hear See, Colin, maybe that’s not the question that you wanted to talk about. But B, go ahead.

22:59

No, it’s absolutely on the credit clock thing. It was a game changer for us. Like without that, it was really tough for us to be able to actually adopt, being able to use Full Site Editing and unblock themes as an agency. So thank you all for the work that you’ve put into that feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. in less this is already there. And I just haven’t seen it, but because our development workflow is shifting a lot to where sometimes we’re actually finding ourselves building in the browser in a staging environmentStaging Environment A staging environment is a non-production copy of your site. This is a private place to build the site -- design, copy, and code -- until your client approves it for production or live. Sometimes used in addition to, or as a Development Environment. where we used to be, you know, building in a local environment and things like that. There’s, with our workflow, we virtually control everything. And what we’re running into is an issue to where we actually have to maybe go enable or disable functionality inside the theme dot JSON. And then, you know, commit that, push it to staging, then be able to continue our workflow. It’d be awesome if there was just a away with create block theme or something like that, where there was like a theme dot JSON editor, to where we could just modify whatever those features are that we need, turn it on. It’s

24:16

actually our stretch goal for this release. We’ve already started development of a JSON editor. I can’t promise that it will be in the next release. I can promise it it is in Development Act development. That was actually my morning. That’s what I’ve been working on it. Big part of Sony.

24:33

I think I’m done.

24:38

Yeah, that’s awesome. Thank you. Just wanted to note from the chat, that granular a more granular export would be also quite feasible for like, be able to only export a template from the overrides or something like that. So we have more hands Justin, then Alex, and then do a little case study. Yep. Okay.

25:03

Yeah, just just because we have both Brian and the team, the Create block theme team here. I’d like to invite Brian to take the work that he mentioned, forking template meant our the fighter manager. Go ahead and like, bring it into the ticketticket Created for both bug reports and feature development on the bug tracker.. And just share and see if we can, can collaborate there. I’m sure the team will welcome that.

25:34

Yeah, I think one big difference is pattern manager, they basically load like a fake Block Editor with a fake Custom Post TypeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept., and, and do all this extra work. So it’s, it’s like, the basically, it’s like two completely separate approaches, one through the site editor, one through like a MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. kind of post type that they auto generate every time they kind of load all your patterns from your team. But I think it’s worth looking at those two things, because I think it’s two different approaches. But there might be some crossover.

26:00

Yeah, at least Yeah, at least have the conversation going there. So you know, for comparison.

26:10

Yeah. Alex?

26:17

Hey, thank you for hosting this. So I have very slowly started again, into using the full site editor, I have a crowdfunding plugin that we’re building a blog theme for that leverages the site editor, and, you know, it’s it, it’s definitely been a difficult ramp up for me. So I appreciate the work that that’s been done. And it’s improved a lot. So So I want to make sure to say that, um, I think it so there, there’s a pair of questions I have, and I guess, they’re they’re both kind of philosophical, and maybe for the room at large. But I, you know, it is building sites through the editor and stuff. Obviously, not a lot is not as much as done through version control, as it used to be like, you can still do patterns through version control to some degree. So part one of my question is, you know, how are people approaching that to ensure that they don’t lose their stuff, or their, you know, their templates, and, you know, I use, I do use a page builder to kind of manage builds, we, my team uses bricks right now. But you know, like, I’m trying to, you know, stay nimble to keep up with the advances of the site editor, the Block Editor and such. And then the other part of it is to is like, as I guess, as it as far as the make team goes, or whatnot, whenever I think about the site editor and the Block Editor, I kind of think about them as separate things. But I realized that all the work is pretty much shared. So you know, I don’t know if that’s a valid question or not, but it I’d be curious to know, like, what what the thought is, you know, are these kind of the same thing? Are they kind of separately develops pieces? Or is it a little bit of both?

28:24

Any buddy has an answer for that question.

28:29

Last question.

28:32

Say that again, Alex, what’s the question?

28:34

So that Okay, the second part of the question is, is the Block Editor and the site editor? Like, are those considered one in the same? Are they two separate projects? In that’s just a bit of curiosity that I have?

28:54

They are merged. They they’re heading. Singularity. We’re headed, we’re heading to the singularity. The Block Editor was built first, you know, in the launch of everything and

29:05

post. That’s right. Yeah. Yeah, you’re right, you’re.

29:13

So right now, actually, 6.5 is the first release where there’s a lot of divergence happening where a lot of the features that were initially kind of developed in the side editor are being brought over to the post editor and kind of the way that you can think of it. The entire Gutenberg system is built in these individual packages. There is one Edit Site package, there’s one edit post package, and there is one or editor package. And a lot of the features can have inish originally only that edit kind of the Block Editor of the post editor. That was the first piece and then a lot of the new discoveries and the new explorations happened in the site editor. And now both of those are converging a lot of functionality into that main just editor package. And so you’ll see in 6.5, for example, the ability to preview the template while you’re editing the post, but all of the template things are completely locked down, and stuff like that. Those are all things that are coming from the site editor into the post editor, and where the code bases getting more unified again. No, no, no, that makes that makes sense. Because I was kind of thought of them as two different things. And when I talked to colleagues about it, it’s like, well, no, they’re, they’re the same. And it philosophically they both felt very different to me, but so thank you for, for explaining that. And then I think just for the room, like just kind of, you know, managing stuff, that managing layouts that are kind of held in the database, like, you know, what are some additional precautions that you won’t take or, you know, specific approaches that you take to kind of building in in the browser as much as we are now.

30:57

I have one side tangent that I wanted to mention here, while we have 30 people in the room is that there is a PR that thinking about metal boxes differently, too, because the post editor is still even if a metal box is there, because a plugin as a custom fieldCustom Field Custom Field, also referred to as post meta, is a feature in WordPress. It allows users to add additional information when writing a post, eg contributors’ names, auth. WordPress stores this information as metadata. Users can display this meta data by using template tags in their WordPress themes. or for any other reasons, the post editor is not loaded in an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. And some of the features that needs to be that comes from the editor and the post editor to come together. It needs to be loaded in an iframe. So there is the idea that all the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes could be in a separate modal that needs to be activated by the user. But then the post editor can be loaded in the iframe that has a lot of advantages. One is definitely styling, but it’s also consistent behavior and all that. So the if somebody wants to look for that PR, there is we need a lot of people testing that, to see what would if something breaks when that modal meta box kind of screen is introduced, before it’s introduced, so to speak. So I will ask everybody to kind of go there. And think about that in their projects as well. I’m gonna go look for that. PR. And next already in the chat. It’s in the chat. You’re also good. Thank you so much. So next up is and she has waited patiently through line tangent.

32:48

Okay, I think I want to circle back a little bit to the design part of this experience for me, because I’m a designer, these features and functionality. They’re great. But I think a lot of my pain points coming into the block. Theme experience for the first time was the UI. We all know the navigation is it’s it’s embarrassing. I mean, I don’t know why there’s so little attention being paid to it. It’s just, it’s it’s really bad. And then, personally, the additional CSS field is it’s, it’s, I can’t breathe when I use it, I hate it. I absolutely hate it. So I’ve got this work around that I use so that I can then integrate with Git and the repo and and that brings us again, back to the whole idea of version control. So anyway, that’s something I wanted to bring up today, because I think sometimes we get very wrapped up in this feature and that feature in the code and that it uh, and for me, what holds things back sometimes is just the experience itself and how horrible everything looks.

34:28

Harsh words, Brian, thanks for listening. Well, thanks. And but I get this additional CSS is if you don’t have a code edit, color coded editor that kind of led to see Yeah, it’s really hard, but there is relief coming for that part. I saw. I’ve seen the PR, and I know that quite a few people are working on it at the navigation. I think that has been a progress working progress for two years now. But yeah, I hear you, Brian,

34:59

would it be would it’d be out of the realm of possibility to have some sort of integration with the additional CSS field with a, like Visual Studio code or some actual editor, I don’t know what goes behind that. But some sort of integration. I

35:22

kind of feel like if you’re actually integrating with, like an editor on your computer, this probably gonna be more into like, what we might call plugin territory. Not something that I don’t know if I don’t know, core has surprised me before with features. But I doubt we bring that sort of integration, but I could see us just improving the UI around like what you have in the back end. And the side editor, I think that’s where the focus would have to be. I actually haven’t really used that I just use CSS files on my theme. So I do need to play around with that and see how challenging, challenging it is. I don’t I’m not sure.

36:14

It’s a little hidden. That’s one thing, and it’s just plain text. There is no color coding. There’s nothing in there. There’s also no linting. Yeah, that it would help you with the, with corrections of things. Yeah. Brian, Europe.

36:33

Yeah, I actually wanted to build on that conversation and the previous one about metal boxes. And I just wanted to point out, I was going to bring up an issue with the metal box, pull request. And then I saw that Phoebe and had, of course, already commented on it last week, saying exactly what I wanted to say, which is that if you click on the link, I don’t know if I can share. But if you click on the link to go to the the idea of meta boxes, for example. And you scroll all the way down to the bottom of the PR there is this design concept that is really about like rethinking how you think about the Block Editor. And right now the metal boxes, they want to have like another button on the right hand side of the screen with another you know panel or a modal that takes over the screen. And it’s sort of just not the best experience. But if you go all the way down, as Fabian points out, there’s this really great redesign where the left hand side of of the site after that black bar will kind of like expand out, and more functional settings and things like that can really be handled there things like custom fields, things like if you’re a WooCommerce product, all your product details, all that sort of stuff. And then there’s the site itself. And it’s this kind of like three tiered thing. And I really think that if this is the path that they go, and you know, at least generally, getting things out of that little right hand sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., like the additional CSS and all these sorts of things, where you know, at the end of the day, it’s it’s nice that it’s in this tiny little window, and you can see your content, but sometimes you just want to make something big. And even the font library has this issue where it’s like, it doesn’t fit in this little sidebar, so then they just stick a modal in front of you. And it’s not the best experience. But the new stuff coming there I think is really handy. And I think it’s I think a lot of people will if you know, I think it’s a while out, but I think it’ll hopefully solve a lot of these UI issues by giving a sort of breathable area for things that is not your content and getting the stuff out of these two little narrow sidebars. So I would say click on that PR and scroll all the way down to see an example screenshots or watch the video in the outreach channel, where Saxon goes, like really in depth into what some of these ideas could be.

38:36

Yeah, yes, thank you for bringing that up. There’s this video I shared in any outreach, it’s 18 minutes, but it’s very kind of it walks through the prototype on figma. And how the admin design kind of is evolving. And it’s a really, really interesting video. So but it’s also not, for now, yeah, it’s kind of a little ways out. Because as long as it’s in figma, there was not a whole lot of development there. But you can see it in the in Gutenberg 18.0, you see this three pane window already with the template when you do a list view and layout there. So that’s at least a precursor. Mark.

39:25

What I was gonna say quickly is that I was just in Jessica’s, I think she uses the additional CSS field. And I know pretty much every hobby developer, shall we say that knows a little bit of CSS immediately uses our field they never use. They never use their own CSS files, for obvious reasons. It’s just easier to copy it into the field. I’m not entirely sure if I’m mistaken that the original version in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. actually did have linting and highlighting in the same way that code pen does. So that’s I think library scripts which can be used if it’s not already in planning. The other thing about the general idea of now skating around and doing stuff, I think we’re kind of in a little. We’re very focused on this stuff. And so we see all of the little details. But if you actually presented to a client and somebody that is open to learning new stuff and show them, this is how you do it and explain the difference between the page editor, post editor, the site editor, the styles editor, most of them get it most of understand it, as long as they’re not coming from a page builder, from another from another CMS, or from historic WordPress, where you had to build everything with PHP, it’s kind of it needs a little bit of open an open mind, for people to go, right, I’m gonna learn them learn something new. It’s a huge system. There’s lots of complexity to it. And the experience that I have with just completely technically illiterate users, and also agencies that we work in partnership with design agencies, most of them I would say, after a couple of weeks, they kind of get used to it. So it’s not as bad as all of the negative feedback would suggest. Apart from the navigation block, but we all know that so I don’t need to say anything about that.

40:59

Yeah, I think the hardest thing in life is to unlearn things that you have with with great effort learned in the first place. So yeah, it’s it’s when you switch programming languages for developers, or if you switch from one place to, to building something to a different place with a different UI and different metaphors. Yeah, we are in 15 minutes. What are the other topics that we might have? Wanted to talk about? That we haven’t touched it? Was there anything else that so there was a lot of chat, chat, things, I didn’t pay that much attention. But I think it’s

41:55

one thing that I wanted to bring up that I think is an interesting thing, where it may make, it may even make sense to kind of set a line on one vision higher up in project leadership. And that is, I feel like for the last two or so years, a major focus of the project has been how, how easy it is to switch from one theme to another kind of how how to make it super easy with block themes, to make them to allow you to switch between different block themes. And that actually led to things like the menu location getting removed from the navigation block, because it is easier to switch between one block theme and another block theme, if it isn’t just a random, unique string that somebody can give for the menu location, but instead just have a standardized way of doing it. And there, there are quite a few of those. Kind of the fact that in that kind of when you have a custom font sizes, or custom spacing sizes, if you have less than five of them, then it shows t shirt sizes. And the actual letters in the t shirt sizes are just pre picked from from core. And there is no way to customize any of those pieces. And I feel like we’re often struggling between how can we make How can we build these features so that they’re super changeable, kind of optimizing so that you can super easily switch between themes. But then also these environments where that is just never going to happen. These are purpose built custom built themes. And I think that divide that those two completely opposite worlds are creating is at the root of a lot of the issues that a lot of the people in this room I often hear talking about. And I’m wondering whether kind of either project wise, we’ve just made the decision that our main focus is democratizing publishing, and therefore everything should just be super easy to switch all the time. So we just have to work around it or there’s a middle ground that kind of helps helps make it easier on both sides.

44:15

Some interesting aspects now I think if we had more tools to switch off things that what Colin mentioned before that needs to be not everybody wants to have their brand design be ruined by deadlines. Yeah. If we had a little bit more additional features like that would be really helpful but in one place, not put it in theme JSON here and put it in, in a PHP function. It’s called there. I think that will be also quite helpful in that Yeah. Kathy she raised her hand for a while.

44:59

I never know if the audio works. So I don’t know if you can hear me like, oh, that’s like the first time literally ever that has worked. Okay, so this might be a little bit tangential. So I hope you’ll indulge me but I’m a, I’m a plugin helper and not, you know, building sites necessarily yet. And I guess I just kind of want to ask or raise the issue of like, what’s coming down the pipe for making it maybe easier for plugins to start registering? site editor, templates. Because not all content. I mean, the the theme ultimately can have an can provide ways to display content. But you know, not every theme will have compatibility for your plugin and plugins have lots of content that we need to provide. And we’re going to need to provide ways for people to customize that. So I just kind of wanted to raise that issue of like, what’s happening there? And again, I’m sorry, it’s a little bit tangential to this conversation. But

45:59

it’s a very good question that come up. Nick, do you have a thought about that?

46:08

too, but I do, like WooCommerce does. But I think that they’re it’s very convoluted to do it.

46:15

It’s extremely convoluted. Yeah.

46:18

So I think it’s interesting, because something I haven’t explored, but probably should. But so technically, it’s possible. But it’s not something as simple as register template partners or something.

46:31

Yeah, that’s, that’s about what I have found in the past week of kind of like poking around in this and sort of why I wanted to be on this call and raise that question, because it’s like their plugins

46:45

would patterns sit that that kind of content needs? I mean, I know they’re clearly very different than templates, but

46:58

not necessarily. Oh, yet.

46:59

Like patents? Yeah, yeah. So yeah, we’re just talking about wanting to create, like a template from the plugin. Like, if you have a Custom Post Type, maybe you want to? I’m working on a little something for the developer blog. Hopefully, that might address some use cases, not all. So hopefully, I say I’m working on I will be working on it soon. Hopefully, we’ll have like a solution for some use cases. Yes, it’s a little convoluted. And you do have to really dig into what’s actually happening with templates under the hood. But we’ll see. Feel free to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. And we can kind of chat through some of your issues there. I’m happy to at least see if I have a solution. Cool, thank you.

48:10

Any other thoughts? And about that topic? So I know, we raised it about version control. And then we didn’t really dig into that. So what is was somebody had a workflow that goes from create block theme, to get and, and then deployment. And then when there was something changed? On the client side, it goes back to export things, or what’s the Eucalan? Who mentioned that?

48:45

Yeah, so that’s kind of our workflow. Right now. We’re actually working on a tool to better surface things that have changed. You know, I think that’s one of the challenges right now, especially on a large site. From a database standpoint, you know, we are, we’re able to go in and see, you know, what the different revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. are, there are post types that are associated with all the different, you know, customizations, and things. And then you can see revision history and stuff. So what we’re trying to do is find a visual way to surface that. So that as a developer, if we log into the site, we can see, oh, look, we’ve got stuff that’s actually not committed. So we’re not tracking this or we’re not seeing that change. There’s places that we can go within the editor to where you can actually see, you know, like, it’s slightly inconsistent right now, but it’s, you know, you can see like, hey, this has been modified or you can, you know, hit the clear customizations or, or things like that, but what we’re doing is we’re trying to surface those, so that we’re not just having to do a blanket, you know, log onto the site. It’s been a week. We’re going to jump in there. Let’s just do an export from Create block theme because I know we’re not supposed to use create block theme in production. But we do. And it’s a, you know, we, we take that in and kind of work from there. So that’s kind of been our workflow. Our previous workflow was always content was on production code started local into depth into staging, so code went up, content came down. And we’re really trying to figure out how to get as close to that as possible. The we use tower internally for for control, or version control GUI, they’ve got an incredible feature to where you can actually select individual lines in a file that you want to commit. And so that’s been really, really helpful for us, because we may do a, you know, an export or an overwrite of the theme with create block theme in our local environment. You know, my theme, that JSON, because one of the challenges we run into is a client will go into the site editor, then they go to the Style Editor, and then they start changing things in the blocks over there. And so we’ll all that gets written to a theme dot JSON. So we may have something that’s I think, dot JSON that we’ve tried to modify. And when we deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. it, we overwrite that so we have to be careful about or I’m sorry, we don’t overwrite it, we deploy it, but nothing changes. And so then that’s where we would find out. So what we were doing is pulling that down, and then we would grab the individual pieces. So instead of just saying, you know, the updates that theme that JSON, we want to know, okay, this specific block defaults were updated, and then we can commit that piece. So that’s been that’s been incredibly helpful.

51:56

I imagine. I imagine Lisa would really love that was Lisa, who said that it’s hard to figure out where actually something changed? And yeah, so it’s been really helpful. Yeah. So are you working on this to make it also available at some point or yes,

52:18

yeah, that’s our that’s our goal for surfacing right now with with get tower, the commit workflow, that is something that you can absolutely do right now. We’ve kind of gotten into a workflow that if we know somebody else is managing the site, where it you know, before it was always ego, and you’re going to work on something we’d use, like WP migrate, pull down the database, get the latest and greatest in maybe media files if we need them. Now, we kind of do the same thing. But then the next step is overwrite theme with the Create block theme plugin, and then open up get and kind of see what’s, uh, let’s change changed.

53:02

Looks want. Yeah. Well, go ahead.

53:07

The one thing I’ll say that has kind of been a caution for us on that is that if you when you do the Create block theme, and then overwrite the thing, if you just discard those changes, because you’re like, oh, I don’t need that. Well, it did actually remove those changes from the from theme. So you got to be careful with that.

53:32

Could you say that again, I want to make sure I hear that fully.

53:37

So

53:38

in JSON, you may be able to correct me if I’m incorrect, or like from wrong on this. But it’s like, when you use the overwrite theme, it actually it goes and grabs all of the settings that have been saved in the database, and then it pulls them down into your themes. Well, it’s no longer in the database. So if in a Git workflow, you’re then to just say discard changes, because you didn’t actually need that stuff. Well, now you’re in a new system that doesn’t match production anymore, and so you need to pull down again.

54:13

Okay, so we are two minutes left. I think we’re, I think we all can talk about it another two more hours or something like that. It was really insightful to have you all here and talk about these things. Especially for the kind of free okay, we’re all to kind of put it all together in one in one transcript of a session like this, too, and that’s what we’re going to do. We’re gonna share the recording and we’re gonna see the transcript and some of the tools and links that were in the chat will also be published. It’s probably take until after Easter, but that’s What I wish you is a wonderful weekend. Thank you so much for your time here and have a wonderful weekend and Easter. And I hope we do this again in in the in a few months, and kind of see what’s the status and what has changed. I’m also looking through the GitHub repo and see if we can match up some of the requirements with PRs that are already the people are working on. And I probably need to ask Fabian if he has some. Some of them he probably wrote some of them. So be well, and thank you so much for all your time, and until the next time, and I see you in the outreach channel. Take care bye

17:04:22 From justintadlock : Is Jason going to play us a song?
17:04:45 From Sarah Norris : Reacted to “Is Jason going to pl…” with 🎸
17:04:54 From Jeff Chandler : Reacted to “Is Jason going to pl…” with 🎸
17:04:56 From Jason Crist : Doing something with my hands keeps me focused. 😛
17:05:23 From justintadlock : Today’s topic: https://make.wordpress.org/core/2024/03/19/hallway-hangout-using-site-editor-in-production-for-client-sites/
17:06:02 From justintadlock : Reacted to “Doing something with…” with 👍
17:07:47 From Jeff Chandler : Oohh, Restricting the editor is a hot topic.
17:08:10 From Lisa Snyder, @silverhoopedge : restricting like “block locking” or something else?
17:08:29 From Lisa Snyder, @silverhoopedge : pattern locking?
17:09:06 From Kristin Aus : Reacted to “Oohh, Restricting th…” with 👍🏻
17:09:08 From justintadlock : Replying to “restricting like “bl…”

It’s one possibility, but there are many ways you might want to restrict. Locking, theme.json, some filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., etc.
17:09:34 From Lisa Snyder, @silverhoopedge : Reacted to “It’s one possibility…” with 👍
17:09:47 From Brian Coords : “templateLock”:”contentOnly” is another similar tool here
17:10:02 From Lisa Snyder, @silverhoopedge : Reacted to “”templateLock”:”cont…” with 👍
17:10:08 From Kathy : A locked down version of the editor came up today on Twitter. I think there’s a discussion happening here: https://github.com/WordPress/gutenberg/issues/60021
17:10:27 From Jennifer Kelly : Cullen that sounds awesome!
17:11:18 From Jeff Chandler : Nick Diego covered this topic in 2022 in a Workshop, but it may be worth revisiting https://twitter.com/nickmdiego/status/1590690057144348674
17:12:49 From Brian Coords : I forgot how to raise my hand 🤚
17:12:57 From alex vasquez : Same haha
17:13:27 From justintadlock : It’s under “Reactions” in the bottom toolbar
17:13:30 From Belinda : Its the same problem with synced patterns
17:13:55 From Brian Coords : (Agreed – I forked this plugin to work with classic menu locations: https://wordpress.org/plugins/classic-menu-block/)
17:13:56 From Belinda : If you have a synced pattern in a template you have different ones on local/dev/prod
17:15:27 From Belinda : Why can’t we used synced patterns in the block editor?
17:15:43 From Fabian Todt : Reacted to “(Agreed – I forked t…” with 👍
17:16:48 From Fabian Kägy : This is the issue for Synced Theme patterns: https://github.com/WordPress/gutenberg/issues/59272
17:16:53 From justintadlock : Reacted to “This is the issue fo…” with 💯
17:17:08 From Cullen @ Matchbox : Reacted to “This is the issue fo…” with 💯
17:19:03 From Brian Coords : https://github.com/WordPress/create-block-theme/issues/287
17:22:20 From Cullen @ Matchbox : Two other issues we encounter often:

• We’re often unable to find posts in large menus that include multiple post types.
• It’s difficult to surface what changes were made in a production environment so that we can then bring them back into the git repo. (We’re working on a plugin for this)
  17:23:33 From Jeff Chandler : What’s “Create Block Theme” anyone have a link that explains it?
  17:23:55 From justintadlock : Replying to “What’s “Create Block…”

https://wordpress.org/plugins/create-block-theme/
17:23:56 From Sarah Norris : https://wordpress.org/plugins/create-block-theme/
17:24:03 From Jeff Chandler : Reacted to “https://wordpress.or…” with 👍
17:24:05 From Sarah Norris : https://github.com/WordPress/create-block-theme
17:24:07 From Jeff Chandler : Reacted to “https://wordpress.or…” with 👍
17:24:07 From Birgit Pauli-Haack : https://wordpress.org/plugins/create-block-theme/
17:24:21 From Birgit Pauli-Haack : Sarah beat me to it 🙂
17:24:41 From Sarah Norris : Reacted to “Sarah beat me to it …” with 😁
17:25:00 From Jeff Chandler : Thank you for all the links 🙂
17:25:19 From justintadlock : Reacted to “Thank you for all th…” with 😂
17:25:34 From Fabian Todt : Reacted to “Thank you for all th…” with 😂
17:25:45 From Jeff Chandler : wow, already has more than 10K active installs
17:26:59 From Fabian Kägy : It would be cool to have more granular export options in the site editor.

Like being able to only export one template (override the one on disk) instead of always having to export the entire theme
17:27:11 From Hans-Gerd Gerhards : Reacted to “It would be cool to …” with 👍
17:27:14 From Jason Crist : Reacted to “It would be cool to …” with ❤️
17:27:32 From Brian Coords : Granular export options, save to the filesystem directly on save, WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ command to export
17:27:33 From Mike McAlister : I’d love to see Create Block Theme have a dedicated space on .org. And if it’s going to be prominent going forward, we should look at rebranding it to something more user friendly and communicate its value better.
17:27:40 From Brian Coords : Reacted to “I’d love to see Crea…” with 👍
17:28:01 From Jeff Chandler : Replying to “I’d love to see Crea…”

This is the first time I’ve seen or heard about Create Block Theme 😛
17:28:13 From Mark Howells-Mead : Yes please! 😄
17:28:31 From Mike McAlister : Replying to “I’d love to see Crea…”

My point exactly. Let’s turn this from a niche themer tool to something more widely known and promoted.
17:28:32 From Mark Howells-Mead : Awesome indeed!
17:28:55 From Vicente Canales : First draft of a JSON editor for CBT 🙂 https://github.com/WordPress/create-block-theme/pull/520
17:28:55 From Belinda : +1 for granular export
17:29:18 From Sarah Norris : Reacted to “First draft of a JSO…” with ❤️
17:30:06 From Kristin Aus : Reacted to “+1 for granular expo…” with 👍🏻
17:30:39 From Cullen @ Matchbox : Reacted to “It would be cool to …” with 👍
17:30:43 From Kristin Aus : Reacted to “My point exactly. Le…” with 👍🏻
17:30:49 From Mike McAlister : When creating Pattern Manager, we had to do some really fancy footwork to do some of the more advanced pattern management. That’s why we ended up with the dedicated editor instance, etc.
17:31:17 From Birgit Pauli-Haack : Reacted to “I’d love to see Crea…” with 👍
17:31:38 From justintadlock : Reacted to “When creating Patter…” with 👍
17:32:00 From Hans-Gerd Gerhards : Reacted to “When creating Patter…” with 👍
17:32:13 From Brian Coords : Replying to “I’d love to see Crea…”

It’s mentioned inside the docs, but that’s about it https://developer.wordpress.org/themes/getting-started/quick-start-guide/#using-the-create-block-theme-plugin
17:32:37 From Cullen @ Matchbox : Reacted to “First draft of a JSO…” with ❤️
17:32:54 From Mark Szymanski : Great question Alex
17:33:16 From Jeff Chandler : Reacted to “Great question Alex ” with 👋
17:33:20 From Mike McAlister : Block editor, site editor, and admin UI, all coming together slowly as one experience.
17:33:39 From Nick Diego : Reacted to “Block editor, site e…” with ➕
17:34:47 From Jeff Chandler : Replying to “Block editor, site e…”

Make it come sooner 🙂
17:35:40 From Fabian Kägy : The meta box ticket: https://github.com/WordPress/gutenberg/pull/59242
17:35:48 From Jeff Chandler : I think Brian shared something about the metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. stuff a few weeks ago
17:35:48 From alex vasquez : Reacted to “The meta box ticket:…” with 👍
17:35:57 From Brian Coords : Reacted to “The meta box ticket:…” with 👍
17:35:58 From justintadlock : Reacted to “The meta box ticket:…” with 👍
17:36:02 From Cullen @ Matchbox : Reacted to “The meta box ticket:…” with 👍
17:37:13 From Mike McAlister : RE Alex’s question, I build in the editor, but try to keep as much as possible in a git workflow. You can use tools like Create Block Theme and Pattern Manager to write to disk. There is still a lot of work to do on a cohesive workflow there.
17:37:33 From Fabian Kägy : @alex vasquez regarding your question:

It depends a bit on the client. But for a lot of sites I think of the site editor as a development tool. Clients are not administrators and so they don’t typically interface with the site editor.
17:38:10 From alex vasquez : +1 for what Ann is saying. Thank you for saying it, Ann.
17:38:11 From Fabian Kägy : Replying to “@alex vasquez regard…”

And yeah using it as a development tool and always exporting things back into git
17:39:14 From Cullen @ Matchbox : Replying to “The meta box ticket:…”

Does going to Three dots > Preferences > Panels and disabling the panels bypass the iframe issue or is it persistent even with those panels disabled through preferences?
17:40:03 From Fabian Kägy : Replying to “The meta box ticket:…”

Sadly even when panels are not visible they still block the iframed editor
17:40:31 From Kathy : Wait… where the heck even IS the custom CSS area?
17:40:33 From Cullen @ Matchbox : Reacted to “Sadly even when pane…” with 👍
17:40:48 From Mark Howells-Mead : In the styles editor, behind the three dots.
17:40:52 From Jessica Lyschik : I use the Additional CSS frequently for all these things that we can‘t change via design tools or the theme.json.
17:41:03 From Anne Katzeff (she/her) : Me too, Jessica.
17:41:08 From Fabian Kägy : @Brian Coords we are the same person 🥸
17:41:12 From Wes Davis : Chiming in to say that Navigation is one of the biggest pain points for me too — it feels like a step backwards to have to tell clients that used to be able to easily manage their own header menu links with the “classic” menus, that with their fancy new block editor, they now have to ask us to make updates to header/footer menus for them.
17:41:12 From Jason Crist : https://marketplace.visualstudio.com/items?itemName=chrisrhymes.gutenburg-comment-highlight
17:41:19 From Amy Dalrymple : Replying to “@alex vasquez regard…”

I have dipped into this for my team – I have folks creating layouts and setting up pages in both production and staging environments. I didn’t see an easy way to keep environments synced. Not everyone one my team is a developer and don’t have access to Git. I abandoned any conversion to Site Editor for us pretty quick, unfortunately.
17:41:38 From Fabian Kägy : Replying to “The meta box ticket:…”

https://github.com/WordPress/gutenberg/issues/52724
17:41:45 From Belinda : Reacted to “Chiming in to say th…” with 👍
17:41:50 From Wes Davis : Replying to “Chiming in to say th…”

With their fancy new block editor SITE, they now have to ask us to make updates
17:41:57 From Hans-Gerd Gerhards : Reacted to “Chiming in to say th…” with 👍
17:41:58 From Fabian Kägy : Replying to “The meta box ticket:…”

Ia raised that last June 😂 I think there could be room for improvement there
17:42:18 From Cullen @ Matchbox : Replying to “The meta box ticket:…”

I love this UI concept.
17:42:28 From Jessica Lyschik : It would be nice if the Additional CSS would be directly linked from the global styles panel instead of being hidden in another menu
17:42:40 From Hans-Gerd Gerhards : Reacted to “It would be nice if …” with 👍
17:42:50 From Chris Reynolds ⚡️ : Reacted to “It would be nice if …” with 💯
17:42:54 From Mike McAlister : Saxon is doing some really excellent work on the design side of things.
17:43:00 From Brian Coords : Reacted to “Saxon is doing some …” with 👍
17:43:22 From alex vasquez : Replying to “@alex vasquez regard…”

I have a specific way that I like to work when building layouts and the site editor kinda flies in the face of that. I don’t want to pick on the site editor too much. But the amount of clicking around drives me kind of nuts. It would be nice to have a better interaction with global class management and assignment to blocks as part of the site editing experience (but not the block editing experience).
17:43:32 From Brian Coords : Reacted to “It would be nice if …” with 💯
17:43:44 From alex vasquez : Replying to “@alex vasquez regard…”

And thank you, for sharing this Fabian. I appreciate. =)
17:43:45 From Jeff Chandler : It’s awesome to see all of you sharing experiences and ideas and working towards improving things for everyone. As a user, I appreciate all of the work and time you all invest into WordPress.
17:43:51 From Jessica Lyschik : It did in limited ways
17:43:56 From Anne Katzeff (she/her) : What about styles.css for custom styles, esp. for a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/.. It’s not enabled out of the box. And I can’t figure out how to enable it.
17:44:00 From Cullen @ Matchbox : Reacted to “It’s awesome to see …” with ❤️
17:44:00 From Sarah Norris : Reacted to “It’s awesome to see …” with ❤️
17:44:05 From Jessica Lyschik : Reacted to “It’s awesome to see …” with ❤️
17:44:06 From alex vasquez : Reacted to “What about styles.cs…” with 👍
17:44:10 From Brian Coords : Reacted to “@Brian Coords we ar…” with 😂
17:44:12 From alex vasquez : Reacted to “What about styles.cs…” with 👏
17:44:14 From alex vasquez : Removed a 👍 reaction from “What about styles.cs…”
17:44:30 From alex vasquez : Reacted to “Chiming in to say th…” with 👍
17:44:46 From alex vasquez : Replying to “The meta box ticket:…”

This is great!
17:45:08 From Anne Katzeff (she/her) : Reacted to “+1 for what Ann is s…” with ☮️
17:45:21 From justintadlock : Replying to “What about styles.cs…”

Depends on the parent theme. Explained here: https://developer.wordpress.org/themes/advanced-topics/child-themes/#loading-style-css
17:45:55 From Anne Katzeff (she/her) : Replying to “What about styles.cs…”

2024 is the parent theme
17:46:10 From Belinda : Using the site editor is quite slow when navigating between screens
17:46:35 From alex vasquez : Reacted to “Using the site edito…” with 👍
17:46:40 From Jessica Lyschik : But it‘s actually not 😅 Just by different names for the color palette
17:46:50 From Hans-Gerd Gerhards : Reacted to “Using the site edito…” with 👍
17:46:52 From Kathy : Reacted to “In the styles edit…” with 👍🏻
17:46:54 From Mike McAlister : Settling on some standard naming conventions for font sizes, spacing, etc. would really help the visual swap between themes.
17:47:01 From justintadlock : Replying to “What about styles.cs…”

For TT4, you can use the first method outlined there.
17:47:16 From Jessica Lyschik : Reacted to “Settling on some sta…” with 💯
17:47:17 From Anne Katzeff (she/her) : Replying to “What about styles.cs…”

Thank you Justin, what a relief to know!
17:47:24 From Belinda : Reacted to “But it‘s actually no…” with 💯
17:47:43 From Cullen @ Matchbox : Reacted to “But it‘s actually no…” with 💯
17:47:51 From Brian Coords : Reacted to “But it‘s actually no…” with 💯
17:48:01 From justintadlock : Reacted to “Thank you Justin, wh…” with 👍
17:48:10 From Anne Katzeff (she/her) : Reacted to “Settling on some sta…” with 👍
17:48:11 From Belinda : Reacted to “Settling on some sta…” with 👍
17:48:18 From Cullen @ Matchbox : Replying to “But it‘s actually no…”

We’ve been trying to identify naming conventions for this.
17:48:22 From Brian Coords : (Aurooba and I get deep into this whole “composability” issue without standardized tokens in our upcoming podcast about the Font Library 😂)
17:48:27 From Jeff Chandler : Ask Justin about standardizing things in WordPress https://wptavern.com/standardizing-theme-hook-names lol
17:48:39 From Mark Howells-Mead : Replying to “Settling on some sta…”

I agree with this; recommendations instead of constraints though. Even listing them as a suggestion in the docs would help.
17:48:39 From Fabian Todt : Reacted to “(Aurooba and I get d…” with 👍
17:48:40 From Sarah Norris : Reacted to “(Aurooba and I get d…” with 👀
17:48:47 From Jessica Lyschik : Replying to “But it‘s actually no…”
It has been a long discussion at TT4 development…
17:49:04 From justintadlock : Replying to “Ask Justin about sta…”

Not even touching standardizing names of things anymore. That ship has sailed.
17:49:16 From Jeff Chandler : Replying to “Ask Justin about sta…”

😅
17:50:26 From Cullen @ Matchbox : Replying to “But it‘s actually no…”

This may be a good GitHub discussion for us to start where we can share our naming conventions.
17:50:39 From Sarah Norris : Reacted to “This may be a good G…” with 👍
17:50:46 From Cullen @ Matchbox : Replying to “But it‘s actually no…”

I’ll try to start that later today.
17:50:46 From Mike McAlister : A not-so-great-but-maybe-temporary solution could be using patterns for the layout.
17:51:13 From Mike McAlister : Replying to “A not-so-great-but-m…”

Ultimately depends on how the end user is going to use them.
17:51:40 From Cullen @ Matchbox : Reacted to “Not even touching st…” with 😂
17:51:49 From Fabian Kägy : This here is the related issue on GitHub: https://github.com/WordPress/gutenberg/issues/58417
17:52:01 From alex vasquez : Reacted to “This here is the rel…” with 👍
17:52:12 From Jeff Chandler : Hi awesome Kathy!
17:52:17 From Mike McAlister : Ultimately these are the kinds of hiccups we really need to figure out if we want to keep driving adoption.
17:52:26 From Kristin Aus : Reacted to “(Aurooba and I get d…” with 👍
17:52:54 From justintadlock : Replying to “This here is the rel…”

Thanks, I was looking for that ticket.
17:52:57 From justintadlock : Reacted to “This here is the rel…” with 👍
17:53:19 From Fabian Todt : FYI I think this is how Woo does it, and yes’t is a lot of code 😅
https://github.com/woocommerce/woocommerce/blob/trunk/plugins/woocommerce/src/Blocks/BlockTemplatesController.php
17:53:34 From alex vasquez : Thank you for hosting this Justin and Birgit. I have have to jump out. I appreciate this type of meeting with this audience.
17:53:44 From justintadlock : Reacted to “Thank you for hostin…” with 👋
17:53:46 From Birgit Pauli-Haack : Reacted to “Thank you for hostin…” with 👋
17:54:29 From Anne Katzeff (she/her) : Reacted to “Thank you for hostin…” with 👋
17:56:39 From Hans-Gerd Gerhards : Thank you, it was very interesting. Unfortunately, I have to say goodbye
17:57:11 From Brian Coords : Cullen – is there a method where you could use a parent theme w/ version control and a child theme on the site with just local overrides to separate things out a bit?
17:58:08 From Wes Davis : Local (by Flywheel/WP Engine) does a great job of providing a UI that shows which files have changed between the local and live/production version of the site and letting you select which you want to push or pull when doing a sync.
17:58:25 From Mark Howells-Mead : Thanks all!
17:58:42 From Jennifer Kelly : thanks everybody!
17:58:43 From Brian Coords : Looking forward to these updates to Create Block Theme
17:58:48 From Kristin Aus : Thanks!
17:58:49 From Cullen @ Matchbox : Replying to “Cullen – is there a …”

This is a cool idea. I’d love to explore this more.
17:59:00 From Belinda : Reacted to “Looking forward to t…” with 💯
17:59:02 From Anne Katzeff (she/her) : Very insightful gathering. Thank you everyone!
17:59:05 From Fabian Todt : Reacted to “Looking forward to t…” with 💯
17:59:07 From Fabian Todt : Thanks for Hosting!
17:59:08 From Cullen @ Matchbox : Thank you everyone!
17:59:08 From Sarah Norris : Thanks all!!
17:59:14 From Nick Diego : 👋
17:59:19 From Tracy Rhodes : Great session, thanks to all!
17:59:32 From Cullen @ Matchbox : Replying to “Cullen – is there a …”

Are you doing this at all right now?
17:59:38 From Béryl : Thank you so much! ✨
17:59:39 From Brian Coords : Replying to “Cullen – is there a …”

Nope just thought of it
17:59:45 From Cullen @ Matchbox : Reacted to “Nope just thought of…” with 👍
17:59:46 From Belinda : Thank you 🙂