The WordPress Multisite — what I call Monster Sites — is an often misunderstood creature.There is plenty of documented reasons why you should never use it, and beyond the knowledge of how to install and administer a Monster Site, there is little understanding of what it should and should not be used for.<\/p>\n
Often, it is only when a developer ventures into using a Monster Site installation do they find out just why “monster” is an appropriate label. Without proper planning or preparation for its use, a multisite installation can be a disaster waiting to happen.<\/p>\n
But what if you could prevent a multisite from becoming a monster by knowing why certain configurations work better than others? This is why I would like to approach WordPress Multisite from a strategic point-of-view by illustrating potential strategies, industries those strategies could serve, and some lessons learned in experimenting with some of these strategies.<\/p>\n
Additionally, I would like to describe these approaches without the interference of heavy, technical details in anticipation of a broad audience. My hope is that I can help start a new conversation regarding a more strategic use of WordPress Multisite and tame Monster Sites once and for all!<\/p>\n","protected":false},"excerpt":{"rendered":"
The WordPress Multisite — what I call Monster Sites — is an often misunderstood creature.There is plenty of documented reasons why you should never use it, and beyond the knowledge of how to install and administer a Monster Site, there is little understanding of what it should and should not be used for. Often, it … Continue reading Monsters of WordPress<\/span>