How to set up a development site

These should be the default steps to follow in order to set up a solid development environment.

  • install an instance of WordPress on your development server (TSO host)
  • remove the “admin” username, change the default username password & email address (save details on LastPass)
  • add an admin user for (do not use obvious username, use something fruity, ie: PinkApple, BlueBerry, etc)
  • edit permalinks under Settings – select “Post name” or if it’s a very active blog, use either “Month and name” or “Day and name”
  • tick the “Discourage search engines from indexing this site” box under Settings –> Reading
  • add this new development site to BlogVault & Bread Board
  • edit site title, tagline, email address and site language accordingly under Settings –> General Settings
  • if the client doesn’t want to bother moderating blog comments, untick the following under Settings –> Discussion Settings.
    — Allow link notifications from other blogs ( pingbacks and trackbacks)
    — Allow people to post comments on new articles
  • delete all default content (Hello World! post, Links and About page)
  • get rid of pointless themes
  • get rid of pointless plugins
  • install the Plugin Auditor plugin and do add information about all other plugins 🙂
  • install the captcha plugin
  • install the maintenance page plugin (regardless of sensitive info)
  • add the Yoast SEO plugin. This step could be done before launch but since you are at it you might as well do it now
  • add Stream to monitor user activity, in case something hits the fan you’ll know who did what
  • add the WP Help plugin, this will help you store any help topic within the admin area for easy retrival by the client
  • make sure you use the latest version of WordPress, plugins and themes
  • after buying a fresh instance of the theme (from ThemeForest) download and store the licence certificate in the notes section of the corresponding project within RedBooth
  • some premium plugins might require registration in order to receive updates of the 3rd party plugins that came with it
  • after you select a theme with the client, create a child theme
  • before you start customising the theme, set up a Git repository

That’s all for now, happy developing.

How to deploy a website

A ‘dummies’ guide to site migration

There are a few ways to deploy a site and as Project Managers, it’s important that we can do so easily, and within realistic timelines.

The BlogVault way

We have access to blogvault and if you were to create a staging site on Wholegrain server, you’d be taking regular backups in Blogvault.

This makes it very easy for us to ever migrate the site from one server to another as long as we have the FTP and cPanel details of the target server. Before you start anything at all, you want to create an empty WordPress installation on the final server to which you are transferring the site. This allows the Blogvault software to pull through the database details during the transfer.

When you’re ready, to transfer the site, you need to click on Migrate site from the More options menu next to the site you’re planning to transfer (see below).


If you need to share more detailed instructions with a client on how to copy data in between the production and the staging environments, please refer to the BlogVault Staging Sites Tutorial.

The Flywheel way

Login into Flywheel and scroll down to find the link that says Begin a Migration.


Follow up by next steps by filling the details in this form

Answer 3 questions below sensibly. In most cases, you want to transfer billing to the client. There shouldn’t be a site that we want to overwrite and check before saying that there are no important directories in the root.



Unless the client is in a proper hurry, which we need to charge for – we can ask them to migrate the site with standard migration.

The WP Engine way

Install on your staging site and follow instructions. This page displays a video for you to watch

Once the site is migrated, of course go through the post launch list in every case.