We rebranded to wildcloud; formerly known as WPCS. 

Build a WPCS Product in 5 Steps

Ready to scale your WaaS* or WP-SaaS? In this second installation of our introduction series, we demonstrate the WPCS platform by building a Product in 5 steps.

*WaaS: Website as a Service (standardizing and developing your websites like a SaaS)

As you may know, WPCS.io is the WordPress multi-tenant cloud platform that enables you to unify the development of your Website as a Service and manage all your WordPress installations as one. No matter how many sites you have, you only have to develop and manage one.

Having said that, the question that arises is: how do I build my WPCS Product?

This video series walks you through the platform by the example of an LMS product, one of our most common use cases. Let’s have a look at the contents per video:

Installing the Plugins (in the Version) #

The goal of this video is to inspire and teach you how to build a Version, making sure that future maintenance is minimized. If you follow along with this video, you’ll be able to unify not only the management of your tenants (client websites) but also your storefront in a single Version.

As mentioned, this video series shows you all this by the example of an LMS product. However, you can apply this for any type of WaaS or SaaS.


Launching a Storefront (by creating a Snapshot) #

This video explains how to build a Storefront that will enable you to spin up new Tenants in WPCS after your customers make a purchase. This will enable you to sit back and relax as the sales of your business become automated. The goal of WPCS is to enable you to scale and your new storefront stands as the foundation of that endeavor.

One of the most important features in this video is the use of our Snapshots to create different templates for your Tenants. One of the uses of a Snapshot is as a starting point for your new sites. This video demonstrates which plugins we use for the Storefront, after which we create a Snapshot to use for our Storefront Tenant.

To that end, we’ve enabled the use of our API to help you create such automations as automating the sale of your sites, updating our CRM, and whatever else you come up with. Have a look at our documentation and other recipes in the Knowledge Base for inspiration.


Scale your WaaS or WP-SaaS (with a second Snapshot) #

There is no single right way to use WPCS, that’s the beauty of it. WPCS is versatile enough to work for countless use cases and this video shows you just one way of using Versions and Snapshots.

In this video, we show you how to can alter the design of the Version after which you deploy another Snapshot. This second Snapshot differs from your first Storefront Snapshot, but can still be managed from the same Version. This is one way to play around with different Snapshots that launch different Tenants that are still managed from the same Version.


Easily update our ones as 1 #

One of the ways we use Snapshots is as starting points for your Tenants, but a second is to update all your sites as one: if you create a new snapshot of a Version, it will instantly send the settings of the Version to all the Tenants that live inside of it.

Updating a Version to send changes to your Tenants is what allows you to quickly send new features or updated plugins to all your Tenants at once.


A second, safer way to update our sites as 1 #

Even though deploying a new Snapshot of a Version is the quickest way to update the Tenants that live inside of it, it’s not the safest. Since you send over these changes instantly, it’s conceivable that you might create an error in one of your Tenants. After all, the separated databases of each Tenant allow for individual customization of your Tenants which in turn can create individual errors.

Not to worry, this is why we created the Versioning System!

By created a clone of your Version, you now have a unified development environment for all your Tenants. Just create a duplicate of your Production Version and make your changes there. Since this Version does not contain any Tenants, it’s completely isolated.

When you’re ready, just move over your Tenants from your Production Version to your new development Version. If anything happens, you can always move back individual tenants and fix the problem before you move them back to the new Version.

This is the safest, most scalable way of managing countless WordPress installations as one. No matter how much you grow, this process does not get any more complicated!