Part 3: Can WordPress Multisite Help You?

In the previous two parts, we introduced you to new concepts in WordPress Multisite that a single site installation does not have. In this final part, we will guide you toward an understanding of when using WordPress Multisite is the best option, and help you determine if it is the right fit for your organization.

So far, I have provided a lot of information on what WordPress Multisite is and the benefits it contains, but what about the practical application of it? You came here wondering if WordPress Multisite might be the solution for you. This section will outline key things to consider when deciding whether or not to use WordPress Multisite.

When You Should Use WordPress Multisite

There are some instances when it makes perfect sense to use WordPress Multisite. Multisite typically works best when the sites on the network all run along a similar theme or have a limited differential in terms of required functionality. Let’s take a look at a few prime candidates.

Multilingual Network

If your site needs to be translated into additional languages, using WordPress Multisite can quickly get you there. The theme and plugins will likely be the same across all sites with only content differences. Each language would be its own subsite that could be configured with access only for the translators who need to be able to touch the content. This is a strategy we utilize here at WebDevStudios (WDS) with a subdirectory install that winds up looking like:

• English – http://acmecorp.com/en
• Spanish – http://acmecorp.com/es
• French – http://acmecorp.com/fr

Blog Network

WordPress can be a high-performance blogging engine. If your use case is to put together a group of basic blogs, WordPress Multisite in the answer. WordPress.com is a prime example of a blog network. Users have a limited set of functionality available to them and several different themes they can choose from. The variety in look and feel of sites hosted by WordPress.com is impressive.

While we are on the topic of WordPress.com’s service, I want to mention some of its staggering statistics. 

• 21.7 BILLION page views per month
• 79.2 million new blog posts each month
• ~74 million sites hosted (this number is questionable as the full number is not released)

Wow! That is a huge amount of data and traffic for one WordPress installation, and guess what? Nobody has ever reached the limit of Multisite’s capabilities. As long as you have the hardware to support it, there is theoretically no limit to the number of sites you can host on a WordPress Multisite install. WordPress.com proves that.

Multi-Department Corporate Sites

Earlier, I shared a multi-department Acme Corp example. It is a common scenario we see at WDS, wherein companies desire to have departmental websites in which each department controls its own content and has some limited ability to manage the look and feel from a common style guide.

One such client we worked with tapped WordPress Multisite for their intranet. It was not even a public facing site! It was one of the more creative uses I have come across and included:

• A couple dozen departmental sites
• Centralized file management for forms, memos, etc.
• HR/personnel management
• Employees’ corner
• Monthly corporate newsletter
• Classified similar to Craigslist
• Employee blogs

When You Should NOT Use WordPress Multisite

As awesome as WordPress Multisite is, there are also times when it does not make sense to use. Take a look at these examples.

Each Site Needs Significant Custom Development Work and/or Plugins

When you have a group of sites, even within the same organization, that need a significant amount of custom development work, WordPress Multisite may not be a good idea. One tiny mistake in the code for another site can have implications across the entire network—possibly crashing it.

Even when the “significant custom development” is nothing more than installing a bunch of plugins, WordPress Multisite can cause issues. Some plugins alter network operations in ways that only a super admin should be altering. Ideally, the network will have a well-defined purpose that limits the amount of customizations to functionality that will be needed per site.

A great example of this scenario is my own personal site https://ben.lobaugh.net. Being a developer, I have the ability to go in and tweak the code on my site as often as needed. I know that I can bring down the site if I screw up, but it will not affect anyone else. I am also not worried about ensuring the code I write is safe for a Multisite environment.

Each Site Needs Its Own IP Address

WordPress Multisite aims to make running a network of sites as simple and painless as possible. When you have a network of sites that all need their own IP addresses, a lot of complexity is introduced. It is absolutely possible to make it work, but it will require significant time investment in development operations to configure the servers properly. For a small network with a few sites, this may not be a big deal; but when you get into dozens and thousands of sites, it is simply not feasible.

Ecommerce

Ecommerce is a sticky wicket with WordPress. In recent years, ecommerce support on WordPress has improved dramatically for single site installs; however, Multisite ecommerce support has largely been neglected. This is in part due to the overhead needed to run a proper ecommerce site. There are additional database tables, relationships, and processing power needed to run an ecommerce site, in addition to things such as payment systems and SSL certificate requirements. Though it is possible to run WordPress Multisite in this manner, it requires a significant investment in time and architectural knowledge that usually makes it more time and cost-effective to use multiple separate WordPress single site installations.

You made it!

