-
-
Notifications
You must be signed in to change notification settings - Fork 28
Description
This is an epic 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 goal is to make the initial setup and post-setup support of the consumer site as easy as possible with a minimal manual update efforts. Another goal is to add more features and integrations before moving to 3.x.
The road to 2.0:
-
🟡 🛠
composer require drevops/vortex-tooling
The scripts will be published as adrevops/vortex-toolingpackage. This will allow to manage and update the custom scripts using a standardcomposer updateapproach.
The customisations of those scripts within a consumer project will still be possible by providing the same script name in thescriptsdirectory: 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-andpost-event scripts will be supported.
Also, switch vortex scripts to PHP script to make it easier to support Vortex. -
🟢
SemVerfor Vortex developement.
This will make it possible to both a) support multiple major version branches and b) versiondrevops/vortex-toolingpackage -
⚪️ 💻 DDEV and Lando for local development
-
⚪️ 🔄 More flexible CI
Consumer sites should be able to run operational tasks from CI UI. Also, some of the steps/jobs can be separated into own workflows. -
⚪️ 🔬 Environment detector
Move environments identification to use https://github.com/drevops/environment-detector -
⚪️ 🛠 More tools
-
⚪️ 🤖 AI
-
⚪️ 🪄 Better development experience
-
⚪️ 🎛️ Installer ->
vortex-cli
Installer will becomevortex-cliwhereinstallwill be one of the commands.updatewill be another one. This will provide a pathway to add more commands in the future.
Legend:
⚪️ - not started
🟡 - in progress
🟢 - done
Prioritisation takes place on 2.x project board
What will happen to 1.x version
The develop becomes main for 1.x development until 2.0 is ready. Then, main will host 2.x versions and 1.x versions will move to 1.x branch for LTS support (there will be 6 more minor versions until June 2026).
Metadata
Metadata
Assignees
Labels
Type
Projects
Status