In this scenario, we have basically the exact same configuration on all the sites and the only variation is content. In this scenario, each site has its own disparate config and may not have a true config strategy at all. This is a good thing. You want to get that updated, tested, and deployed ASAP. They make a change that is fine on this one site over here, but they deploy it and suddenly one of those other sites over there has a problem. You fix that problem and get that site working, and yet another site starts to experience a problem.
What does that look like? Try to deploy the same basic features to all your sites — this means the same content types, blocks, views, etc. Build a base profile and base theme that has most of your standard capabilities — this means that all sites essentially have the same baseline capabilities to begin. Adding an entirely different content type or drastically changing a content type opens the possibility for hardships.
I talk in more detail about configuration management strategies in another post. Challenges aside, multisite is a really compelling model for many organizations. My strong recommendation is to start as far back from the technology as possible. Pull together stakeholders from your organization and do a discovery to determine what features you will need on the platform.
Work with your design team to establish component based design principles for your organization this means instead of building a bunch of one off content types for your landing pages, build a generic landing page and a bunch of custom block types to let your content team build up those pages.
Once you have some of the basics in place, then you can start figuring out your configuration management and development strategy. Remember, multisite may be a great fit for your organization but not all of your sites! I recently had a customer tell me that they wanted to put an internally facing product development website full of unreleased intellectual property on the same multisite platform as their public facing customer sites.
I mean, can you do that? Will Drupal work in that situation? Of course it will! BUT remember if you have drastically different config and audiences, the platform is that much harder to maintain, test, deploy, etc. So here I would suggest a multisite platform for the public facing part of the company and a different application for the internally facing one. Which itself could be a multisite platform if there are multiple sites needed for the intranet.
I recently tested updating to Drupal 9. Here is the the rundown! Acquia has announced the official end of life for its Lightning distribution. Time to start thinking about the skills you want to focus on this year.
Given that, the Total Cost of Ownership TCO of maintaining an online marketing presence and communication tools goes up to the whole other level. In such scenarios, keeping up a single CMS to ensure its security and maintenance is advantageous. Managing a database of every single site that has been created say 11 without the multisite feature can prove to be an exhausting task. The centralized database enables users to share content, tools, and site features across all sites while simultaneously being able to change the appearance of each site.
Besides, a single database is easier to manage, upgrade, and makes the perfect solution if all sites serve a similar function. While the benfits are significant, it is advisable to be aware to some common risks that come up with the Drupal multisite solution. In case you have multiple sites serving different purposes and functions, and have very little in common, Drupal multisite is not the best solution. The Domain Access module would not be functional here are each site database will need to be main tained separately.
In such cases, multisite might actually become unweildy to handle, and it best avoided. While Drupal multisite makes it easy to maintain the codebase, it can does have a trade-off with your ability to deploy innovative website experiences. Rolling out replicas or closely similar sites using Drupal multisite is fast because of the shared set of modules in use. However, microsites for marketing campaigns or other interactive sites need a range of custome modules and creating those within the multisite set up could generate complexities.
So it is advisable to keep such sites outside the Drupal multisite setup and manage independently. The dependence on a single codebase to operate multiple sites can be a problem in case of a flaw in the codebase. If your Drupal platform is not regularly kept up-to-date, you run the risk of having all you sites go down at once due to a security vulnerability or other major bugs.
As with every tech solution, Drupal multisite has its pros and cons. However, understanding how your current IT infrastructure is set up, and estimating your future requirements, would be the first step in figuring out if Drupal multisite will meet your requirements without running into the challenges.
At Srijan, our teams can help connect and consult with you to help you through this process. And then step into designing an effective multisite architecture that works for you. We have worked with several global enterprises to deliver multisite architecture with the Drupal multisite solution. We understand the business and technological nuances involved in a large-scale multisite setup and have the expertise to help you successfully navigate the discovery, development and deployment phases of the project.
Looking to consolidate your digital presence with a multisite architecture? How We do. Drupal modules are of 3 types: those that are included in the core core modules , downloadable from Drupal.
Drupal has an awesomely flexible system of user roles and permissions, as well as opportunities for fine-grained user access. These are the keystones of Drupal security, smooth user experiences, Categories Drupal Development. Drupal 8. Web Design. Project Management. Drupal multisite: how it works and when it is the best choice. Author: Nadine. What is Drupal multisite? In the multisite setup, different Drupal sites share: Drupal core codebase available modules available themes At the same time, they do not share: base domains or URLs databases enabled modules enabled themes configurations files user profiles content Here is an example of Drupal multisite feature created by our company for a global retail chain of goods for homes.
Drupal multisite benefits For some companies, a strong multisite feature is one of the reasons they have chosen Drupal at all. Another benefit of Drupal multisite is the presence of useful solutions and tools.
Drupal multisite risks In some cases, Drupal multisite can present risks — the "flip side" of its benefits. When Drupal multisite is the best choice As usual with benefits and risks, they are relative, and depend on the situation.
Multisite is the most successful if sites in the collection are the responsibility of the same development and Drupal support team. And, remember, it should be a careful and experienced one. Read also 1. Top Drupal e-commerce distributions to quickly create an online store.
0コメント