Congratulations on getting through all three parts in this series on WordPress Multisite. Multisite is a powerful tool that I hope you will be able to utilize. WDS loves WordPress Multisite, and we are always interested to see how others are using it. We would love it if you dropped us a line in the comments. If you would like to chat about your implementation or work with us on your project, head over to the contact page.

Looking forward to hearing about your projects!

Photo by rawpixel.com on Unsplash

The post What Is WordPress Multisite and How Can It Help You? (Part 3) appeared first on WebDevStudios.

Introduction to WordPress Multisite

There is a good deal of information on the web about WordPress Multisite, but most of it dives too deep technically, or quickly shows you steps to set up a Multisite environment. I am going to tackle it from another angle, from the point of view of an outsider looking in (with possibly no technical background) wondering if WordPress Multisite will fit the needs of their organization. To help facilitate the discussion, let’s start with some terminology.

New Terminology

WordPress Multisite introduces new ideas into WordPress, and there are several new terms that come along with it. Below are the various Multisite terminologies defined to help provide a foundation in communication for the rest of the article.

• Network: The Network refers to a group of sites created on your Multisite instance. Though it is technically possible to run multiple networks on a single Multisite instance, we will focus on the basic single network that comes with Multisite. To keep things simple, you should be aware that some older literature referred to a Network as a Site.

• Site: A site refers to a single site within a network. These are sometimes also referred to as subsites, or blogs. Over the years, the term site has changed meaning to refer to the individual sites on a network. You may see reference in older literature that use the term site in the context of network.

• Blog: Another name for a single site on the network.

• Subsite: Another name for a single site on the network.

• Network Admin: This is a new section of the wp-admin area that appears in the Admin Bar after enabling Multisite on your WordPress installation. The Network Admin is where you will control the sites, plugins, and themes available to your sites.

• Super Admin: Super Admin is a new role that is available specifically for Multisites. Users with Super Admin access are allowed to access the Network Admin area and manage the entire network. Super Admins can access the dashboards of any site and administer them as well. The traditional Administrator account only has access to the sites it has permissions on.

• Subdomain Install: Network setup option that creates new sites with a subdomain of the primary domain. For example:
  • Primary domain: example.com
  • Site for Bob: bob.example.com
  • Site for Sally: sally.example.com 

• Subdirectory Install: Network setup option that creates new sites with a subdomain of the primary site. Useful when creating sites that all need the same look and feel such as corporate or language sites. For example:
  • Primary domain: example.com
  • Site for Bob: example.com/bob
  • Site for Sally: example.com/sally

What is WordPress Multisite?

You are undoubtedly familiar with WordPress. A content management system you install to manage your website content. Perhaps you have multiple websites, each with their own installation of WordPress running the site. Enter WordPress Multisite; WordPress Multisite transforms a single site into a powerhouse that can run an unlimited number (nobody has found a max number yet!) of websites from a single WordPress installation. In essence, it could combine all the individual WordPress installations you run into one single installation that supports all the sites. Each site can have its own domain, theme, and set of plugins utilized.

As an example of how I use the power of WordPress Multisite, I have several family members who have basic blogs set up to post their random thoughts. There are also several organizations that I have helped support over the years and test beds for new corporate sites running. Each of the site owners are able to manage their own content, while I ensure the network stays up and running efficiently with WordPress, and that all plugins are kept up to date.

Feel free to take a peek at a couple sites on my network:

• http://raeann.lobaugh.us/ – Sister’s site
• http://cara.lobaugh.us/ – Aunt’s site
• http://lewiscountychaplaincy.org/ – Website for the Lewis County Chaplaincy agency
• http://lobaughwedding.com – Site for Lobaugh weddings, currently featuring my wedding
• http://fetchfitness.clients.lobaugh.us/ – In-progress site for a friend’s business

You will notice there are subdomains and custom domains. WordPress handles both with elegance. By default, new sites on my network are created as subdomains of lobaugh.us and then a custom domain is applied when ready. Subdirectories are also supported. Subdirectories make it look like all the sites are part of the same domain. For example, in my network, my sister’s site could be http://lobaugh.us/raeann. There are good reasons to run WordPress Multisite in subdomain mode that I will get into in Part 3.

In Part 1, you were introduced to new terminology used by WordPress Multisite and provided a high level view of what WordPress Multisite is. In the following parts, we will cover why using WordPress Multisite matters, and how to determine if it could be the right tool for your organization.

The post What Is WordPress Multisite and How Can It Help You? (Part 1) appeared first on WebDevStudios.