Podcasts about wp cli

Introducing Rob Ruiz Meet Rob Ruiz, a seasoned Senior Full Stack Developer with nearly two decades of expertise in WordPress innovation and open-source magic. As the Lead Maintainer of WP Rig since 2020, Rob has been the driving force behind this groundbreaking open-source framework that empowers developers to craft high-performance, accessible, and progressively enhanced WordPress themes with ease. WP Rig isn’t just a starter theme—it’s a turbocharged toolkit that bundles modern build processes, linting, optimization, and testing to deliver lightning-fast, standards-compliant sites that shine on any device. Show Notes For more on Rob and WP Rig, check out these links: LinkedIn Profile: https://www.linkedin.com/in/robcruiz WP Rig Official Site: https://wprig.io GitHub Repository: https://github.com/wprig/wprig Latest Releases: https://github.com/wprig/wprig/releases WP Rig 3.1 Announcement: https://wprig.io/wp-rig-3-1/ Transcript: Topher DeRosia: Hey everybody. Welcome to Hallway Chats. I’m your host Topher DeRosia, and with me today I have- Rob Ruiz: Rob Ruiz. Topher: Rob. You and I have talked a couple of times, once recently, and I learned about a project you’re working on, but not a whole lot about you. Where do you live? What do you do for a living? Rob: Yeah, for sure. Good question. Although I’m originally from Orlando, Florida, I’ve been living in Omaha, Nebraska for a couple of decades now. So I’m pretty much a native. I know a lot of people around here and I’ve been fairly involved in various local communities over the years. I’m a web developer. Started off as a graphic designer kind of out of college, and then got interested in web stuff. And so as a graphic designer turned future web developer, I guess, I was very interested in content management systems because it made the creating and managing of websites very, very easy. My first couple of sites were Flash websites, sites with macro media Flash. Then once I found content management systems, I was like, “Wow, this is way easier than coding the whole thing from scratch with Flash.” And then all the other obvious benefits that come from that. So I originally started with Joomla, interestingly enough, and used Joomla for about two or three years, then found WordPress and never looked back. And so I’ve been using WordPress ever since. As the years have gone on, WordPress has enabled me to slowly transition from a more kind of web designer, I guess, to a very full-blown web developer and software engineer, and even software architect to some degree. So here we are many years later. Topher: There’s a big step from designer to developer. How did that go for you? I’m assuming you went to PHP. Although if you were doing Flash sites, you probably learned ActionScript. Rob: Yeah. Yeah. That was very convenient when I started learning JavaScript. It made it very easy to learn JavaScript faster because I already had a familiarity with ActionScript. So there’s a lot of similarities there. But yeah. Even before I started doing PHP, I started learning more HTML and CSS. I did do a couple of static websites between there that were just like no content management system at all. So I was able to kind of sharpen my sword there with the CSS and HTML, which wasn’t particularly hard. But yeah, definitely, the PHP… that was a big step was PHP because it’s a proper logical programming language. There was a lot there I needed to unpack, and so it took me a while. I had to stick to it and really rinse and repeat before I finally got my feet under me. Topher: I can imagine. All right. So then you work for yourself or you freelance or do you have a real job, as it were? Rob: Currently, I do have a real job. Currently, I’m working at a company called Bold Orange out of Minneapolis. They’re a web agency. But I kind of bounce around from a lot of different jobs. And then, yes, I do freelance on the side, and I also develop my own products as well for myself and my company. Topher: Cool. Bold Orange sounds familiar. Who owns that? Rob: To be honest, I don’t know who the owners are. It’s just a pretty big web agency out of Minneapolis. They are a big company. You could just look them up at boldorange.com. They work for some pretty big companies. Topher: Cool. All right. You and I talked last about WP Rig. Give me a little background on where that came from and how you got it. Rob: Yeah, for sure. Well, there was a period of time where I was working at a company called Proxy Bid that is in the auction industry, and they had a product or a service — I don’t know how you want to look at that —called Auction Services. That product is basically just building WordPress sites for auction companies. They tasked us with a way to kind of standardize those websites essentially. And what we realized is that picking a different theme for every single site made things difficult to manage and increase tech debt by a lot. So what we were tasked with was, okay, if we’re going to build our own theme that we’re just going to make highly dynamic so we can make it look different from site to site. So we want to build it, but we want to build it smart and we want to make it reusable and maintainable. So let’s find a good framework to build this on so that we can maintain coding standards and end up with as little tech debt as possible, essentially. That’s when I first discovered WP Rig. In my research, I came across it and others. We came across Roots Sage and some of the other big names, I guess. It was actually a team exercise. We all went out and looked for different ones and studied different ones and mine that I found was WP Rig. And I was extremely interested in that one over the other ones. Interestingly enough- Topher: Can you tell me why over the other ones? Rob: That’s a great question. Yeah. I really liked the design patterns. I really liked the focus on WordPress coding standards. So having a system built in that checked all the code against WordPress coding standards was cool. I loved the compiling transpiling, whatever, for CSS and JavaScript kind of built in. That sounded really, really interesting. The fact that there was PHP unit testing built into it. So there’s like a starter testing framework built in that’s easy to extend so that you can add additional unit tests as your theme grows. We really wanted to make sure… because we were very into CICD pipelines. So we wanted to make sure that as developers were adding or contributing to any themes that we built with this, that we could have automated tests run and automated builds run, and just automate as much as possible. So WP rig just seemed like something that gave us those capabilities right out of the box. So that was a big thing. And I loved the way that they did it. Roots Sage does something similar, but they use their blade templating engine built in there. We really wanted to stick to something that was a bit more standard WordPress so that there wasn’t like a large knowledge overhead so that we didn’t have to say like, okay, if we’re bringing on other developers, like junior developers work on it, oh, it would be nice if you use Laravel too because we use this templating engine in all of our themes. We didn’t want to have to worry about that essentially. It was all object-oriented and all that stuff too. That’s what looked interesting to me. We ended up building a theme with WP Rig. I don’t know what they ended up doing with it after that, because I ended up getting let go shortly thereafter because the company had recently been acquired. Also, this was right after COVID too. So there was just a lot of moving parts and changing things at the time. So I ended up getting let go. But literally a week after I got let go, I came across a post on WP Tavern about how this framework was looking for new maintainers. Basically, this was a call put out by Morton, the original author of WP Rig. He reached out to WP Tavern and said, “Look, we’re not interested in maintaining this thing anymore, but it’s pretty cool. We like what we’ve built. And so we’re looking for other people to come in and adopt it essentially.” So I joined a Zoom meeting with a handful of other individuals that were also interested in this whole endeavor, and Morton reached out to me after the call and basically just said, “I looked you up. I liked some of the input that you had during the meeting. Let’s talk a little bit more.” And then that eventually led to conversations about me essentially taking the whole project over entirely. So, the branding, the hosting of the website, being lead maintainer on the project. Basically, gave me the keys to the kingdom in terms of GitHub and everything. So that’s how it ended up going in terms of the handoff between Morton and I. And I’m very grateful to him. They really created something super cool and I was honored to take it over and kind of, I don’t know, keep it going, I guess. Topher: I would be really curious. I don’t think either of us have the answer. I’d be curious to know how similar that path is to other project handoffs. It’s different from like an acquisition. You didn’t buy a plugin from somebody. It was kind of like vibes, I guess. Rob: It was like vibes. It was very vibey. I guess that’s probably the case in an open source situation. It’s very much an open source project. It’s a community-driven thing. It’s for everybody by everybody. I don’t know if all open source community projects roll like that, but that’s how this one worked out. There was some amount of ownership on Morton’s behalf. He did hire somebody to do the branding for WP Rig and the logo. And then obviously he was paying for stuff like the WPrig.io domain and the hosting through SiteGround and so on and so forth. So, we did have to transfer some of that and I’ve taken over those, I guess, financial burdens, if you want to think of it like that. But I’m totally okay with it. Topher: All right. You sort of mentioned some of the things Rig does, compiling and all that kind of stuff. Can you tell me… we didn’t discuss this before. I’m sitting at my desk and I think I want a website. How long does it take to go from that to looking at WordPress and logging into the admin with Rig? Rob: Okay. Rig is not an environment management system like local- Topher: I’m realizing my mistake. Somebody sends me a design in Figma. How long does it take me to go from that to, I’m not going to say complete because I mean, that’s CSS, but you know, how long does it take me to get to the point where I’m looking at a theme that is mine for the client that I’m going to start converting? Rob: Well, if you’re just looking for a starting point, if you’re just like, okay, how long does it take to get to like, okay, here’s my blank slate and I’m ready to start adopting all of these rules that are set up in Figma or whatever, I mean, you’re looking at maybe 5 minutes, 10 minutes, something like that. It’s pretty automated. You just need some simple knowledge of Git. And then there are some prerequisites to using WP Rig. You do have to have composer installed because we do leverage some Composer packages to some of it, although to be honest, you could probably get away with not using Composer. You just have to be okay with sacrificing some of the tools the WP Rig assumes you’re going to have. And then obviously Node. You have to have Node installed. A lot of our documentation assumes that you have NPM, that you’re using NPM for all your Nodes or your package management. But we did recently introduce support for Bun. And so you can use Bun instead of NPM, which is actually a lot faster and better in many ways. Topher: Okay. A lot of my audience are not developers, users, or light developers, like they’ll download a theme, hack a template, whatever. Is this for them? Am I boring those people right now? Rob: That’s a great question. I mean, and I think this is an interesting dichotomy and paradigm in the WordPress ecosystem, because you’ve got kind of this great divide. At least this is something I’ve noticed in my years in the WordPress community is you have many people that are not coders or developers that are very interested in expanding their knowledge of WordPress, but it’s strictly from a more of a marketing perspective where it’s like, I just want to know how to build websites with WordPress and how to use it to achieve my goals online from a marketing standpoint. You have that group of people, and then you have this other group of people that are very developer centric that want to know how to extend WordPress and how to empower those other people that we just discussed. Right? Topher: Right. Rob: So, yeah, that’s a very good question. I would say that WP Rig is very much designed for the developers, not for the marketers. The assumption there is that you’re going to be doing some amount of coding. Now, can you get away with doing a very light amount of coding? Yes. Yes, you can. I mean, if you compare what you’re going to get out of that assumed workflow to something that you would get off like Theme Forest or whatever, it’s going to be a night and day difference because those theme, Forest Themes, have hours, hundreds, sometimes hundreds of hours of development put into them. So, you’re not going to just out of the box immediately get something that is comparable to that. Topher: You need to put in those hundreds of hours of development to make a theme. Rob: As of today, yes. That may change soon though. Topher: Watch this space. Rob: That’s all I’ll say. Topher: Okay. So now we know who it’s for. I’m assuming there’s a website for it. What is it? Rob: Yeah. If you go to WPrig.io, we have a homepage that shows you all the features that are there in WP Rig. And then there’s a whole documentation area that helps people get up and running with WP Rig because there is a small learning curve there that’s pretty palatable for anybody who’s familiar with modern development workflows. So that is a thing. So the type of person that this is designed for anybody that wants to make a theme for anything. Let’s say you’re a big agency and you pull in a big client and that client wants something extremely custom and they come to you with Figma designs. Sure, you could go out there and find some premium theme and try to like child theme and overhaul that if you want. But in many situations, I would say in most situations, if you’re working from a Figma design that’s not based off of another theme already that’s just kind of somebody else’s brainchild, then you’re probably going to want to start from scratch. And so the idea here is that this is something to replace an approach, like underscores an approach. Actually, WP Pig was based off of underscores. The whole concept of it, as Morton explained it to me, was that he wanted to build an underscores that was more modern and full-featured from a development standpoint. Topher: Does it have any opinions about Gutenberg? Rob: It does now, but it did not when I took it over because Gutenberg did not exist yet when I took over WP Rig. Topher: Okay. What are its opinions? Rob: Yeah, sure. The opinion right out of the gate is that you can use Gutenberg as an editor and it has support like CSS rules in it for the standard blocks. So you should be able to use regular Gutenberg blocks in your theme and they should look just fine. There’s no resets in there. It doesn’t start from scratch. There’s not a bunch of styling you have to do for the blocks necessarily. Now, if you go to the full site editing or block-based mentality here, there are some things you need to do in WP Rig to convert the out-of-the-box WP Rig into another paradigm essentially. Right when you pull WP Rig, the assumption is you’re building what most people would refer to as a hybrid theme. The theme supports API or whatever, and the assumption is that you’re not going to be using the site editor. You’re just going to kind of do traditional WordPress, but you might be using Gutenberg for your content. So you’re just using Gutenberg kind of to author your pages and your posts and stuff like that, but not necessarily the whole site. WP Rig has the ability to kind of transform itself into other paradigms. So the first paradigm we built out was the universal theme approach. And the idea there is that you get a combination of the full site editing capabilities. But then you also have the traditional menu manager and the settings customizer framework or whatever is still there, right? These are things that don’t exist in a standard block-based theme. So I guess an easy example would be like the 2025 WordPress theme that comes right out of the box. It comes installed in WordPress. That is a true block-based theme, not a universal theme. So it doesn’t have those features because the assumption there is that it doesn’t need those features. You can kind of transform WP Rig into a universal theme that’s kind of a hybrid between a block-based and a classic theme. And then it can also transform into a strictly block-based theme as well. So following the same architecture as like the WordPress 2025 theme or Ollie or something like that is also a true block-based theme as well. So you can easily convert or transform the starting point of WP Rig into either of those paradigms if that’s the type of theme you’re setting out to build. Topher: Okay. That sounds super flexible. How much work is it to do that? Rob: It’s like one command line. Previously we had some tutorials on the website that showed you step-by-step, like what you needed to change about the theme to do that. You would have to add some files, delete some files, edit some code, add some theme supports into the base support class and some other stuff. I have recently, as of like a year and a half ago or a year ago, created a command line or a command that you can type into the command line that basically does that entire conversion process for you in like the blink of an eye. It takes probably a second to a second and a half to perform those changes to the code and then you’re good to go. It is best to do that conversion before you start building out your whole theme. It’s not impossible to do it after. But you’re more likely to run into problems or conflicts if you’ve already set out building your whole theme under one paradigm, and then you decide how the project you want to switch over to block-based or whatever. You’re likely to run into the need to refactor a bunch of stuff in that situation. So it is ideal to make that choice extremely early on in the process of developing your theme. But either way it’ll still work. That’s just one of the many tools that exist in WP Rig to transform it or convert it in several ways. That’s just one example. There are other examples of ways that Rig kind of converts itself to other paradigms as well. Topher: Yeah. All right. In my development life, I’ve had two parts to it. And one is the weekend hobbyist, or I download cadence and I whip something up in 20 minutes because I just want to experiment and the other is agency life where everything’s in Git, things are compiled, there are versions, blah, blah, blah. This sounds very friendly to that more professional pathway. Rob: Absolutely. Yes. Or, I mean, there’s another situation here too. If you’re a company who develops themes and publishes them to a platform like ThemeForest or any other platform, perhaps you’re selling themes on your own website, whatever, if you’re making things for sale, there’s no reason you couldn’t use WP Rig to build your themes. We have a bundle process that bundles your theme for publication or publishing. Whether you’re an agency or whether you’re putting your theme out for sale, it doesn’t matter, during that bundle process, it does actually white label the entire code base to where there’s no mention of WP Rig in the code whatsoever. Let’s say you were to build a theme that you wanted to put up for sale because you have some cool ideas. Say, page transitions now are completely supported in all modern or in most modern browsers. And when I say print page transitions, for those that are in the know, I am talking about not single page app page transitions, but through website page transitions. You can now do that. Let’s say you were like, “Hey, I’m feeling ambitious and I want to put out some new theme that comes with these page transitions built in,” and that’s going to be fancy on ThemeForest when people look at my demo, people might want to buy that. You could totally use WP Rig to build that out into a theme and the bundle process will white label all of the code. And then when people buy your theme and download that code, if they’re starting to go through and look through your code, they’re not going to have any way of knowing that it was built with WP Rig unless they’re familiar with the base WP Rig architecture, like how it does its object-oriented programming. It might be familiar with the patterns that it’s using and be able to kind of discern like, okay, well, this is the same pattern WP Rig uses, so high likelihood it was built with WP Rig. But they’re not going to be able to know by reading through the code. It’s not going to say WP Rig everywhere. It’s going to have the theme all over the place in the code. Topher: Okay. So then is that still WP Rig code? It just changed its labels? Rob: Yeah. Topher: So, it’s not like you’re exporting HTML, CSS and JavaScript? The underlying Rig framework is still there. Rob: Yeah. During the bundle process, it is bundling CSS and HTML. Well, HTML in the case of a block-based theme. But, yeah, it is bundling your PHP, your CSS, your JavaScript into the theme that you’re going to let people download when they buy it, or that you’re going to ship to your whatever client’s website. But all that code is going to be transpiled. In the case of CSS and JavaScript, there’s only going to be minified versions of that code in that theme. The source code is not actually going to be in there. Topher: This sounds pretty cool. You mentioned some stuff might be coming. You don’t have to tell me what it is, but do you have a timeline? When should we be watching for the next cool thing from Rig? Rob: Okay, cool. Well, I’m going to keep iterating on Rig forever. Regardless of any future products that might be built on WP Rig, WP Rig will always and forever remain an open source product for anybody to use for free and we, I, and possibly others in the future will continue to update it and support it over time. We just recently put out 3.1. You could expect the 3.2 anytime in the next six months to a year, probably closer to six months. One feature I’m looking at particularly closely right now is the new stuff coming out in version 6.9 of WordPress around the various APIs that are there. I think one of them is called the form… There’s a field API and a form API or view API or something like that. So WP Rig comes with a React-based settings framework in it. So if you want your theme to have a bunch of settings in it to make it flexible for whoever buys your theme, you can use this settings framework to easily create a bunch of fields, and then that framework will automatically manage all your fields and store all the data from those fields and make it easy to retrieve the values of the input on those fields, without knowing any React at all. Now, if you know React, you can go in there and, you know, embellish what’s already there, but it takes a JSON approach. So if you just understand JSON, you can go in and change the JSON for the framework, and that will automatically add fields into the settings framework. So you don’t even have to know React to extend the settings page if you want. That will likely get an overhaul using these new APIs being introduced into Rig. Topher: All right. How often have you run into something where, “Oh, look, WordPress has a new feature, I need to rebuild my system”? Rob: Over the last four or five years, it’s happened a lot because, yeah, I mean, like I said, when I first took this thing over, Gutenberg had not even been introduced yet. So, you had the introduction of Gutenberg and blocks. That was one thing. Then this whole full site editing became a thing, which later became the site editor. So that became a whole thing. Then all these various APIs. I mean, it happens quite frequently. So I’ve been working to keep it modern and up to date over the past four years and it’s been an incredible learning experience. It not only keeps my WordPress knowledge extremely sharp, but I’ve also learned how various other toolkits are built. That’s been the interesting thing. From a development standpoint, there’s two challenges here. One of the challenges is staying modern on the WordPress side of things. For instance, WordPress coding standards came out with a version 3 and then a version 3.1 about two years ago. I had to update WP Rig to leverage those modern coding standards. So that’s one example is as WordPress changes, the code in WP Rig also needs to change. Or for instance, if new CSS standards change, right, new CSS properties come out, it is ideal for the base CSS in WP Rig, meaning the CSS that you get right out of the box with it, comes with some of these, for instance, CSS grid, Flexbox, stuff like that. If I was adopting a theme framework to build a theme on, I would expect some of that stuff to be in there. And those things were extremely new when I first took over WP Rig and were not all baked in there essentially. So I’ve had to add a lot of that over time. Now there’s another side to this, which is not just keeping up with WordPress and CSS and PHP, 8. whatever, yada yada yada. You’ve also got the toolkit. There are various node packages and composer packages of power WP Rig and the process in which it does the transpiling, the bundling, the automated manipulation of your code during various aspects of the usage of WP Rig is a whole nother set of challenges because now you have to learn concepts like, well, how do I write custom node scripts? Right? Like there were no WP CLI commands built into WP Rig when I first took it over. Now there’s a whole list. There’s a whole library of WP CLI commands that come in Rig right out of the gate. And so I’ve had to learn about that. So just various things that come with knowing how do you automate the process of converting code, that’s something that was completely foreign to me when I first took over WP Rig. That’s been another incredible learning experience is understanding like what’s the difference between Webpack and Gulp. I didn’t know, right? I would tell people I’m using Gulp and WP Rig and they would be like, “Well, why don’t you just use Webpack?” and I would say, “I don’t know. I don’t know what the difference is.” So over time I could figure out what are the differences? Why aren’t we using Webpack? And I’m glad I spent some time on that because it turns out Webpack is not the hottest thing anymore, so I just skipped right over all that. When I overhauled for version 3, we’re now not using Gulp anymore as of 3.1. We’re now using more of a Vite-like process, far more modern than Webpack and far better and faster and sleeker and lighter. I had to learn a bunch about what powers Vite. What is Vite doing under the hood that we might be able to also do in WP Rig, but do it in a WordPress way. Because Vite is a SaaS tool. If you’re building a SaaS, like React with a… we’re not a SaaS. I guess a spa is a better term to use here. If you’re building a single page application with React or view or belt or whatever, right, then knowing what Vite is and just using Vite right out of the box is perfect. But it doesn’t translate perfectly to WordPress land because WordPress has its own opinions. And so I did have to do some dissecting there and figure out what to keep and what to not keep to what to kind of set aside so that WordPress can keep doing what WordPress does the way WordPress likes to do it, but also improve on how we’re doing some of the compiling and transpiling and the manipulation of the code during these various. Topher: All right. I want to pivot a little bit to some personal-ish questions. Rob: Okay. Topher: This is a big project. I’m sure it takes up plenty of your time. How scalable is that in your life? Do you want to do this for the rest of your life? Rob: That’s a fantastic question. I don’t know about the rest of my life. I mean, I definitely want to do web development for the rest of my life because the web has, let’s be honest, it’s transformed everyone’s way of life, whether you’re a web developer or not. You know, the fact that we have the internet in our pocket now, you know, it has changed everything. Apps, everything. It’s all built on the web. So I certainly want to be involved in the web the rest of my life. Do I want to keep doing WordPress the rest of my life? I don’t know. Do I want to keep doing WP Rig the rest of my life? I don’t know. But I will say that you bring up a very interesting point, which is it does take up a lot of time and also trust in open source over the past four or five years I would argue has diminished a little bit as a result of various events that have occurred over the past two or three years. I mean, we could cite the whole WP Engine Matt Mullerwig thing. We can also cite what’s going on with Oracle and JavaScript. Well, I mean, there’s many examples of this. I mean, we can cite the whole thing that happened… I mean, there’s various packages out there that are used and developed and open source to anybody, and some of them are going on maintained and it’s causing security vulnerabilities and degradation and all this stuff. So it’s a very important point. One thing I started thinking about after considering that in relation to WP Rig was I noticed that there’s usually a for-profit arm of any of these frameworks that seems to extend the lifespan of it. Let’s just talk about React, for example, React is an open source JavaScript framework, but it’s used by Facebook and Facebook is extremely for-profit. So companies that are making infrastructural or architectural decisions, they will base their choice on whether or not to use a framework largely on how long they think this framework is going to remain relevant or valid or maintained, right? A large part of that is, well, is there a company making money off of this thing? Because if there is, the chances- Topher: They’re going to keep doing that. Rob: They’re going to keep doing it. It’s going to stay around. That’s good. I think that’s healthy. A lot of people that like open source and want everything to be free, they might look at something like that and say like, well, I don’t want you to make a paid version of it or there shouldn’t be a pro version. I think that’s a very short-sighted way of looking at that software and these innovations. I think a more experienced way of looking at it is if you want something to remain relevant and maintained for a long period of time, having a for-profit way in which it’s leveraged is a very good thing. I mean, let’s be real. Would WordPress still be what it is today if there wasn’t a wordpress.com or if WooCommerce wasn’t owned by Automattic or whatever, right? They’ll be on top. I mean, it’s obviously impossible to say, but my argument would be, probably not. I mean, look at what’s happened to the other content management systems out there. You know, Joomla Drupal. They don’t really have a flourishing, you know, paid pro service that goes with their thing that’s very popular, at least definitely not as popular as WordPress.com or WordPress VIP or some of these other things that exist out there. And so having something that’s making and generating money that can then contribute back into it the way Automattic has been doing with WordPress over these years has, in my opinion, been instrumental. I mean, people can talk smack about Gutenberg all they want, but let’s be real, it’s 2025, would you still feel that WordPress is an elegant solution if we were still working from the WYSIWYG and using the classic editor? And I know a lot of people are still using the classic editor and there’s classic for us, the fork and all that stuff. But I mean, that only makes sense in a very specific implementation of WordPress, a very specific paradigm. If you want to explore any of these other paradigms out there, that way of thinking about WordPress kind of falls apart pretty quickly. I, for one, am happy that Gutenberg exists. I’m very happy that Automattic continues. And I’m grateful, actually, that Automattic continues to contribute back into WordPress. And not just them, obviously there’s other companies, XWP, 10Up, all these other companies are also contributing as well. But I’m very grateful that this ecosystem exists and that there’s contribution going back in and it’s happening from companies that are making money with this. And I think that’s vital. All that to say that WP Rig may and likely will have paid products in the future that leverage WP Rig. So that’s not to say that WP Rig will eventually cost money. That’s just to say that eventually people can expect other products to come out in the future that will be built on WP Rig and incentivize the continued contributions back into WP Rig. The open source version of WP Rig. Topher: That’s cool. I think that’s wise. If you want anything to stay alive, you have to feed it. Rob: That’s right. Topher: I had some more questions but I had forgotten them because I got caught up in your answer. Rob: Oh, thank you. I’ll take that as a compliment. I mean, my answer was eloquent. But I’m happy to expand on anything, know you, WordPress related, me related, you know, whether it comes to the ecosystem in WordPress, the whole WordCamp meetup thing is very interesting. I led the WP Omaha meetup for many years here in Omaha, Nebraska and I also led the WordCamp, the organizing of WordCamp here in Omaha for several years as well. That whole community, the whole ecosystem, at least in America seems to have largely fallen apart. I don’t know if you want to talk about that at all. But yeah, I’m ready to dive into any topics. Topher: I’m going to have one more question and then we’re going to wrap up. And it was that you were talking about all the things you had to learn. I’m sure there were nights where you were looking at your computer thinking, “Oh man, I had it working, now I gotta go learn a new thing.” I would love for you to go back in time and blog all of that if you would. But given that you can’t, I would be interested in a blog moving forward, documenting what you’re learning, how you’re learning it and starting maybe with a post that’s summarizes all of that. Obviously, that’s up to you and how you want to spend your time, but I think it’d be really valuable to other people starting a project, picking up somebody else’s project to see what the roadmap might look like. You know what I mean? Rob: For sure. Well, I can briefly summarize what I’ve learned over the years and where I’m at today with how I do this kind of stuff. I will say that a lot of the improvements to WP Rig that have happened over the last year or two would not be possible without the advent of AI. Topher: Interesting. Rob: That’s a fancy way of saying that I have been by coding a lot of WP Rig lately. If you know how to use AI, it is extremely powerful and it can help you do many things very quickly that previously would have taken much longer or more manpower. So, yeah, perhaps if there was like five, six, seven people actively, excuse me, actively contributing to WP Rig, then this type of stuff would have been possible previously, but that’s not the case. There is one person, well, one main contributor to WP Rig today and you’re talking to them. There are a handful of other people that have been likely contributing to WP Rig over the versions and you can find their contributions in the change log file in WP Rig. But those contributions have been extremely light compared to what I’ve been doing. I wouldn’t be able to do any of it without AI. I have learned my ability to learn things extremely rapidly has ramped up tenfold since I started learning how to properly leverage LLMs and AI. So that’s not to say that like, you know, WP Rig, all the code is just being completely written by AI and I’m just like. make it better, enter, and then like WP Rig is better. I wish it was that easy. It’s certainly not that. But when I needed to start asking some of these vital questions that I really didn’t have anyone to turn to to help answer them, I was able to turn to AI. For instance, let’s go back to the Webpack versus Gulp situation. Although Gulp is no longer used in WP Rig, you know, it was used in WP Rig until very recently. So I had to understand like, what is this system, how does it work, how do I extend it and how do I update it and all these things, right? And why aren’t we using WebPack and you know, is there validity to this criticism behind you should use webpack instead of Gulp or whatever, right? I was able to use AI to ask these questions and be able to get extremely good answers out of it and give me the direction I needed to make some of these kind of higher level decisions on like architecturally where should WP Rig go? It was through these virtual conversations with LLMs that I was able to refine the direction of WP Rig in a direction that is both modern and forward-thinking and architecturally sound. I learned a tremendous amount from AI about the architecture, about the code, about all of it. My advice to anybody that wants to extend their skill set a little bit in the development side of things is to leverage this new thing that we have in a way that is as productive as possible for you. So that’s going to vary from person to person. But for me, if I’m on a flight or if I’m stuck somewhere for a while, like, let’s say I got to take my kid to practice or something and I’m stuck there for an hour and I got to find some way to kill my time 9 times out of 10, I’m on my laptop or on my phone having conversations with Grok or ChatGPT or Gemini or whatever. I am literally refining… I’m just sitting there asking it questions that are on my mind that I wish I could ask somebody who’s like 10 times more capable than me. It has been instrumental. WP Rig wouldn’t be where it is today if it wasn’t for that. I would just say to anybody, especially now that it’s all on apps and you don’t have to be on a browser anymore, adopt that way of thinking. You know, if you’re on your lunch break or whatever and you have an hour lunch break and you only take 15 minutes to eat, what could you be doing with those other 45 minutes? You could just jump on this magical thing that we have now and start probing it for questions. Like, Hey, here’s what I know. Here’s what I don’t know. Fill these knowledge gaps for me.” And it is extremely good at doing that. Topher: So my question was, can you blog this and your answer told me that there’s more there that I want to hear. That’s the stuff that should be in your book when you write your book. Rob: I’m flattered that you would be interested in reading anything that I write. So thank you. I’ve written stuff in the past and it hasn’t gotten a lot of attention. But I also don’t have any platforms to market it either. But yeah, no, I made some… I’m sorry. Topher: I think your experience is valuable far beyond Rig or WordPress. If you abstract it out of a particular project to say, you know, I did this with a project, I learned this this way, I think that would be super valuable. Rob: Well, I will say that recently at my current job, I was challenged to create an end to end testing framework with Playwright that would speed up how long it takes to test things and also prevent, you know, to make things fail earlier, essentially, to prevent broken things from ending up in the wild, right, and having to catch them the hard way. I didn’t know a lot about Playwright, but I do know how toolkits work now because of WP Rig. And I was able to successfully in a matter of, I don’t know, three days, put together a starter kit for a test framework that we’re already using at work to test any website that we create for any client. It can be extended and it can be hooked into any CI CD pipeline and it generates reports for you and it does a whole bunch of stuff. I was able to do this relatively quickly. This knowledge, yes, does come in handy in other situations. Will I end up developing other toolkits like WP Rig in the future for other things? I guess if I can give any advice to anybody listening out there, another piece of advice I would give people is, you know, especially if you’re a junior developer and you’re still learning or whatever, or you’re just a marketing person and just want to have more control over the functionality side of what you’re creating or more insight into that so you could better, you know, manage projects or whatever. My advice would be to take on a small little project that is scoped relatively small that’s not too much for you to chew and go build something and do it with… Just doing that will be good. But if you can do it with the intent to then present it in some fashion, whether it be a blog article or creating a YouTube video or going to a meetup and giving a talk on it or even a lunch and learn at work or whatever, right, that will, in my experience, it will dramatically amplify how much you learn from that little pet project that’s kind of like a mini learning experience. And I highly encourage anybody out there to do that on the regular. Actually, no matter what your experience level is in development, I think you should do these things on a regular basis. Topher: All right. I’m going to wrap this up. I got to get back to work. You probably have to get back to work. Rob: Yeah. Topher: Thanks for talking. Rob: Thanks for having me, Topher. Really appreciate it. Topher: Where could people find you? WPrig.io?  Rob: Yeah, WPrig.io. WP rig has accounts on all of the major platforms and, even on Bluesky and Mastodon. You can look me up, Rob Ruiz. You can find me on LinkedIn. You can find me on all of those same platforms as well. You can add me on Facebook if you want, whatever. And I’m also in the WordPress Slack as well as Rob Ruiz. You can find me in the WordPress Slack. And then I’m on the WordPress Reddit and all that stuff. So yeah, reach out. If anybody wants to have any questions about Rig or anything else, I’m happy to engage.  Topher: Sounds good. All right, I’ll see you. Rob: All right, thanks, Topher. Have a good day. Topher: This has been an episode of the Hallway Chats podcast. I’m your host Topher DeRosia. Many thanks to our sponsor Nexcess. If you’d like to hear more Hallway Chats, please let us know on hallwaychats.com.

