Update labels/verbiage to Drupal 10 throughout interface

Created on 9 February 2024, 14 days ago
Updated 16 February 2024, 7 days ago

Problem/Motivation

There are a number of places throughout the AM:A ui where the "Drupal 9" verbiage shows up. Now that we are able to run AM:A on Drupal 10 we should be able to update these!

Steps to reproduce

Go to the AM:A Modules overview page /acquia-migrate-accelerate/modules for a quick example:

Proposed resolution

Change these to "modern Drupal"

Remaining tasks

Go through UI and update any references from Drupal 9 to "modern Drupal" πŸ˜„

User interface changes

Any user-facing mentions of a Drupal version should be updated to "modern Drupal"

API changes

n/a

Data model changes

n/a

πŸ“Œ Task
Status

Fixed

Version

1.9

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

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

    Affects the content, performance, or handling of Javascript.

Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @dan612
  • πŸ‡§πŸ‡ͺBelgium Wim Leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Whoops! πŸ˜…

    Ideally we wouldn't tie it to any Drupal version. Because:

    • people still use AM:A with Drupal 9
    • Drupal 11 is due to be released later this year

    How about instead? πŸ˜„

  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

    Updated the IS as per #2 πŸ“Œ Update labels/verbiage to Drupal 10 throughout interface Active - for future proofing.

    I think these alterations will require a ui rebuild as we need to compile the changes into ui/dist/common.bundle.js. I tried doing this locally but was hitting some issues with node versions. I think i was able to get npm run build to work on Node 18 (whereas node 20 was failing) - but need to run through it again to be sure 😁

  • Assigned to dan612
  • Status changed to Needs work 11 days ago
  • πŸ‡§πŸ‡ͺBelgium Wim Leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Yes, you'll need node 16 or 18 β€” quoting package.json:

      "engines": {
        "node": "^16 || ^18"
      },
    
  • Pipeline finished with Failed
    10 days ago
    Total: 756s
    #93383
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

    Leave it to me to not read instructions πŸ˜†

    There were a few places where "modern Drupal" didn't fit...it read awkwardly. I tried to update things within context to what seemed fit πŸ˜€

    Couple screenshots of the changed ui:

  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

    Pipelines is quite angry with me but im not sure if that much noise is normal or not 😬

  • Status changed to Needs review 10 days ago
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • Issue was unassigned.
  • Status changed to RTBC 7 days ago
  • πŸ‡§πŸ‡ͺBelgium Wim Leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Pipelines is quite angry with me but im not sure if that much noise is normal or not 😬

    There's some contrib test failures, but they cannot be related to this. These are upstream regressions. They're happening against 1.9.x HEAD too.

    I'll try to get those fixed next week.

    This looks great! πŸ‘

  • Pipeline finished with Skipped
    7 days ago
    #96618
  • Status changed to Fixed 7 days ago
  • πŸ‡§πŸ‡ͺBelgium Wim Leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί
Production build https://api.contrib.social 0.61.6-2-g546bc20