[meta] Replace Drupal in UI text with the name of the distribution

Created on 26 November 2013, almost 11 years ago
Updated 18 January 2023, almost 2 years ago

Problem/Motivation

Inspired by πŸ“Œ No "Drupal" in UI text -- config_translation, content_translation, locale, language, and translation server parts of installer Closed: duplicate .

Drupal has a deal with distributions, that they can replace Drupal with their own Distribution name. Also we have a UI text standard
https://www.drupal.org/docs/develop/user-interface-standards/interface-t... β†’
that says:

Use "Site"β€”not "Drupal". Referring to Drupal by name complicates distributions, and users may not know the site is running on Drupal.

You can also use terms like "the core software".

But Drupal still appears in the UI. Here are some examples:

core/includes/install.core.inc:  drupal_set_title(t('Drupal already installed'));
core/includes/install.core.inc:      'description' => t('The installer requires that you create a translations directory as part of the installation process. Create the directory %translations_directory . More details about installing Drupal are available in <a href="@install_txt">INSTALL.txt</a>.', array('%translations_directory' => $translations_directory, '@install_txt' => base_path() . 'core/INSTALL.txt')),
core/includes/install.core.inc:        'description' => t('The @drupal installer requires that you create a settings file as part of the installation process. Copy the %default_file file to %file. More details about installing Drupal are available in <a href="@install_txt">INSTALL.txt</a>.', array('@drupal' => drupal_install_profile_distribution_name(), '%file' => $file, '%default_file' => $default_settings_file, '@install_txt' => base_path() . 'core/INSTALL.txt')),

That last one is interesting, because the first spot says @drupal and replaces it with the distribution name, but later in the same string it uses the word Drupal specifically.

You can find other usage by using a grep command looking for "Drupal" inside of quotes. Here's a grep command that yields some false positives, but should find most/all of what we're looking for:

egrep -i -e "'[^']*[^/\]drupal[^/\]" -e '"[^"]*[^/\]drupal[^/\]' `find . \( -type d -name tests \) -prune -o -type f -print` | grep -i --color drupal

Proposed resolution

Replace Drupal in UI text with the distribution name, or phrases like "the site" and "the core software".

Remaining tasks

Make an issue for each group of modules/themes in the following list, and complete the issues.

Novice task:

  1. Find a module group in the list that doesn't have an issue yet.
  2. Click "Add child issue" in the sidebar of this issue to create a child issue.
  3. Fill in the issue fields:
    • Title: No "Drupal" in UI text -- _________
      (Replace ___________________ with the group of modules/themes you are working on)
    • Category: Task
    • Version: 9.2.x-dev (or the current latest 9.x development version)
    • Component: one of the modules from the list in the group you are creating the issue for
    • Issue tags: Novice
    • Issue summary -- Replace the default summary with this:
      <h3 id="summary-problem-motivation">Problem/Motivation</h3>
      
      This is a child issue of [
                  
                    
                    
                    πŸ“Œ
                    [meta] Replace Drupal in UI text with the name of the distribution
                      Active
                    
                  ], for the following modules/components: ______________________________________________.
      
      Drupal has a deal with distributions, that they can replace Drupal with their own Distribution name. Also we have a UI text standard
      https://www.drupal.org/docs/develop/user-interface-standards/interface-text#interface-text-wording
      that says:
      <blockquote>
      Use "Site"β€”not "Drupal". Referring to Drupal by name complicates distributions, and users may not know the site is running on Drupal.
      </blockquote>
      You can also use terms like "the core software".
      
      But Drupal still appears in the UI.
      
      <h3 id="summary-proposed-resolution">Proposed resolution</h3>
      
      Replace Drupal in UI text with the distribution name, or phrases like "the site" and "the core software".
      
      <h3 id="summary-remaining-tasks">Remaining tasks</h3>
      <ol>
      <li><strong>Novice task</strong> -- Locate the word "Drupal" appearing in UI text in this group of modules/themes. Here's a grep command that yields some false positives, but should find most/all of what we're looking for:
      
      egrep -i -e "'[^']*[^/\]drupal[^/\]" -e '"[^"]*[^/\]drupal[^/\]' `find . \( -type d -name tests \) -prune -o -type f -print` | grep -i --color drupal
      </li>
      <li><strong>Novice task</strong> -- Replace each occurrence either with "the core software", "the site", or the distribution name. There is a function that will return the distribution name: drupal_install_profile_distribution_name().</li>
      <li><strong>Novice task</strong> -- Make and upload a patch file, or use an issue fork / merge request workflow.</li>
      </ol>
      
      <h3 id="summary-ui-changes">User interface changes</h3>
      We will not use the word Drupal in the UI, but instead either show the distribution name or the phrases "the site" or "the core software".
      
      <h3 id="summary-api-changes">API changes</h3>
      None.
      
      <h3 id="summary-data-model-changes">Data model changes</h3>
      None.
      
      <h3 id="summary-release-notes">Release notes snippet</h3>
      Not necessary.
      
    • In the beginning of the issue summary, replace _____________________ with the group of modules/themes for this issue.
  4. Save the issue
  5. Edit the issue summary of this issue to include a link to your new child issue. To make a link to an issue, use a syntax like
    [#1234567]
    

    replacing the number with the issue number you just created.

  6. Add a comment to this issue saying you made a child issue and save.

Issues that need to be made or completed

  • action
  • admin UI-related modules: contextual, help, inline_form_errors, quickedit, settings_tray, shortcut, toolbar, tour
  • aggregator
  • appearance-related modules: breakpoint, color, layout_builder, layout_discovery
  • comment, node, path, taxonomy
  • block, block_content
  • book
  • ckeditor, editor, filter
  • config
  • contact
  • content_moderation, workflows
  • field-related modules: datetime, datetime_range, field, field_ui, link, options, telephone, text
  • forum
  • history, statistics, tracker
  • internationalization modules: config_translation, content_translation, locale, language, and translation server parts of installer πŸ“Œ No "Drupal" in UI text -- config_translation, content_translation, locale, language, and translation server parts of installer Closed: duplicate
  • media-related: file, image, media, media_library, responsive_image
  • menu_link_content, menu_ui
  • migrate, migrate_drupal, migrate_drupal_ui πŸ“Œ No "Drupal" in UI text -- migrate, migrate_drupal, migrate_drupal_ui Closed: duplicate
  • search
  • services-related modules: basic_auth, hal, jsonapi, rdf, rest, serialization
  • system-related modules: automated_cron, ban, dblog, syslog, system, update, and user
  • speed-related modules: big_pipe, dynamic_page_cache, page_cache
  • views, views_ui πŸ“Œ No "Drupal" in UI text -- views, views_ui Closed: duplicate
  • core themes

Already done

User interface changes

We will not use the word Drupal in the UI, but instead either show the distribution name or the phrases "the site" or "the core software".

API changes

None.

πŸ“Œ Task
Status

Active

Version

10.1 ✨

Component
BaseΒ  β†’

Last updated about 11 hours ago

Created by

πŸ‡ΊπŸ‡ΈUnited States yesct

Live updates comments and jobs are added and updated live.
  • Needs product manager review

    It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

No activities found.

Production build 0.71.5 2024