Add information about new desktop app to documentation

Created on 14 April 2025, 6 days ago

Problem/Motivation

We should update the content of this page https://new.drupal.org/docs/drupal-cms/get-started/install-drupal-cms, and potentially other places, with information about the new launcher. https://new.drupal.org/drupal-cms/launcher.

I'm not sure we need a whole page on downloading and using the launcher, since hopefully that's something people can figure out. Though, maybe we do need a page that includes information about the fact that you can resume and it'll launch your site where you left off last time. And how to cleanup/remove the site when you're done. Actually yeah ... that's probably a good idea.

The draft version of this content of https://new.drupal.org/docs/drupal-cms/get-started/install-drupal-cms currently lives here: https://docs.google.com/document/d/12--ffE924hCqGhf8aB3twH8wAmMgCHU4JQ37...

πŸ“Œ Task
Status

Active

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @eojthebrave
  • πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN

    Add a link to the draft content for the new page, and assigning to Amber to review and copy edit.

    One thing that drafting this content makes me aware of is the fact that the cms launcher (because it uses sqlLite) doesn't have any easy way to move to a hosting provider (since they'll likely use MariaDB/MySQL). Which is something we might want to consider in the future. I've called this out in the draft content because I think it's an important distinction between choosing the launcher versus DDEV for people who are unsure which one they should use.

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

    To be clear on this, the launcher vs. DDEV is not an apples-to-apples choice. The launcher is not really a proper development environment, since there's no easy way to port the database from one environment to another (at least, not without some hacking). Maybe at some point the launcher will be a reasonable way to start a site, but for now it's really best suited for trialing Drupal CMS.

  • πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN

    +1. We need to make sure that distinction is clear in the docs so that someone who is trying to figure out which of the different installation experiences (in browser, cms launcher, or ddev) to use makes an informed decision and not one that is going to back them into a corner and frustrate them.

  • πŸ‡ΊπŸ‡ΈUnited States Amber Himes Matz Portland, OR USA

    I'm editing the launcher doc to frame it as a more extensive trial, replacing words like "Install" with "Try" or "Explore" in the title and in the steps. If/when the doc is placed in the "Get started" section, the title, "Try out Drupal CMS using the desktop app" contrasted with "Install Drupal CMS locally with DDEV" will hopefully make it clear what the different purposes are. Also, the intros to both tutorials reiterate the options (install locally with DDEV, try in a browser, try with the desktop app). And the intro text for the section, "Install Drupal CMS", will be edited to outline each of the options and their purpose. In my opinion, with these edits, the doc for the launcher app can be placed in the "Get started" section.

    I've completed editing the launcher doc both for clarity and for grammar and punctuation.

    I've also edited the changes to the section doc, "Install Drupal CMS" to make it more clear that using the launcher is another way to try out Drupal CMS more extensively.

    Also, I've edited the issue summary to add remaining tasks.

Production build 0.71.5 2024