W tym odcinku omawiam trzy przydatne komendy WP-CLI: eval, eval-file oraz shell. Te komendy pozwalają na uruchamianie kodu PHP bezpośrednio w kontekście WordPressa. To idealne rozwiązanie do szybkiego wykonywania jednorazowych operacji, migracji danych czy testów bez konieczności modyfikowania plików. W odcinku dzielę się praktycznymi przykładami zastosowania tych narzędzi, które pomagają lepiej zrozumieć ich potencjał i zastosowanie w codziennej pracy.

Síguenos en: Después de unas merecidas y disfrutadas vacaciones, volvemos a nuestros episodios semanales de Freelandev con nuestro día a día en el mundo WordPress y en OsomPress ¿Qué tal la semana? Semana esther Agosto tranquilo con mantenimientos habituales Siguiendo con la revisión de sitios con PHP 7.4 Avanzando con Dakota Next Semana Nahuai Follow-up, la opción de ver el calendario de fechas al programar un post está de vuelta en la 6.6.1 (o no la encontré en la 6.6). Cerramos una nueva colaboración en OsomPress. También vendrá a comentarlo cuando sea el momento. Flipando con la maquetación del menú responsive en un tema de bloques. Novedades sobre el proceso de review de WordPress.com Interesante reflexión que me trasladó Elías sobre para quien es el editor del sitio. Investigando las diferencias entre Transients API y las funciones wp_cache_*. Trasteando con WP-CLI. Echando un ojo al curso intermedio de desarrollo de temas de Learn WordPress. Investigando la opción de usar marcado de sintaxis solo con CSS. Necesitas una fuente que soporte “Color layers” (COLRv0 y COLRv1) y jugar con “@font-palette-values” y “font-pallete”. Meetup de Terrassa el 10 de septiembre. Contenido Nahuai Novedades https://wordpress.com/blog/2024/07/30/perplexity-partnership/ https://make.wordpress.org/core/2024/07/29/wordpress-6-6-performance-improvements/ https://make.wordpress.org/core/2024/08/15/introducing-twenty-twenty-five/ https://wptavern.com/jamie-marsland-joins-automattic-as-head-of-wordpress-youtube Menciones Enoch nos propone usar filtros anti-pop y mejorar el nivelado de audios. Bohdan nos propone usar un único fichero SVG y llamar a SVGs individuales usando ids.

