One liner install command

Created on 12 December 2023, 7 months ago
Updated 26 June 2024, 16 days ago


Consider providing a "one liner" installation command in the "View commands" modal, in order to avoid copying and pasting twice for each module, which could be tedious when building a site from scratch.

Proposed resolution

composer require drupal/webform && drush pm:install webform

✨ Feature request





User experience

Created by

πŸ‡¦πŸ‡ΊAustralia elgandoz Canberra

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Comments & Activities

  • Issue created by @elgandoz
  • πŸ‡ΊπŸ‡ΈUnited States chrisfromredfin Portland, Maine

    Beta blocker at least insofar as we decide whether or not this is needed. I tend to like one-liners, but there's something about the education of breaking it out, too. Giving both options is of course one possibility, but curious to hear others' thoughts.

  • πŸ‡ΊπŸ‡ΈUnited States chrisfromredfin Portland, Maine
  • I narrowly prefer a one-liner for this case but agree there's value in listing the commands separately with the explanation/troubleshooting steps. Perhaps a solution is to add a "copy install commands" button to the "view commands" modal that just uses the Clipboard API to copy the one-liner command, while leaving the remaining content basically as-is.

    That way those who just want to copy-paste can do so quickly (arguably even quicker than if we just printed out the one-liner) and the added detail is there in the existing content for those who need it alongside the individual commands. I'd be happy to help with that!

  • πŸ‡¦πŸ‡ΊAustralia pameeela

    Wrote up a whole response to this but realised that it only matters in the context of the existing modal. I have added a screenshot of that to the IS.

    Short version: I think a one-liner is preferable, and there is somewhat of a precedent of using one liners in other docs β†’ . It would save most people time, and can be pretty easily unpacked if someone needed to run one step without the other.

    However, the current 'View commands' modal shows a description of each step as well as some basic troubleshooting for each. It might be tricky to merge these cleanly. Not impossible, but it would be more confusing.

    So I think it's a question of saving some time vs possibly making it harder to follow if something goes wrong.

  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    πŸ“Œ Activators should be responsible for generating project commands Fixed is related.

    That issue moves the "generate the commands to show the user" responsibility to the backend, which is much more powerful and flexible when it comes to knowing the actual state of the system. We could not only generate one-liners, we could generate customized command sets (multiple lines) that give you everything you need, start to finish -- including Drush, if you don't have it.

  • πŸ‡ΊπŸ‡ΈUnited States chrisfromredfin Portland, Maine
Production build 0.69.0 2024