We often set up a staging site for the client and then move the staging site into production. With WordPress, content is both file-based and found within the database. Synchronizing files is fairly simple, but synchronizing databases isn’t as easy. RAMP is a tool developed to help firms migrate their WordPress content between sites.
RAMP allows you to make changes in your staging environment, then selectively push these changes to your production site. Once content has been reviewed and approved, you can go to your RAMP page, select these content changes, and push them to your production site.
RAMP will run a special pre-flight check that will make sure that everything will go smoothly and allow you to double-check what you’re planning to push – including:
- Categories, tags and users that are referenced by other posts, pages, etc. will be created automatically in production.
- When a child page is included on a batch without the parent page, and the parent page doesn’t exist in production.
- A selected child category where the parent category is not in production and isn’t part of the batch.
- If an image is selected to be included in a batch, but the image was deleted from the file system (outside of WordPress).
- If a page, category or tag is included in a selected menu, but doesn’t exist in production and isn’t part of batch.
- Content that has changed on production and is newer than the changes on staging.
RAMP also includes a roll back button for the latest batch. Thank to our clients at HCCMIS, an insurance provider for travelers, who let us know they are testing the system.
The average piece of content takes 20 hours to create and costs approximately $1,200 to produce. And yet, 60-70% of B2B content sits unused, collecting dust in the depths of your blog or resource center.