Aurooba and Brian dig into the Font Library - a flagship feature launching in WordPress 6.5. Along the way they discuss the long road getting it into core, some user interface issues, and the future of "composability" in WordPress.A full transcript of the episode is available on the website. Watch the video podcast on YouTube and subscribe to our channel and newsletter to hear about episodes (and more) first!Fonts in WP Tavern - https://wptavern.com/a-pared-back-web-fonts-api-may-land-in-wordpress-6-0-or-not-at-allRich Tabor - Composability - https://rich.blog/theme-composition/WordPress 6.5 - https://make.wordpress.org/core/6.5Brian's Tavern Article - https://wptavern.com/synced-pattern-overrides-punted-font-library-approved-as-wordpress-6-5-nears-releaseBrian's website – https://www.briancoords.comAurooba's website – https://aurooba.com (00:00) - S02E12 - Font Library (00:09) - Intro and WordPress 6.5 (03:08) - Font Library and Developers Naming Things (05:05) - Release Landing Page, Playground, and WP CLI (09:49) - Styles Panel in the Site Editor (13:23) - Typography Panel and Tech issues (18:05) - Variants and Variable Fonts (19:52) - Google Fonts and GDPR (21:43) - Saving changes in the site editor (24:58) - Font Library's Journey to Core (28:01) - Ongoing Discussion for the Font Library (32:25) - The Hosting Companies Responsibility (35:47) - Composability

