This page describes the tools used at Yoast when developing the various plugins and libraries.
Note: These instructions assume you're working with OSX.
Homebrew is a package manager for OSX, similar to
pip and allows you to easily install and update software from the command line.
Installing Homebrew is pretty straight-forward:
- Open your terminal:
- Run the following command:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
More information about how to work with Homebrew can be found at: http://brew.sh/
Iterm2 and Oh-My-Zsh (Optional)
iTerm2 is a replacement for the default terminal application that can be found on Mac OSX. The reason we suggest you install this is because it adds a lot of extra features when working in your terminal. Click here to see what kind of snazzy features are included!
Oh-My-Zsh is a shell for your command line that adds certain features that can't be done in a regular shell without a lot of hassle. It also allows you to more easily manage your zsh configurations.
You can install both by running:
brew install --cask iterm2
sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"
After installing both you'll want to change your shell from bsh to zsh by running
chsh -s /bin/zsh. Otherwise you won't get to see all those snazzy features from Oh-My-Zsh.
- ZSH can display the current active Git branch in your shell.
- Better auto-completion for directories and filenames.
Git / GitHub
Within Yoast, Git is used for version control. Don't know how Git works? Check out this tutorial. Our Git repositories are all hosted on GitHub. If you don't have one already, go and create an account.
Install git by running
brew install git
Add a global git ignore file so you don't accidentally add system files like
.DS_Store to the repository.
At Yoast, we make use of Local as the foundation for our development setup.
- Go to Flywheel's preferences » Advanced » Router Mode and set it to "Site Domains".
- Create a new site, call it basic.wordpress.test.
- Optional: make sure your browser / system trusts the SSL certificate of the newly created site.
- For macOS that needs a few steps, docs here.
To manage and search your database in an easy and quick way, Sequel Pro is the tool to use. You can download the latest version from: https://www.sequelpro.com/
To find out how to connect to the Docker database, check out the instructions on the Plugin Development Docker repository.
xgettext is a GNU internationalization (i18n) and localization (l10n) library. At the time of writing this is needed to build the wordpress-seo plugin.
brew install gettext
brew link gettext --force
As the plugins are written in PHP, it is necessary to have PHP locally installed.
brew install firstname.lastname@example.org
PHP extensions are distributed through PECL. Pecl is installed with PHP, but you may need to make it accessible on your computer's path. Find the PHP bin directory, which should follow the pattern (or a similar one) below:
Brew PHP Switcher (Optional)
Please note: Currently only usable with Homebrew.*
Brew PHP Switcher is a simple shell script to switch your Apache and CLI quickly between major versions of PHP. Useful if you support multiple products/projects that are built using either brand new or old legacy PHP functionality.
Assuming you're running the latest version of PHP and want to downgrade to an earlier version, you can do the following:
- Install PHP 7.2 (or older) with
brew install email@example.com
- Install Brew PHP Switcher
brew install brew-php-switcher
- Switch to PHP 7.2 (or older)
- Reopen your terminal and check the PHP version
Composer is a package manager for PHP and is used in our WordPress plugins to manage code dependencies in an easy way. To install it, run the following command in your terminal:
brew install composer
After Composer has been installed, you'll be able to run the following command in the plugin directories which contain a
composer.json file to install all necessary dependencies:
Note: To update the packages, run
composer update. However, this is generally something that isn't necessary to do.
XDebug using Local
If you use Local as your development environment, XDebug should already be installed on your local site. To enable XDebug in your IDE, use the following steps.
Make sure that these paths are included in your PHP include path:
~/Local Sites/<site-name>/app/public: the folder where the WordPress installation is located.
/Applications/Local.app/Contents/Resources/extraResources/local-bootstrap.php: A file used by Local to bootstrap the site.
You can use these steps to include these paths in your PHPStorm project.
Make sure that these paths are mapped to the right paths on the server:
~/Local Sites/<site-name>/app/publicshould be mapped to the same path (
~/Local Sites/<site-name>/app/public) on the server.
/Applications/Local.app/Contents/Resources/extraResources/local-bootstrap.phpshould be mapped to the same path (
/Applications/Local.app/Contents/Resources/extraResources/local-bootstrap.php) on the server.
You can use these steps to add these path mappings in your PHPStorm project.
Node via NVM
First off, install NVM. After that, you can install a node version by running the following command
nvm install <version>
Check the Node.js website to see what the latest LTS version is.
brew install yarn
package.json file prior to running:
To install Grunt CLI, run the following command in your terminal:
yarn global add grunt-cli
After this has been installed, you can run various commands in your project's directory to deal with various tasks. A command that is usually used is
grunt watch. This command will watch for changes in directories and run a set of predefined commands over the source code to ensure it's properly outputted.
As our repositories use a lot of similar tasks, we ended up creating a repository to bring these similar tasks together.
Please make sure you also check out the Grunt directory and especially the
aliases.yml file to see what commands are available.
To assist in debugging WordPress (plugins), you can make use of the Debug Bar plugin.
What this plugin can do for you, is log what queries have run, what environmental parameters are defined and can help you find other obscured (but useful) data.