After a VIP Go single site or multisite is launched, there may be new business units, campaigns or redesign initiatives that require new sites within the organization. In our experience, using one of the flows outlined below has allowed clients to successfully launch their new content on the VIP Go platform.
Creating a new subsite within the multisite network #
The Super Admin, an administrator who manages the multisite network, will need to be the one to create this new site by going to My Sites -> Network Admin -> Sites -> click Add New and fill in the details for the new subsite.
By default, all subsites use a subdirectory structure; this path can be changed to a new domain as part of the launch process. Please see our documentation for multisite on VIP Go for more details.
Note that newly created sites are not automatically connected to Jetpack, Akismet, and VaultPress. If you’re hoping to utilize a specific Elasticsearch index as well, this will need to be set up for the website by VIP Support.
Please reach out to VIP support after creating the new subsites so that we can connect the desired features for you.
Site redesigns #
There are times when a site is undergoing a redesign for a campaign or general freshening up with new coding and content updates. Remember that VIP’s platform uses a content-down and code-up workflow. This means that any new content needs to be added to the production site and then synced down to child environments, and new code should be tested on the child environment prior to merging to production.
This workflow ensures there is nothing unwanted introduced into the live production environment from any child environments which can have adverse risks like taking down the online site or even opening it up to security issues.
If working on updates for a single site #
At VIP, content must be authored in production and then sync’d down to a child environment for testing. This ensures that content does not need to be imported into the live environment close to launch, which could cause the site to be taken down if anything is amiss. It’s also important to note that VIP does not accommodate child environment -> production environment imports into live (sites receiving traffic) environments.
Leaving content in a draft-state in production makes it so that on your go-live date, all your team needs to do is bulk-publish the new content on the live site and then merge Pull Requests containing the new code.
If working on updates for a site within the multisite network #
We’ve seen clients successfully launch redesigns by using MultilingualPress’s “Based on site” feature to create a new subsite within the network based on the original site they are intending to edit. From there, your team may stage the site with new content, code directly on production, and use the Maintenance Mode plugin to keep this site redesign out of the public eye if needed.
Please contact VIP Support if there are any changes we will need to assist with — including search-replace commands, indexing Elasticsearch; Jetpack, Akismet, or VaultPress connections; etc. — five business days prior to your anticipated go-live date. You’ll find some common launch expectations in our Launch day playbook.
Requesting a new environment #
In some cases (different team or agency access, security reasons, etc.), a subsite within a multisite network will not suffice, and a new VIP environment will need to be created for your team.
Request a new environment with VIP by submitting a new ticket to our support team at https://wordpressvip.zendesk.com/. In the request, please include whether the new environment should be a single site or multisite environment and if there are any child environments (pre-production, develop, etc.) that you’d like spun up as well.
Please contact your Relationship Manager if you are unsure which new environment will fit your business needs.
We look forward to assisting you with your next site launch!