Hola y bienvenido a WP A DAY, tu fuente generada algorítmicamente para conocer las últimas noticias y actualizaciones en el ámbito de WordPress. Hoy es 29 de octubre de 2023. En las noticias de hoy, tenemos un puñado de noticias interesantes. Para abrir boca, la versión 16.9 de Gutenberg ha sido lanzada e incluye varias mejoras, correcciones de errores y avances en características de la Fase 3. Algunos aspectos destacados incluyen la posibilidad de renombrar la mayoría de los bloques, duplicar y renombrar patrones, y la adición de nuevas categorías de medios como audio y video. También se han realizado mejoras en el control de diseño Dimensions, se han agregado unidades de tamaño CSS Level 4, y ahora se muestra la paginación en las llamadas getEntityRecords(). Se han solucionado numerosos errores y se han realizado otras mejoras. Amplía tus conocimientos en make.wordpress.org. Y siguiendo con la actualidad, la segunda versión de prueba (RC2) para WordPress 6.4 ya está disponible. Recuerda no instalar ni probar esta versión en sitios web de producción o misiones críticas. Se recomienda evaluar RC2 en un servidor de prueba y sitio. Puedes probar WordPress 6.4 RC2 de tres maneras: instalando y activando el plugin WordPress Beta Tester, descargando la versión RC2 e instalándola en un sitio de WordPress, o usando el comando WP-CLI "wp core update --version=6.4-RC2". Se han resuelto más de 25 problemas desde RC1. Si eres desarrollador, se agradece tu contribución en pruebas, detección de vulnerabilidades, actualización de temas y plugins, y traducción de WordPress a otros idiomas. La versión final de WordPress 6.4 será lanzada el 7 de noviembre de 2023. Accede a toda la info en wordpress.org. Y para finalizar, texts.com es una aplicación que reúne todos tus chats de diferentes plataformas como iMessage, WhatsApp, Instagram, Signal, Discord, entre otros, en un solo lugar. Además de ofrecer una gran comodidad, la aplicación también cuenta con cifrado de extremo a extremo y funciones adicionales como programar mensajes para enviar cuando el destinatario esté despierto. Automattic adquiere Texts.com y su fundador se une al equipo. Un paso más hacia el futuro de la mensajería. Puedes unirte a la lista de espera para probar la aplicación. Tienes toda la información en wordpress.com. Esto resume las noticias de hoy sobre las actualizaciones de WordPress. Asegúrate de consultar nuestra sección de enlaces relacionados para obtener más información sobre estas historias. Si disfrutaste este episodio, díselo a tus amigos. Para obtener la transcripción y los enlaces a las publicaciones mencionadas en este programa, visita Blogpocket.com. Gracias por escucharnos y nos vemos en el próximo episodio. ¡Te deseo una maravillosa semana!.

Hola y bienvenido a WP A DAY, tu fuente para obtener las últimas noticias y actualizaciones en el mundo de WordPress. Hoy es domingo 15 de octubre de 2023. En un reciente artículo leído en WordPress, se anuncia la disponibilidad de la versión 6.4 Beta 4 para su descarga y pruebas. Se advierte que esta versión está en desarrollo, por lo que no se recomienda instalarla en sitios web productivos. Se sugiere probarla en un servidor y sitio de pruebas. Se ofrecen tres formas de probarla: instalar el plugin WordPress Beta Tester, descargar la versión Beta 4 directamente o utilizar el comando WP-CLI. La fecha estimada para el lanzamiento final es el 7 de noviembre de 2023. Se insta a la comunidad a continuar probando para garantizar la calidad del lanzamiento. Se proporciona una guía detallada para quienes deseen contribuir como probadores. Esta versión Beta se lanzó en respuesta a la actualización de mantenimiento y seguridad de WordPress 6.3.2. El lanzamiento de la versión Release Candidate 6.4 está programado para el 17 de octubre y dependerá de la retroalimentación de los probadores. Agradecimientos a los contribuyentes en este lanzamiento. Sumérgete en la información completa en Make WordPress Core. En otro orden de cosas, en un informe exclusivo de The WordPress Photo Directory, se anunció que se ha superado oficialmente la marca de las 10.000 fotos. El propósito de este directorio es proporcionar fotografías gratuitas y de alta calidad, con licencia Creative Commons, enviadas por la comunidad y adecuadas para su uso en sitios de WordPress y otros lugares. El directorio fue propuesto por Matt Mullenweg en el State of the Word 2021 y ahora todas las imágenes se pueden ver en Openverse, un buscador de medios de código abierto. Las principales categorías de fotos en el directorio son naturaleza, arquitectura, objetos y animales. Por fin, el directorio de fotos se ha convertido en lo que Justin Tadlock imaginó en 2021: "un proyecto donde cualquier persona pueda subir una bonita foto de la naturaleza que haya tomado durante el fin de semana". Sumérgete en la información completa en wp-content.co. Y no puedes irte sin escuchar la noticia más sorprendente de hoy. ¡WordPress.com se conecta al fediverso! ActivityPub es la tecnología que permite a los usuarios de WordPress.com interactuar con una audiencia más amplia a través del fediverso. Con esta integración, los usuarios ahora pueden seguir blogs de varias plataformas directamente desde su cuenta de WordPress.com.  Lee esta gran noticia en el blog de WordPress.com. Gracias por acompañarnos en este episodio del podcast WP A DAY. Si quieres seguir aprendiendo sobre WordPress y estar al tanto de todas nuestras novedades, no olvides suscribirte a nuestro podcast. Además, recuerda que las transcripciones y los enlaces citados los puedes encontrar en Blogpocket.com. ¡Hasta la próxima!

