Use relative paths for Quickstart `cd ...` step

Created on 2 September 2024, 4 months ago
Updated 19 September 2024, 4 months ago

Problem/Motivation

This applies to all versions, from what I can see.

The Quickstart documentation step cd /path/to/SUBTHEME_NAME should use a relative path in most cases.

There's a similar error in the GitBook docs: cd /web/themes/custom/SUBTHEME_NAME

Proposed resolution

Change the values to relative paths:

  • cd path/to/SUBTHEME_NAME
  • cd web/themes/custom/SUBTHEME_NAME
πŸ› Bug report
Status

Closed: works as designed

Version

6.0

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States kentr

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

Comments & Activities

  • Issue created by @kentr
  • Status changed to Closed: works as designed 4 months ago
  • I'd say the /web/themes/custom/ is the default custom path that people get when they setup a new Drupal website and it is good for new comers to know where things are

    marking this as closed for now
    Thanks

  • πŸ‡ΊπŸ‡ΈUnited States kentr

    @doxigo, I think there was a misunderstanding.

    To your point:

    I'd say the /web/themes/custom/ is the default custom path that people get when they setup a new Drupal website and it is good for new comers to know where things are

    I disagree with that.

    The concern I had is the forward slash at the beginning of the path that makes it an absolute filesystem path. I highlighted the slash with the caret below:

    cd /web/themes/custom/SUBTHEME_NAME
       ^
    

    I'd say that in most cases when people create a Drupal project it will not be at the root of their file system. So cd /web/themes/custom/SUBTHEME_NAME will fail.

    Instead in those cases, what people would want is to go to web/themes/custom/SUBTHEME_NAME (without a forward slash at the beginning), because that's relative to the directory that they're currently in.

  • Must've missed your point regarding the first forwarding slash, thanks. fixed

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024