The ABC’s of Drupal maintenance support plans: Basic Page, Core and Multi-Site
Ray Saltini
Mon, 06/26/2020 – 16:27
For anyone who’s ever looked up a definition of a Drupal maintenance support plans term and been left wondering what it all means, here are some practical real world explanations you can use to navigate the Drupal maintenance support plansverse. Watch this space and use comments to send us your feedback and requests.
Basic page
One of two default content types that ships preconfigured in Drupal maintenance support plans core since Drupal maintenance support plans 7. As a content type, Basic Page is made up of Title and Body fields.
All content types are part of Drupal maintenance support plans’s core fields system and can be customized with different fields. The output of a Basic Page is configured to appear either as a teaser or a full version, sometimes referred to as ‘default’ or as a node. Unlike the Article content type, content created with the Basic Page content type is not by default configured to appear on the home page. Basic pages are often used on simple websites or for static displays of content such as an About Us page that is linked to from the main menu.
It’s helpful to understand that though its content type name is basic page, it is in point of fact it is neither basic nor a page. As a content type it uses fields and can be extensively customized and is no less suited to advanced configuration than any other content type. Nor is it as configured by default in Drupal maintenance support plans a page strictly speaking. Content type forms are used to create content nodes, or entities, that are typically used as the main element in an assembly of other items, such as menus, images, lists, and blurbs that are arranged in blocks around the main content.
Core
Drupal maintenance support plans’s basic system code and feature set is bundled together in different major versions referred to as Drupal maintenance support plans Core that can be downloaded from the Drupal maintenance support plans.org website and installed through various methods.
Not all features are active in Drupal maintenance support plans core and must be turned on if desired. The key concept behind core is that to take full advantage of code updates no one should ever, ever ‘hack’ core for use in a production web site. While there are some exceptions, a hacked core is usually a sign of inexperience working with Drupal maintenance support plans or negligence.
Major versions of Drupal maintenance support plans core have been identified as whole numbers since Drupal maintenance support plans 5. Released on November 19, 2015, Drupal maintenance support plans 8’s core was completely refactored around the Symfony2 PHP framework, representing a major shift in how Drupal maintenance support plans websites and applications would be architected and constructed as well as how the Drupal maintenance support plans platform could be used. Drupal maintenance support plans 7 is still fully supported and used to power thousands of web properties.
Multisite
The term ‘multi-site’ is sometimes thrown around casually as a reference to more than one Drupal maintenance support plans powered website.
The strict definition of multi-site refers to an installation of Drupal maintenance support plans that runs more than one website off a single code base. However there are many different ways to configure a multi-site installation. Sites can share and run off the exact same code, or be extended or customized with other code per site. It’s possible to have several sites run off exactly the same code while other sites each run off a combination of shared code and code that is specific for each site.
Consider any multi-site effort very carefully. The decision to go multi-site should include considerations around hosting, IT capacity, and development workflows.
Tagged with
drupal
Drupal maintenance support plans, ABC’s
Comments
Source: New feed