Apple Journals & Day One | Matt MullenwegImportant Takeaways:Apple announced its own Journal app at WWDC, which competes with Automattic's product, Day One.Day One has a few advantages over Apple's Journal app. One of them is the upcoming feature of Shared Journals, which allows fully end-to-end encrypted shared private journals with friends and family.Another advantage of Day One is its cross-platform availability. Unlike Apple's Journal app, which is limited to Apple devices, Day One works on all Apple devices, Android devices, and the web.Link: Original ArticleA Place of One's Own, in Noho – Automattic DesignImportant Takeaways:Automattic has a unique office space in Noho, New York, which is described as a “magic space” with unobstructed views of lower Manhattan.The office design is inspired by the aesthetics of jazz clubs and features collections of mid-century vintage furniture, art and design books, and original art pieces.The office is designed to be a practical and elastic canvas for diverse uses, and it reflects the rich aesthetics of Automattic's multiple creative tools.The office space is not just for work; it also serves as a socializing and connecting space for Automattic employees.Link: Original ArticleLinking to Supporting Orgs – Make WordPress.orgImportant Takeaways:The post discusses the need for a dedicated page on WordPress.org to link to independent organizations that support WordPress's mission of democratizing publishing.These organizations are not officially part of WordPress but offer valuable resources and opportunities to get involved.The proposed structure for such a page includes an introduction, organization categories, organization listings, updates and announcements, and contact information.The organizations should align with the mission of WordPress, adhere to a code of conduct, and actively contribute to the WordPress community or the broader mission of democratizing publishing.A vetting process is suggested for adding organizations to this page, including initial screening, detailed review, contacting the organization, decision to list, and periodic review.Link: Original ArticleWordPress Accessibility Day Gains Nonprofit Status Through Partnership with Knowbility – WordPress Accessibility DayImportant Takeaways:WordPress Accessibility Day, a virtual 24-hour conference focused on accessibility best practices for WordPress websites, has gained 501(c)(3) nonprofit status through a partnership with Knowbility.The event was initially started in 2020 by the WordPress core Accessibility Team and was revived in 2022 by Amber Hinds and Joe Dolson as an independent event.The 2022 event was a success, with 11 organizers, 1604 attendees, and 20 volunteers from 52 countries. After all event expenses were paid, WordPress Accessibility Day donated $2,000 to Knowbility.The partnership with Knowbility allows WordPress Accessibility Day to gain nonprofit status, making donations tax-deductible in the United States. It also provides access to Knowbility's accessible online event planning resources.The 2023 event will be held from 10:00 AM CDT (3:00 PM UTC) on Wednesday, September 27th, until 10:00 AM CDT (3:00 PM UTC) on Thursday, September 28th. The event will be live captioned and have sign language interpreters.Link: Original ArticleOne Equity Partners acquires cloud services provider Liquid Web and forms new holding company, CloudOne DigitalImportant Takeaways:One Equity Partners (OEP) has completed the acquisition of Liquid Web, a provider of managed cloud services, forming a new platform known as CloudOne Digital.The senior leadership team of Liquid Web will transition to expanded roles in the new, larger CloudOne platform with Jim Geiger as CEO, Carrie Wheeler as COO, and Joe Oesterling as CTO.Liquid Web, founded in 1997, operates 10 global data centers with more than 500,000 sites under management. With its brand acquisitions, CloudOne Digital will serve over 187,000 clients worldwide.CloudOne Digital will offer a broad portfolio of cloud products that meet the needs of web-dependent small and mid-sized businesses, cloud servers for developers and businesses with highly persistent, compute-intensive workloads, and managed private cloud for mid-market businesses that require enterprise-grade infrastructure and solutions.OEP plans an aggressive expansion strategy for CloudOne Digital, aiming to combine and integrate complementary businesses in the multi-cloud infrastructure segment.Link: Original ArticleWordCampers Demand Changes to Q&A Format – WP TavernImportant Takeaways:WordCamp attendees are calling for changes to the Q&A format at live events, citing issues with attendees abusing the format for self-promotion or not asking relevant questions.WordPress Core Committer Felix Arntz suggested that questions taking longer than a minute should be asked informally at a later opportunity.Arntz proposed several ideas to improve the Q&A format, including submitting questions to a central platform for upvoting, discarding lengthy questions, and providing mandatory training for emcees on handling problematic Q&A situations.He also suggested making Q&A optional, depending on the speaker's preference, to create a more inclusive environment for speakers.The feedback received on Arntz's Twitter thread was largely positive, with other attendees offering their own suggestions for improving the Q&A format.Link: Original ArticleNew Filter Controls: Discover “Commercial” and “Community” in the Theme and Plugin Directory – Make WordPress.orgImportant Takeaways:New categorizations were introduced in the Theme and Plugin Directory in late 2022 to enhance the browsing experience. These filters categorize plugins/themes as “Commercial” and “Community.”The “Commercial” filter allows users to discover themes and plugins developed by professional companies and individuals who offer their products for a fee. These premium options often come with dedicated support, advanced features, and customization options.The “Community” filter showcases themes and plugins created by the WordPress community. These products are often developed by passionate individuals who share their work for free or follow an open-source philosophy.The introduction of these filter controls is part of an ongoing effort to improve the browsing experience and refine the visual aspects of the Theme and Plugin Directory as part of the site redesign.Users are encouraged to provide feedback on these updates and try out the new filter controls.Link: Original ArticleThe Power of Community: A WordCamp Europe Sponsorship StoryImportant Takeaways:Barn2 Plugins sponsored WordCamp Europe (WCEU) for the first time in June 2023. The experience was described as a great opportunity for networking, brand exposure, and team bonding.The company spent a total of €13,256 on the event, including sponsorship costs, travel and accommodation, team t-shirts, WordCamp tickets, and other related expenses.The sponsorship booth was a key part of their presence at the event. They created a quiz for attendees, with winners receiving premium swag items. The quiz was a success, with 145 participants.The team also produced a video showcasing some of their most popular plugins, which was displayed at their booth.The author, Katie Keith, highlighted the difficulty in calculating the return on investment (ROI) for sponsoring a WordCamp. However, she emphasized the intangible benefits, such as increased brand awareness, networking opportunities, and team building.Link: Original ArticleSustainability Team • Supporting Organizations • Commercial & Community Themes & Plugins • Pattern Curation – Post StatusImportant Takeaways:The WordPress Sustainability Team has been established with the main objective of embedding sustainable practices into the WordPress community and its processes, focusing on ensuring longevity socially, economically, and environmentally.Several organizations exist to support the work of WordPress, such as The WP Community Collective and HeroPress. A proposal has been made to display such supporting organizations.Filters have been introduced for Themes and Plugins to distinguish between Commercial and Community efforts. The Patterns Directory is considering using filters for displaying all patterns associated with a theme.The post also includes a roundup of other WordPress news, including updates on WordPress 6.3 and 6.4, WP-CLI releases, community events, core updates, design updates, and more.Link: Original Article ★ Support this podcast ★

In this Episode: Learning, then Teaching WordPress DevelopmentCarrie's path to WordPress was an interesting one. She started in web development doing ASP.net, before quitting that and going to work at a Starbucks. She went there because she had aspirations of opening her own coffee shop, and thought on the job learning was the best way to do it. While she was there, her managed introduced her to WordPress. She started freelancing, and was easily able to replace her Starbucks income with freelance income. From there, she dove into Lynda.com (now LinkedIn Learning) courses to learn WordPress, and eventually started teaching there herself. Her approach to teaching develop is fantastic – definitely worth having a listen just for that! Key TakeawaysOne of the most rewarding things about being a freelancer is helping different companies work through a solution. By mixing up your client base and not just taking the easy jobs, you get to solve different problems. When it comes to teaching WordPress (or anything), start with an assumption about the learner. What do they know? What do they need to know? What's the primary outcome for the course? Learn something like you're going to teach it. Don't just know how to do it – understand the “why” behind the “how.” Even if you don't make courses or do talks, this skill will help you with coworkers and clients. There's a lot of knowledge to share! Don't keep things to yourself for “job security.” Use the tools that work best for you. For Carrie, VS Code, GitHub, and WP-CLI are invaluable. Don't just use tools because they're shiny and new. Determine if you need them and what you need them for.  The Official Plesk Podcast: Next Level Ops FeaturingJoe CasabonaJoe is a college-accredited course developer and podcast coach. You can find him at Casabona.org.Carrie DilsCarrie Dils is a Frontend Developer and LinkedIn Learning Instructor

The WordPress Dashboard is a typical GUI with specific use-cases in mind. CLI is way more expressiveIt's also a much more scalable solution because you're not dealing with the assumptions of Core developers. You can create anything you'd like.When you're running a Dashboard solution, everything is a standard web request. With WP-CLI, you run the commands through shell.It doesn't just allow easy scripting, but for a normalization layer. If you have a common set of tools and settings you use for each site, WP-CLI can normalize the installation process for you. You can start off simple, updating Core, themes, and plugins, and then move on to more complicated actions. There are very powerful commands to do imports and exports, combined with search and replace.This allows you to have fully automated site migrations.WordPress has been changing rapidly, and WP-CLI is trying to keep up. They're working to make sure everything works with Gutenberg. They're also working to ensure WP Scaffold, a feature that allows you to spin up new plugins and themes, works properly. Any plugin can integrate and support WP-CLI by adding their own set of commands. For example, if you use a Forms plugin to gather submissions, you can use WP-CLI (integrated with that forms plugin) to gather all of the data, and create beautiful reports and charts.The possibilities are endless with WP-CLI. It's really the most uninhibited version of WordPress you can get.

WordPress 5.9 ha visto la luz, pero no solo esta aplicación trae novedades. También lo hacen WP-CLI, Openverse, Gutenberg o las Apps.

In today’s episode we talk about using WP CLI to manage your WordPress site.

En este nuevo episodio comentamos las noticias destacadas de la quincena(sí, incluida la caída de Facebook y WhatsApp coemntada por Antoñito). Pero además, webonadas, vulnerabilidades, la voz del pueblo y nuestro Can I play with WordPress hablando de WP-CLI

Hoy lanzamos curso de WordPress CLI y respondemos preguntas sobre empezar a emprender, condiciones de venta, validación de memberships, diferenciación en nichos saturados y mucho más.

In our monthly WATCF installment, we discuss important updates regarding WordPress 5.6, WP-CLI, and other news from around the WordPress community. If you don't have time to keep up with all things WordPress listen to our round-up and get the month's most important WordPress news in one go. Listen to this episode of PressThis now!

