2 months ago, I travelled to Vienna, Austria, to attend WordCamp Europe – my favourite conference in the world! It’s such a huge event and a great opportunity to catch up with old friends as well as making new ones. At WordCamp Europe, Matt Geri did a talk on “The Ultimate WordPress Development Environment”, including using WP Pusher for deployment.
Source code control is nothing new to software development. It’s been around for decades. But for those of us who work in the open source community, specifically those who are working with WordPress, we may not have the experience that some of our peers have.
After all, many of the people who work on or work with WordPress are people who are seasoned software developers or who have been working on software for a long time.
The online Subversion repository for a simple WordPress plugin.
And to be clear, this doesn’t mean they learned source control within the context of open source development – maybe they did, maybe they didn’t. In short, they’ve had time to learn the advantages of workflows for and reasons why source control is so important.
Ultimately, the point I’m trying to make is this:
If you’re new to WordPress, and you’ve heard about source control, Subversion, Git, or GitHub or even used it to some degree (even if you aren’t entirely sure what you’re doing), that’s okay! Everyone starts at the beginning.
The purpose of this primer is to help explain some of the benefits of source control, why we use it, and how it plays a role in our day-to-day activities especially when we’re working with others.
TLDR; You can now purchase a WP Pusher license with a monthly subscription, instead of paying for a full year up front. Plans are ranging from $4 to $20 per month and come with our usual 30 day money back guarantee.
Git and the command line can be a daunting prospect, luckily there are multiple Git GUIs, which work across a variety of platforms such as, OSX, Windows, and Linux.
In this post, we’ll be taking a look at the two most important ones. GitHub Desktop and SourceTree by Atlassian, the company behind Bitbucket.
Yesterday, Taylor Otwell released Laravel Valet, a development environment for Mac minimalists. It didn’t take long before Taylor also released a driver for WordPress, which is why I thought I’d do a write-up here on the blog.
If there is one thing I do not understand, it is why you would run a WordPress agency without operating in a niche. If you are running a business selling WordPress based websites, you literally run the most common online based business in the world. Why would someone choose you? How would they even know that you exist?
Today I want to talk about that. Niches. Last week we talked about leveling up and productizing your services and this is very much related. Side note: I originally thought this blog had to be about Git and GitHub, but I guess there are really no rules. Whatever is relevant to people running a WordPress based service business is relevant here. Back to niches. I’m obsessed with them. They are so powerful and if you haven’t realised it, I want to convince you. So please continue reading, okay?
The headline of this post sounds like true click bait. I know! It really isn’t, though, because leveling up your business is exactly what I’m talking about. So bear with me. I want to try something different. Instead of talking about Git, I want to talk about business. I love business. I love talking about businesses and I love running a business. So today we are going to talk about – business! If it works, I will keep doing it once in a while, and if not… Well, let’s hope it works! Let me know what you think in the comments or by sending me an email.
Push-to-Deploy is the feature of WP Pusher that will keep your WordPress websites up-to-date every time you push some fresh code to your Git repositories. In this post, we are going to take a look at what Push-to-Deploy is, how best to use it for an effective workflow.
Last week I wrote a guest post over on the WP Tavern about how fundamental Git is for WordPress teams. In the post, I mention 3 signs that will make it obvious to me that your WordPress development team is not in fact working as a team – but rather as small 1-man teams. The 3 signs are:
- Lack of version control
- Lack of a code collaboration platform
- Lack of a deployment strategy
Git is a fundamental enabler of team work, so without it, it’s hard to get to step 2 and 3 in that list. If you want to read the article, check it out over on WP Tavern.
As part of the Git for WordPress video course, Danny van Kooten shows how he uses Git to release a new version of his plugin MailChimp for WordPress.