Problem/Motivation
The new CLI entry point currently under development in #3453474 uses drupal as the command name (i.e. vendor/bin/drupal).
While this name is straightforward and aligns with the project name, there are concerns about using drupal directly as a CLI command. These include potential ambiguity, searchability, conflicts, and long-term maintainability of the developer experience.
Personally, I prefer drupal, with example usage such as:
$ vendor/bin/drupal cr
$ vendor/bin/drupal upddHowever, given the importance of this decision and its long-term impact, it is worth discussing whether this is the best choice, or if an alternative name should be selected.
Steps to reproduce
N/A
Proposed resolution
Open a discussion to:
- Confirm
vendor/bin/drupalas the final CLI command name, or - Select a new, community-approved name for the CLI tool
The goal is to reach consensus before the CLI becomes widely adopted.
Remaining tasks
- Continue development in #3453474 (CLI entry point in Drupal Core)
- Gather community feedback on naming
- Confirm and document the final CLI command name
User interface changes
N/A
Introduced terminology
CLI command name (e.g. drupal or alternative)
API changes
None
Data model changes
None
Release notes snippet
To do.
Comments
Comment #2
xmacinfoEven though I prefer
drupal, here are two suggestions:1. dmin (contraction of Drupal admin) |
dmin cr1. din (contraction of Drupal admin) |
din crComment #3
amateescu commentedHow about
drush? It has a nice ring to it :)dropwould also be a nice touch.Comment #4
mradcliffeThank you for creating the follow-up.
I reparented this under the meta: #3582246: [meta] CLI in Core community initiative for tracking.
For those who search for drush commands, applying recipes, and quickstart today, what are the common search terms that are used? Is this something that we can get from the drupal.org infrastructure team?