Síguenos en: Después de haber publicado un par de plugins en el repositorio de WordPress este último mes bajo la marca de OsomPress y ahora que lo tenemos reciente y fresquito, vamos a repasar un poco los pasos a dar y cosas a tener en cuenta cuando tenemos que subir nuestro plugin para que lo aprueben y esté disponible desde cualquier instalación de WordPress. Pero antes, como siempre.... ¿Qué tal la semana? Semana esther Solucionado tema checkout WooCommerce  Varias revisiones malware Supervisando proyecto WP y ayudando temas específicos CSS Sesión Show me the Code de El Arroyo Club con Carlos Longareda Contenido esther Preparando módulo seguridad Script para actualizar gastos envío checkout Semana Nahuai Movida con SendinBlue, no segmenta por productos comprados a pesar de que lo publicitan en su web. ????????‍♂️ Integrando Restrict Content Pro con WooCommerce y Mailchimp. Preparando textos para la web de OsomPress. Contenido Nahuai Tema de la semana: Lo principal echar un ojo al handbook: https://developer.wordpress.org/plugins/ Respetar estándares de códigoTener muy presente temas de seguridad (escapar, sanitizar….)Ser cuidadoso con las notificaciones del adminTener en cuenta la internacionalización, hacer las cadenas traducibles.Procurar que los textos del backend son descriptivos.Crear un fichero .pot (se puede hacer con Poedit Pro o WP-CLI)Escribir el read me descriptivo que permita entender que hace el plugin de forma rápida.Enviar el plugin a revisión. (wordpress.org/plugins/developers/add) Una vez aprobado subir los ficheros + capturas de pantalla en svn (Xversion)Realizar traducción al castellano desde translate.wordpress.org (read me) y/o la app Poedit.Actualizaciones del plugin (necesario para incorporar nuevas cadenas). Validación y formateo de código con Visual Studio Code: PHP Code Sniffer (phpcs)Phpfmt (PHP formatter - Visual Studio Code extension)WPCS (WP Coding Standards)CSS Formatter (Visual Studio Code extension) En este artículo de TabernaWP tenéis un artículo de como instalar algunas de estas herramientas. Obviamente, también hay que seguir las guidelines (no trackear sin permiso, nada de contenido ilegal…). Glosario para las traducciones al castellano. Novedades Hemos migrado varias páginas sin problemas. Hay que tener en cuenta que si tienes CSS personalizado debes de reemplazar el prefijo «ab-» por «gb-». También he actualizado a Restrict Content Pro 3.4.4 y sin problemas. Tip de la semana Crear el fichero .pot usando WP-CLI. Ejemplo: wp i18n make-pot ./ languages/osom-modal-login.pot  Menciones Aritz recibió su merecido GIF y nos denominó «Podcast de culto». ???????? Jesús matiza: «Son muy achuchables y muy profesionales????» Bodhan comenta que seguramente nos referíamos a Show Current Template para mostrar la template de la página activa???? Maria en la red nos comparte en Twitter. Xavi nos da las gracias y nos felicita por el plugin. Adrián nos saluda y comenta que es muy fan de Query Monitor y usar background-color:red. Gracias a: Este episodio está patrocinado por StudioPress, los creadores de Genesis Framework, el entorno de trabajo de temas más popular de WordPress. Ya está disponible Genesis Pro para todo el mundo, 360$ anuales que dan acceso a: Genesis FrameworkChild themes de Genesis de StudioPress1 año de hosting en WP EnginePlugin Genesis Pro (Diseños y secciones, restricción de bloques por usuarios…) y Genesis Custom Blocks Pro.

WP CLI to potężne narzędzie, które może Ci pomóc w codziennej pracy z WordPressem. W tym odcinku chcę wprowadzić Cię w temat zarządzania WordPressem z poziomu konsoli. Dzielę się tym w jaki sposób automatyzuję sobie pracę przy pomocy tego narzędzia. Notatki do odcinka: https://maciejkuchnik.pl/011/ --- Send in a voice message: https://anchor.fm/maciejkuchnik/message

Es una herramienta que incorpora una interfaz de comandos a tu WordPress.Permite realizar muchísimas acciones desde una consola de comandos. >> #93 WP-CLI

On this episode, Jason Tucker and Bridget Willard get sentimental and invite past guests to jump on and share what they've learned recently in WordPress. We're all life-long learners. Come join in the fun in the chat and see more details in our Facebook Group. 100 Episodes since October 2015!!Bridget WillardJason TuckerBridget: “As we learn and grow and teach, our bio’s change and grow!”Russell AaronHas been on WPblab off & on since the beginning and was on nearly weekly in the beginning when it was more of a Q&A showHis girlfriend was super supportive of his journey in WordPress and let him spend the time he needed coding and ‘leveling up’ his skills. They now have a little boy, which is also a big learning journey for them!Never thought he could work for a company like WebDev Studios but met the right people and answered the right questions and here he is! Over 2 years with them now!If you are ever having errors, you have 3 options – make a backup and try turning things on and off, have a staging site, and reach out to people you are connected to in the community – lean on other people!WordPress is so cool! Put your heart into it and you’re gonna love it! Kevin HoffmanKevin remembers WPblab when it was still on the Blab platform!Blab was an interesting beast, you never knew who would pop in! Bridget: it was like Chatroulette!Had to keynote WordCamp Pittsburgh on 2 days notice, so he covered his WordPress journey, which basically all started with WPblab. Decided to try and run his own blab – talked for 30 minutes and no one showed up! Realized that he wasn’t putting things on record – not writing blog posts or sharing his work.  People don’t always operate on your time. I have value to offer but it doesn’t mean the person on the receiving end is ready at that moment. He worked on WordPress for 7 years before he wrote his first blog post! James TryonEasily Amused, Inc and Wapu.usJames has been on & off the show for a long time, helping with show notes too!Bridget: For a long time WPblab was a virtual meetup!  It was a great option for people who had meetups far from them.James looks forward to it every week, it makes his Thursday night! Loves the chatting, and hanging out with everyone!  Even though he’s across the country, it feels like everyone is together on Thursday nights!Jason: it’s so strange because he’ll see people online and through Blab all the time and then see them in person and it will be like they’ve just seen each other, even though they are on opposite coasts – all thanks to WPblabJames’ word of wisdom – he has been thoroughly enjoying an hour a day of yard work lately! Exercise and fresh air!He really loved WP Watercooler but WPblab feels like home to him. He looks forward to it every Thursday and feels bad when he has to miss it. We all feel like family!Bridget: “It’s so true! If I have a panic attack while I’m at WCEU, will any of my friends be there?” And so many people jumped up to say they would! Roy SivanHad him on several WPblab shows in the past & interviewed him several timesHis favorite memory was getting in a deep conversation with Bridget about open sourceOne thing that impresses Bridget most is that Roy and none of the WP Crowd ever talk down to her about WordPress & her level of knowledge/skills“For every good developer, there is a user to give that developer purpose!”You’re a user and without you, I have no reason to build this thing – but you give us purpose and a reason to create!Bridget: you can have a cognitive dissonance if you aren’t using your product. Even if you knew it once a few years ago, if you haven’t used it since, everything has changed! The whole crewRoy’s shoutout – go over to Matt Cromwell’s twitter to check out a video of trolling BenRoy – he loved how Jason was always doing tech support with Blab!Bridget – you want Jason to be the “guy” – you certainly don’t want it to be me!Bridget – I don’t build websites, hire Roy!Bridget – just wrote her first WordCamp talk on GitHub with Markdown!All – discuss how much (or if any) company logo can appear on WordCamp talk slides and still be acceptable for WordPress.tvBridget – WordPress has taught me how to go to bars – true story LOLBridget – WordPress.TV is the best – free learning! Lynda is great, but WP.tv is freeRussell – when I got to WordCamp, I want to learn, I don’t want to be bored!  WordPress.tv – if you ever want to see the energy of the community, that’s the placeRussell & Bridget both dream about their WordCamp talks Tools of the week:James: Google Drive is amazing for working as a team – we can all take notes on the same documents and share the same files. We use it all the time, along with Slack.Russell – WP-CLI (command line interface) – if you don’t know what the command line tool is and how amazing it is, go learn about it – it’s the best tool!Kevin: Look into BEM – Block Element Modifier (CSS naming convention)https://twitter.com/kevinwhoffman/status/987005921510526976Roy: SVG.js – complex animating with SVGs – really great library with lots of cool plugins – wrote a plugin called the Gutenburg Object Plugin. Takes the data and saves it properly in the database as an array instead of in markup format.Bridget: TouchNote – will send postcards of your photos & even canvas prints Also: STEP program with the State Department – connects you to US Embassy and give them your info for when you are traveling overseasJason: Markdown editor: https://macdown.uranusjr.com/ – simplest and free – MacDown. It’s 2 panes, type text on one side, renders Markdown on the other side Roy Question for Bridget – where you used to believe Open Source was not a good thing, how do you feel now? – When you have intellectual property and you give it away for free – it is your choice. The thing that’s great about WordPress, it’s not about planned obsolescence.  They don’t create something that will break to create new customers. This is the issue that she has with Gutenberg. WordPress believes that everyone has the right to publish and stands upon the idea that they will never break your site. Gutenberg might break that. What is the best solution for your customer/user?Bridget: The relationships and people are what makes WordPress valuable. WordPress is at a crossroads, do we want to stay with our core beliefs that it’s all about ‘democratizing publishing’ or do we bow to capitalism?I love WordPress, I love the community and I love the WPblab group even more!! ______________Show notes contributed by:Cheryl LaPrade – @yaycherylSherie LaPrade – @heysherie The post WPblab – 100th Episode Mastermind – Lifelong Learning with Our Community appeared first on WPwatercooler. See acast.com/privacy for privacy and opt-out information.

Life Updates Adam:  Life is good. Kyle: interviewed on Jeff Large's show. Watched the olympics opening ceremony. WordPress News WordPress 4.9.3 and 4.9.4 a day later WP-CLI has a new version out. Version 1.5 lets you verify the integrity of your installed plugins and do pretty much anything you want with wp-config.php, to name just…

Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards. In this episode, Brian and Brian discuss market segmentation across the WordPress ecosystem. The focus for this discussion focused entirely on the entry-level segment of site assemblers and their small-business clients as well as the mid-level market of contractors and agencies selling additional levels of service. The duo talked through a few different strategies employed in each segment, including service differentiation, regional focus, building a network of complementary contractors, systemizing processes, delivering quality customer support flow, and selling ongoing service. In addition to this look at market segmentation, the Brians shared a few useful resources for both Gutenberg and WP-CLI. Links Mike McAlister's Gutenberg News Ahmed Awais's create-gutenberg-block Delicious Brain's WP-CLI packages reviews WordPress Website: How much should it cost? Selling Ongoing Services with Sara Dunn Sponsor: iThemes This episode is sponsored by iThemes. The team at iThemes offers WordPress plugins, themes and training to help take the guesswork out of building, maintaining and securing WordPress websites. For more information, check out their website and thank you to iThemes for being a Post Status partner.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards. In this episode, Brian and Brian discuss market segmentation across the WordPress ecosystem. The focus for this discussion focused entirely on the entry-level segment of site assemblers and their small-business clients as well as the mid-level market of contractors and agencies selling additional levels of service. The duo talked through a few different strategies employed in each segment, including service differentiation, regional focus, building a network of complementary contractors, systemizing processes, delivering quality customer support flow, and selling ongoing service. In addition to this look at market segmentation, the Brians shared a few useful resources for both Gutenberg and WP-CLI. Links Mike McAlister's Gutenberg News Ahmed Awais's create-gutenberg-block Delicious Brain's WP-CLI packages reviews WordPress Website: How much should it cost? Selling Ongoing Services with Sara Dunn Sponsor: iThemes This episode is sponsored by iThemes. The team at iThemes offers WordPress plugins, themes and training to help take the guesswork out of building, maintaining and securing WordPress websites. For more information, check out their website and thank you to iThemes for being a Post Status partner.

