I have noticed that the Composer-Ready Project Templates documentation inserts the -n (--no-interaction) parameter between composer and create-project.
Now, if someone searches for "composer create-project" as a string (site:drupal.org "composer create-project") they will get some hits on drupal.org, whereas if they search for site:drupal.org "composer -n create-project" they would get hits for some other pages.
It also looks like "composer -n create-project" as a string is used fairly rarely anywhere:
https://www.google.com/search?q=%22composer+create-project%22 (133.000 results)
https://www.google.com/search?q=%22composer+-n+create-project%22 (86 results)
Is it worth considering streamlining parameters to accommodate discoverability? I suggest that they be put at the end of the line, since I also think it is more reader-friendly to have the "action" commands (composer + create-project) stand side-by-side, uninterrupted by parameters like -n and -s dev, for an uninterrupted syntax like this:
tool > command > what > where + parameters
Currently
composer -n create-project drupal/recommended-project my-project
Better?
composer create-project drupal/recommended-project my-project -n
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Back in the day, the -n parameter was needed, which is mostly what this issue is about. But it is no longer needed, so I think this issue can be closed.
Automatically closed - issue fixed for 2 weeks with no activity.