Online presence often forces companies to build multiple websites: a website for each brand, product or a website for each country. Maintaining tens or hundreds of websites can quickly turn into a time consuming costly effort.
Luckily Drupal is here to help. Multisite functionality is built into Drupal.
Drupal multisite would provide you the opportunity to create multiple websites using the same codebase, however, all the sites would be different from one another, serving different audiences.
The cost of managing the multisite platform is substantially lower than that of managing hundreds of separate websites.
In Drupal we have several ways to accomplish multisite functionality. In this case study some architectures that make this possible will be described. Read on to identify which option is best tailored for your needs.
Websites share code (the Drupal core, modules, and themes), but each website has its own database so they do not share content, configuration, or settings. Each website can also have some extra modules / themes under its own subdirectory in the same codebase. A multisite is accomplished by forming different folders for various websites in the /sites/ folder of the Drupal system. For example:
We can control which website can use which modules and themes, by putting them into correct folders accessible only for specific sites.
Classic Drupal Multisite would be most beneficial if all of the sites have the same features and are using similar modules and settings but different content and users.
A company maintains many brands. Each brand requires a website. Websites are visually different (each brand has its guidelines), but functional requirements are mostly the same (banners, videos, sliders, contact forms, etc.) The same development team maintains and develops all sites. But each site may have its own marketing or content team which manages content for the site.
This architecture consists of a single codebase and single database/installation. The Domain Access suite of modules provide functionality that allows serving multiple sites (domains) from this setup. It also allows you to categorise your content as shared and unique, you can decide a specific piece of content for one particular domain, then you can also share it across all sites, if that is what you want.
Multi-Domain setup makes sense if sites will share content and/or users, and if all of the sites will have the same functionality, content types/data structures but might have some slight visual changes.
E-commerce site with one product catalog, single checkout and common users but separate domains for different product categories.
Multi-Locale allows for using language-based regional targeting. Utilizing the power of multilingual capabilities for multiregional targeting. This is recommended for sites targeting multiple regions.
Using the Drupal multilingual system you can translate any piece of content to different languages. The admin interface has built-in translations for 94 languages. Domain name may be used to determine the language. Specifying "example.com" as language domain for English and "example.de" as language domain for German will result that only content in the respective language will be shown for each domain.
Multi-Locale Architecture would be useful if you want to show content to your site visitors in their native language. Multilingual sites can dynamically show translated content to their visitors based on customisable factors like browser language.
Corporate website for small and medium businesses with clients from different countries.
Drupal distribution is a mix of everything you would need to start your web projects, from the required modules and libraries to custom themes and modules and from the configuration to possibly the default content. It’s a website starter pack.
A Drupal distribution focusses on a certain business and adds features specific to them into one installation so it takes lesser time to configure the most certain elements of a Drupal website.
For example, if you’re looking to build Drupal websites for hospital management, your Drupal developers can pre-configure modules for patient registrations, investigations, pharmacy management etc. and also configure roles for admins, doctors, patients, nurses, etc. So now when you want to deploy the same or similar Drupal solution for a different hospital, the work is much lesser and can be done faster.
A distribution profile works well if the sites are all starting out the same, but they are expected to grow in different directions. Maintenance work is expected to be independent for each of the sites.
A multinational corporation maintains many brands or services. Each brand (service) requires a website in a separate country or region. Websites are visually different (each brand has its guidelines), the languages vary per country, but functional requirements are mostly the same (banners, videos, sliders, news, articles, contact forms, user registration and personal account, etc.) Each country has its own development and marketing or content team which manages codebase and content for the country site.
If you're looking to create a custom web service that meets your company's unique needs, contact Attico today. Our team has the expertise to develop a solution that meets your requirements and delivers results.
How Our Experts Helped Baby&Me Achieve Optimal Results in Migrating 45 Websites Worldwide with New Features and Efficient Transition to Further Support And…
Attico International collaborated with Bonamark to develop a payment module to integrate Stripe with Drupal, the popular CMS. The client needed the payment…