WP-CLI is the command-line interface for WordPress.  It allows developers and site administrators to update plugins, configure site options, script batch processes, write custom commands, much more.Listen to this episode of Press This where we interview Director of IT at Actionable co, Shawn Hooper as he explains the power he’s learned to wield with the help of  WP-CLI.  Shawn is a WordPress Core Contributor, Lead organizer of WordCamp Ottawa, and frequent WordCamp speaker.

WP-CLI is the command-line interface for WordPress.  It allows developers and site administrators to update plugins, configure site options, script batch processes, write custom commands, much more.Listen to this episode of Press This where we interview Director of IT at Actionable co, Shawn Hooper as he explains the power he’s learned to wield with the help of  WP-CLI.  Shawn is a WordPress Core Contributor, Lead organizer of WordCamp Ottawa, and frequent WordCamp speaker.

Von der JVA zu WordPress

In today’s episode, we dive into the powerful possibilities of using WP-CLI to manage your WordPress site.

Aujourd'hui, nous recevons Claire Bizingre et Tanguy Lohéac pour nous parler de l'accessibilité numérique et comment cela se traduit dans WordPress.

Hoy tenemos un episodio un poco técnico donde explicaremos que es WP-CLI y que podemos hacer con esta fantástica herramienta que muchos desarrolladores de WordPress usan. No es una herramienta fácil de dominar pero cuando le pillas el truco, ¡está chupado! y te ahorra un montón de tiempo.

Hoy tenemos un episodio un poco técnico donde explicaremos que es WP-CLI y que podemos hacer con esta fantástica herramienta que muchos desarrolladores de WordPress usan. No es una herramienta fácil de dominar pero cuando le pillas el truco, ¡está chupado! y te ahorra un montón de tiempo.

Дамы и господа (леди и джентльмены) мы рады представить вам новый, долгожданный подкаст! Сегодня у нас много вкусного: разбор WWDC 2017, рассуждения по поводу дизайна и статистики, размышления о том, как быть стильным джаваскриптером, а также кучи новостей из мира WordPress. Пристегивайтесь и погнали. Тему к следующему выпуску предлагайте здесь: Тему к подкасту #129. WWDC 2017 Все новости на MacRumors «Дизайн» Как Facebook, Twitter и LinkedIn используют всплывающие подсказки. Редизайн Android эмодзи. Хочешь быть креативным, не ведись на big data. «Брутальные» редизайны популярных приложений на телефон. Веб-дизайн музей. «Светские новости» PayPal подал в суд на Pandora за логотип. «Разработка» Если бы Apple хостились в России, то они бы выбрали SmartApe!↓ Stack Overflow вывел из Vim уже больше миллиона пользователей. JavaScript: элементы стиля. Нужно убрать AMP, пока он не убрал нас. Новый формат — JSON Feed. Safari 11 и JavaScript — быстрее всех. «WordPress» HHVM исключен из сред тестирования. На Wordpress.com добавляют поддержку сторонних плагинов. Возможная ширина Кастомайзера увличена до 600 пикселей в WordPress 4.8 . WordPress 4.8 улучшает «доступность» в разметке админки. WordPress выбирает JavaScript фреймворк для ядра. WP CLI 1.2.0 вышел и сменил логотип. Чего ожидать в WordPress 4.8. С темами к выпуску можно ознакомиться по ссылке: Темы к подкасту #128. Спасибо всем, кто так или иначе принял участие, и дай вам Бог на эти коротенькие семь дней.

No me extiendo en lo que hablamos en el podcast, simplemente os enlazo las herramientas de las que hablamos, mejor que leer, disfrutad del audio: GravityView https://gravityview.co/ Poopy life poopy.life Oxygen App https://oxygenapp.com/ WP-CLI http://wp-cli.org/ https://buddy.works/guides/how-prepare-and-restore-wordpress-backups?utm_source=newsletter&utm_medium=email&utm_campaign=n_2017 Métodos de contacto Enviadnos vuestras preguntas tanto al formulario de contacto de http://avpodcast.net y https://potencia.pro/contactar como escribirlas en la página […] La entrada Potencia Pro 033: Formas curiosas de vender se publicó primero en Potencia Pro.

Heute sind wir mal wieder zu viert in der Runde und doch haben wir zwei Gäste in der Runde. Wir freuen uns, dass Felix und Alain wieder vorbei schauen auf unserem Sofa und mit uns über die kommende WordPress Version 4.8 reden sowie über die WP CLI. Alain ist inzwischen einer der offiziellen Maintainer der WP CLI und plaudert über die Arbeit und wie das Projekt voran geht. Und also ob das nicht genug wäre packen wir natürlich noch ein paar Termine und News aus dem WordPress Kosmos oben drauf. Viel Spaß beim Hören!

Se você também é um apaixonado por WordPress, pegue seu café e venha conosco. O Umblercast desse mês reuniu 3 especialistas em WordPress e vai responder todas as suas perguntas. PARTICIPANTES Flávio Henrique Marco Andrei Kichalowsky Rodrigo Donini LINKS INDICADOS NO PODCAST The WordPress Plugin Boilerplate: http://wppb.io/ WP-CLI: http://wp-cli.org/ Underscores: http://underscores.me/ Codex WordPress: https://codex.wordpress.org/ Sucuri: https://sucuri.net/pt/ Themeforest: https://themeforest.net/ WordPress Security Checklist: http://wpsecuritychecklist.org/br/

This week I revisit WP-CLI and talk about adding BASH to the workflow Upcoming Events WordCamp Jackson, MI  – May 5-6 WordCamp Porto Alegre – May 6 Segment 1: In the News WCUS Speaker Submissions are open.. WCLAX speaker submits are opening this week as well.. Segment 2:  WP-CLI & Bash workflow Past KSWP about…

This week I revisit WP-CLI and talk about adding BASH to the workflow Upcoming Events WordCamp Jackson, MI  – May 5-6 WordCamp Porto Alegre – May 6 Segment 1: In the News WCUS Speaker Submissions are open.. WCLAX speaker submits are opening this week as well.. Segment 2:  WP-CLI & Bash workflow Past KSWP about…

In this episode, Daniel and I get pretty heavy into development tools and using WP CLI, automated testing, and the future of WP-CLI and Open Source. We go a little long, but it’s a great conversation no matter what your background is. Show Notes Daniel Bachhuber WP-CLI Hand Built WP-CLI on make.wordpress Behat Automated Testing […] The post Episode 28: Daniel Bachhuber and WP-CLI appeared first on How I Built It.

Уважаемые подписчики, сегодня вас ждёт выпуск, в котором будет очень много дизайна, например, статью про UI и UX мобильных форм, заметку о том, что грядёт новый тренд в веб-дизайне — круги. Ещё поговорили про введение в service worker-ы на примере картинок Марико Косаки и обсудили какими бы автомобилями были языки программирования. Тему к следующему выпуску предлагайте здесь: Тему к подкасту #114. «Дизайн» Строим отличные мобильные формы. Джонни Рамон и его техника отбрасывания лишнего. Круги — новый тренд в дизайне? Популярные логотипы в виде emoji. «Светские новости» LEGO заупскает собственную социальную сеть для ребятишек. Зачем Маск прыгает в поезд Трампа? РПЦ запустила первый православный мессенджер. Взломаны сервера CD Projekt RED. Работает — не трогай. Unsplash 5.0. Учёные выяснили, что 40 часов — это слишком длинная рабочая неделя. «Разработка» Прокрастинировать с пользой можно с хостингом SmartApe!↓ Краткое введние в Service Worker. Если бы языки программирования были автомобилями. «Научно-популярное» Больше 50% трафика теперь зашифровано. Для woocomerce теперь необходимо учётную запись wordpress.com. WP CLI 1.1.0 вышел в релиз. Уязвимость WordPress REST API. Спасибо всем, кто предлагал темы к этому выпуску, с ними можно ознакомиться по ссылке: Темы к подкасту #113. Спасибо всем, кто так или иначе принял участие, и дай вам Бог на эти коротенькие семь дней.

