The Drupal Core is used inside headless projects only.
This provides a content management system to change a websites content.
But what is headless?:
Traditional websites have their own back-end and front-end (graphical user interface). All the pieces work with the same code base and communicate directly with each other, making the website as a whole. However in a headless installation the front-end is a stand-alone piece of software, which through API communicates with a back-end. Both parts operate separately from each other, and can even be placed on separate servers, creating a minimum version of a multi-server architecture. The bridge between both parts is the API client. The endpoints of the API are connected to each other.
The biggest advantages of this technology can be found in performance optimisation and flexibility of the software stack.
public/ <-- Contains all public available files
cms/ <-- Contains the CMS
core/ <-- Contains the Drupal Core files installed by composer
modules/ <-- Contains all Drupal modules installed by composer
contrib/ <-- Contains all external/vendor Drupal modules
custom/ <-- Contains all DPDK Custom modules
project/ <-- Contains all project specific modules
profiles/ <-- Contains all Drupal profiles installed by composer
sites/ <-- Contains all Drupal site data (uploads, config)
default/ <-- Contains the Drupal default site install data
files/ <-- Contains the Drupal uploads
default.settings.php <-- Contains the Drupal default config
setting.php <-- Contains the current used config by Drupal
themes/ <-- Contains all Drupal themes installed by composer
vendor/ <-- Contains all composer modules managed by composer
autoload.php <-- Contains the Drupal Autoload code
composer.json <-- Contains the Drupal site dependencies
composer.lock <-- Autogenerated composer file containing all versions
index.php <-- Contains the Drupal Bootstap code
| Last modified | Friday, April 30, 2021, 12:00:21 PM UTC |
| Last author | Colin van Eenige |
| Commit ID | 4c7a701 |