- Issue created by @joachim
The purpose of scaffolding files is to allow Drupal sites to be fully managed by
Composer, and still allow individual asset files to be placed in arbitrary
locations. The goal of doing this is to enable a properly configured composer
template to produce a file layout that exactly matches the file layout of a
Drupal 8.7.x and earlier tarball distribution. Other file layouts will also be
possible; for example, a project layout very similar to the current
[drupal-composer/drupal-project](https://github.com/drupal-composer/drupal-scaffold)
template will also be provided. When one of these projects is used, the user
should be able to use `composer require` and `composer update` on a Drupal site
immediately after extracting the downloaded archive.
> "Other file layouts will also be possible" -- future tense? Does this date from a time when there weren't different Drupal Composer templates? At any rate, future tense shouldn't be used in docs -- docs should describe what currently exists.
> the current [drupal-composer/drupal-project](https://github.com/drupal-composer/drupal-scaffold) template
That URL points to a deprecated project, so we shouldn't be referring to it. It's certainly not 'current'!
> will also be provided
Future tense again.
> When one of these projects is used, the user should be able to use `composer require` and `composer update` on a Drupal site immediately after extracting the downloaded archive.
What are 'these projects'? Also, If this is about Composer template projects, you don't install those with a downloaded archive -- you use composer create-project.
Overall, I really don't know what this paragraph is trying to say!!!