WordPress 4.6, “Pepper”, has been released. It’s named, as always, after a famous jazz musician, and this release is named after Park Frederick "Pepper" Adams III, a baritone saxophonist and jazz composer. The Release Lead for WordPress 4.6 was Dominik Schilling, known often as Ocean90, and the Deputy Release Lead was Garth Mortensen. There were 272 total contributors to this release. According to Aaron Jorbin, 85 of these contributors were first timers, so congratulations to all new WordPress contributors! For this release, we did a special episode of the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle — the CTO of Human Made — and me, Brian Krogsgard. In this episode, Joe and I discuss WordPress 4.6 and deep dive on a few of its features. About WordPress 4.6 Overall, this was a planned iterative release from the beginning, with a goal to fix as many longstanding bugs as possible, and to refine existing features, rather than to focus on a lot of brand new features. Folks have been clamoring for a release like this for a long time, and in most respects 4.6 delivered. According to Trac, 489 tickets were closed, across 53 components, during the 4.6 milestone. Also, it shipped exactly on time. User facing features WordPress 4.6 has a few user facing features that aren't huge functional changes, but nice interface enhancements. Shiny updates No more bleak screen of sadness, as the team working on this termed it. The plugin installation, updates, and delete process is much smoother than it used to be. There's a nice video of this from the initial proposal: This was the second release where "shiny updates" features were a focus. To see some under the hood considerations for developers, there's more information on that from Pascal Birchler. Native fonts WordPress is leaving Open Sans. You may have seen GitHub’s change to native fonts. Or if you’re running 4.6 in development, you’ve seen native fonts replace Open Sans in the admin too. Matt Miklic explains the switch from Open Sans to native system fonts in the WordPress admin. By the way, the declaration of fonts has a good bit of science behind it, and may be useful for those of you who wish to do something similar for your site body copy. Marcin Wichary has a really interesting post describing Medium's process for the switch. And if you're curious, the new declaration is this: font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif; Inline link checker WordPress will now automatically detect improperly formatted links, as you write. While this doesn't check the validity of any properly written URL, it will ensure the URL you add in an href is properly formatted. So, it will catch if you accidentally type something like htp://w.org or http:/w.org and outline it in read for you to fix. If you copy and past a URL into the link editor, but don't include http:// at all (I do this a bunch), it auto detects and inserts it for you. Browser content caching Yet more efforts have been made to always ensure that you do not lose your content as you write. I followed the steps in the Trac ticket to see exactly what happens here. So I typed the first sentence below, saved a draft, then typed the second paragraph: What if I start typing and save a draft? Then start typing some more, because that's what bloggers do. And I chill here for a few seconds, then stupidly just reload this page? Then I reloaded the page without saving again, and got a notice that there is a more up to date version available. And just like that, the content is back, because it was saved in the browser's local storage. Pretty cool. Developer features There are several important developer centric features that you should know about. Enhanced meta data registration This is a significant aid to the (pending) REST API meta handling, but also improves other meta data functionality. The register_meta() function allows developers to tell WordPress more about what specific meta data is designed to do. In WordPress 4.6, the arguments for this function have changed, enabling more information to be communicated in the third parameter, which is now an array. The show_in_rest key, an experimental key (until the API endpoint goes in), finally solves the issue for the REST API for knowing when to include meta data in the API's default responses. It's one step of a few that need to be made to better support meta for the API, but it's a good step forward. For plugin developers not using register_meta(), be sure to learn more about it and the advantages, as there are quite a few. Jeremy Felt describes how to use register_meta on Make Core. Translation priorities and changes WordPress will now default to the translations from Translate.WordPress.org community translations, then pull from theme or plugin translation files. A procedure called “just-in-time” translation loading will be utilized, and for plugins and themes distributed through the official repository, load_plugin_textdomain() and load_theme_textdomain() no longer need to be used. Commercial plugin authors will still largely follow the same internationalization procedures they always have. In a related note, and quite impressively, WordPress 4.6 shipped 100% translated in 50+ languages. Resource hints Joe helped teach me more about resource hints on the podcast, and Aaron did a much better job detailing resource hints than I could, in his excellent field guide: Resource Hints is a rather new W3C specification that “defines the dns-prefetch, preconnect, prefetch, and prerender relationships of the HTML Link Element ()”. These can be used to assist the browser in the decision process of which origins it should connect to, and which resources it should fetch and preprocess to improve page performance. In 4.6, WordPress adds an API to register and use resource hints. The relevant ticket is #34292. Developers can use the wp_resource_hints filter to add custom domains and URLs for dns-prefetch, preconnect, prefetch or prerender. One needs to be careful to not add too many resource hints as they could quite easily negatively impact performance, especially on mobile. Resource hints can be very useful for certain situations, and it's a technique that I personally need to explore further. Those of you doing advanced performance-driven development will surely be excited about support for this in WordPress. Customizer APIs The Customize API continues to evolve and improve, and Nick Halsey walks through new developer-focused features and changes to the API for WordPress 4.6. Also quite notably, Weston Ruter describes new APIs for both settings validation and notification management in the customizer. Other developer-centric changes Multisite changes: Jeremy Felt describes WP_Site_Query and WP_Network_Query, and goes over a few new functions and filters. There is now a persistent comment cache, allowing more performant comment loading functionality. The WordPress HTTP API now uses the Requests library, as Ryan McCue describes. Aaron Jorbin describes some of the lower level WordPress loading priorities and defaults that have changed. He also describes how WP CLI and core have reconciled their differences in wp-settings.php, which makes backward compatability for WP CLI possible now. Boone Gorges describes the introduction of WP_Term_Query. He’s the term whisperer. As Joe and I discuss in the podcast, these sorts of changes make for better consistency in WordPress, and provide an improved developer experience. Learn more WordPress 4.6 is the result of hundreds of community members. You can find their names and links to their profiles on the official release post. Also check out the official 4.6 Codex page that has a lot of handy information and links to source Trac tickets. You can see all closed tickets from 4.6 on the Trac milestone. View all new functions, classes, methods, and hooks on the official Developer Reference. And learn more about some of what I discuss above, and other items, on the ever-helpful field guide. For the record, WordPress 4.5 was downloaded more than 45 million times. You can track 4.6 downloads on the page dedicated to the task. Thank you to everyone who contributed to WordPress 4.6! I hope you have a

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard. Today, we answer questions from Post Status community members, who asked us all sorts of stuff on the Post Status Ask page. If you'd like to ask a question, be sure to go there and we'll see if we can answer it on a future show. Questions & Links We answered the following questions: Why WordPress? In a survey I did before my PressNomics talk, the top answer for what's important to people in regards to the WordPress world was the quality of the community. WordPress' ubiquity -- powering 26% of the web -- helps too. What is the biggest mistake you made learning WordPress? (Or, what would you do differently?) Joe and I each shared what we tend to do wrong when learning new things. We are fully on opposite ends of the spectrum. Recommended link: Just Build Websites. Also, my post on learning WordPress holds up pretty well, considering I wrote it in 2014. Why did a lot of web and WordPress people get upset about the Mandrill pricing changes, when we want people to value the work we're doing ourselves? We discuss what made Mandrill's pricing changes controversial, and why we think some level of "outcry" is understandable here. Basically, Mandrill isn't differentiated enough to warrant the new pricing, in our opinions. However, it's obviously their right to change their pricing and structure, and the questioner has a valid point in how we value other services versus our own. Why isn't the WordPress importer being worked on more intensively? Good question! We talk about the state of the importer, some other options like WP Migrate DB Pro, WP All Import, and WP CLI. We also discuss how to get involved with open source development. Should taxonomies have the same feature capabilities as posts in the future? There's been a lot of interesting work on taxonomies in the last several releases, and you can read more about some of that and find links going back from my release post for WordPress 4.4. However, we think taxonomies and posts should be different. With the introduction of term meta, it is more important to consider architectural choices well in advance. Finally, the Fields API will be interesting in how it affects customizing term edit screens. How should I use my own domains with Multisite? This turned interesting! Fortunately, Multisite component maintainer Jeremy Felt came through while we were on the show to point us to tickets that were merged in WordPress 3.9 for enabling simpler domain mapping, and in 4.3, when a better UI was introduced. So, today, it's much easier to use a custom domain in a network -- within the existing WordPress Multisite options interface -- versus using a tool like Mercator. In addition to these questions, we also banter on about some other things and answer a few less serious questions we go from funny listeners. And at the end, I make a pretty big announcement... Today’s podcast is sponsored by Design Palette Pro. Design Palette Pro makes it easy to customize pretty much any Genesis theme, without touching code. It’s perfect for when you’re helping a friend with a website, but they don’t have a full service budget and you don’t have time to custom code every element. Get a great website in no time, with Design Palette Pro. Go to GenesisDesignPro.com for more information. Thank you to the team at Reaktiv Studios, who builds Design Palette Pro, for being a Post Status partner.

This week I talk about WP CLI: What it is, why I wanted to use it and why it's awesome! Upcoming Events SouthBay WordPress Meetup Holiday Potluck No WordCamps left this year. :( Segment 1: In the News WordPress 4.4 did ship “Learn Javascript Deeply” — Remkus de Vries wrote a great recap/resource Segment 2: Introducing…

This week I talk about WP CLI: What it is, why I wanted to use it and why it’s awesome! Upcoming Events SouthBay WordPress Meetup Holiday Potluck No WordCamps left this year. :( Segment 1: In the News WordPress 4.4 did ship “Learn Javascript Deeply” — Remkus de Vries wrote a great recap/resource Segment 2: Introducing…

Welcome to the Post Status Draft podcast, which you can find on iTunes and via RSS for your favorite podcatcher. Brian and his co-host, Joe Hoyle, a co-founder and the CTO of Human Made, discuss some of today’s hottest, current WordPress news. In this episode of Draft, Joe and Brian discuss micro plugin businesses and playback a recent interview with Barry Kooij. They also tackle WP-CLI, what it is, why it’s useful, and ways they use it the most. The interview with Barry starts around 3:00 in and ends 20:00 in, for members that would like to skip it, if they already heard it in the main newsletter. WP-CLI discussion starts around 44:00. Topics & Links Niche Plugin Businesses Never5 Shop Plugins WP101 SearchWP FacetWP SeedProd GravityView GravityPlus Event Organiser Theme of the Crop WP-CLI WP-CLI WP-CLI Built-in commands Community commands S3 Uploads by Human Made (has built-in CLI integrations, instead of a UI) A more RESTful CLI

On this episode of WPwatercooler we will be discussing WordCamp SF 2013, the State of the Word address and after parties.The Hallway TrackThere are many “Man” or “Woman on the Street” interviews that were conducted by Jason Tucker and Se Reed. Those can be found soon on the WordCamp San Francisco WordPress.TV page.State of the WordState of the Word address by Matt Mullenweg:* OCWP got a big shout out for their 10th anniversary party.* WordPress release cycle – updates and plugins will be updated the most* The release of 3.6 has been postponed* 3.7 and 3.8 release being so close together will create a lot of problems for people that use it in an enterprise setting* Matt said the releases will be small updates with less iterationsVideo can be found here: State of the Word 2013Our favorite sessionsMike Schroeder – WP CLI (command line interface) talk was really excellent. His talk isn’t stagnant. He’s constantly fine tuning it so there is always good, new information.Helen Hou-Sandi – Customizing the WP Admin interfaceCarrie Dills – her talk “Co-opetition” Cooperation, collaboration and competition was great. She highlighted best of competition as well as collaboration.Josh Broton – on Responsive Design. There were 2 huge takeaways: 1) making photoshop images 2.2x bigger and setting quality to 0 then scaling down in the browser saves a huge amount of work. 2) Text in line? justify for grid layouts, if you text in line justify the parent elements and use display inline block on the child elements, you can have completely justified grid system.Natalie MacLees – Her room was packed out. She gave her talk in a really compelling story-telling manner.Mika Epstein – Don’t Use WP Multi-Site. She gave basics of what the watch out for if you want to use WordPress multi-sites.Ian Stewart – Themes – Super passionate and really inspirational. Do not miss it when it’s on WordPress TVContributor Day* The most people that have ever gone to contributor day.* Steve learned how to commit a patch* There was a large focus was on the support and documentation team. That’s where Se and Suzette spent their time. They worked on the Theme Developer Handbook. There will be no standardization for theme options.Shout out to the DradcastActivities we did after WordCamp San Francisco 2013* Pandora Karaoke Bar* Tonga Room* Fang[LISTATTENDEES event_identifier=”ep45-wordcamp-san-francisco-2013-wcsf-recap-wpwatercooler-5-51f589d53223f” show_gravatar=”true”] See acast.com/privacy for privacy and opt-out information.

WP-CLI was a game-changing addition to the WordPress universe when it was released and has since evolved to be a powerful toolkit for advanced dev teams seeking to speed up their workflows or introduce automation into their WordPress builds. As WP-CLI continues its march forward though, backwards compatibility presents challenges that need to be overcome.In this episode of PressThis, we interview lead contributor for WP-CLI Alain Schlesser about his thoughts on what has been accomplished with the WP-CLI roadmap over the last year, what backwards compatibility challenges lay ahead, and how those challenges are being addressed. Alain also shares a bit about the need for contributors to WP-CLI and how you or your dev team can help.If you rely on WP-CLI in your WordPress builds, or are just curious about the evolution of this INCREDIBLY important part of WordPress don't miss this episode of PressThis. Listen now!Support this podcast at — https://redcircle.com/press-this-wordpress-community-podcast/donations