EPIC: Vortex 2.0

[AlexSkrypnyk]

This is an epic placeholder for Vortex 2.0. Used to reference from other issues and capture a roadmap.

---

Overview

Vortex 2.0 will be a major refactor of the distribution, customisation and composability.

The main idea is to make the initial setup and post-setup support of the consumer site as easy as possible with a minimal manual update efforts. To achieve this, the following changes would need to be implemented:

1. 💥 composer create-project
   The Vortex repository will need to be distributed as a package through Packagist to allow this.

2. 🔄 composer update drevops/vortex
   We will rely on Drupal's own Drupal Core Scaffold plugin to distribute updates for some of the Vortex's files.
   This mechanism uses a package that every composer-managed Drupal site already has.
   We have 1 blocker to resolve.

3. 🛠 composer require drevops/vortex-tooling
   The scripts will be moved to Vortex Tooling (drevops/vortex-tooling) repository and will be included into Vortex as a package. This will allow to manage and update the custom scripts using a standard composer update approach.
   The customisations of those scripts within a consumer project will still be possible by providing the same script name in the scripts/custom directory: the original script will look in that directory and, if it finds the script with the identical name, it will use that script.
   But in majority cases, pre- and post- event scripts will be supported.

4. 💅 composer require-dev alexskrypnyk/customizer
   A Customizer package will replace the Vortex Installer drevops/vortex-installer and will integrate with Drupal Core Scaffold plugin's events. This means that it will be possible to run the Customiser on project-create and provide details about your project interactively. It will also allow to develop and test the Customiser as a standard Consumer package rather than a distributable PHAR.

5. 📖 The documentation system will be reworked and will be describing architecture, tooling and workflows on how to work with Vortex. The documentation will become a go-to place for all Drupal developers using Vortex.

6. 🔬 The workflow testing framework, used to test all parts of the Vortex (functional tests), will change from BATS to PHPUnit. This will allow to write tests faster and will allow easier contributions.
   We will still use BATS for unit testing of shell scripts in drevops/vortex-tooling.

7. 🤖 The CI configuration will be simplified and optimised to allow running some of the actions in parallel.

---

Implementation order

• Use drupal/core-composer-scaffold to manage project creation and updates #1042
• Move scripts to drevops/vortex-tooling package. #1192
• Add support for pre- and post- hooks in scripts  #1198
• EPIC: uplift current documentation #951
• CI - separate build and test stages #782

Beyond 2.0

After 2.0, there will be more work done towards adding new features - these all are ready on the project board.