Problem/Motivation

Hi,

2 questions in case it will be too late later for UI Patterns Library.

1: Are components label and description (and potentially other metadata) translatable?
2: In the component library templates, will it be possible to have the component translated label and its original label? To have rendering like the sidebar of https://www.systeme-de-design.gouv.fr/composants-et-modeles:

Accordéon - Accordion
Ajout de fichier - Upload
Alerte - Alert
Badge - Badge
Bandeau d'information importante - Notice
Barre de recherche - Search
Bouton - Button

Also, if I remember well, in SDC it is possible to indicate the lifecycle of a component (experimental, deprecated, etc.), I think it will be nice to put some badges and/or colors and/or infos in the library based on this metadata.

For example, there are components with a "new" character on https://www.systeme-de-design.gouv.fr/composants-et-modeles which made me think about that.

TODO

This POC is ok for:
- name/label
- description
- group/category

The remaining metadata that needs to be made translatable:
- links title
- variants title
- variants description
- slots title
- slots description
- props title
- props description
- potentially other props keys depending on the prop itself

CommentFileSizeAuthor
#5 Capture d’écran du 2024-12-10 13-56-47.png129.76 KBgrimreaper

Issue fork ui_patterns-3481491

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

grimreaper created an issue. See original summary.

pdureau’s picture

pdureau commented

Also, if I remember well, in SDC it is possible to indicate the lifecycle of a component (experimental, deprecated, etc.), I think it will be nice to put some badges and/or colors and/or infos in the library based on this metadata.

SDC has this:

    "status": {
      "type": "string",
      "title": "Development Status",
      "description": "Use this property to identify if the component can be safely used in production.",
      "enum": [
        "experimental",
        "stable",
        "deprecated",
        "obsolete"
      ]
    },
pdureau’s picture

pdureau commented
Title: Components metadata translation questions/ideas » [2.0.0-rc] Components metadata translation questions/ideas
Assigned: Unassigned » grimreaper

Hi Grimreaper,

Let's not forget this issue. Do we have something to do for 2.0.0-rc1?

grimreaper opened merge request !294

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
StatusFileSize
new Capture d’écran du 2024-12-10 13-56-47.png129.76 KB

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Title: [2.0.0-rc] Components metadata translation questions/ideas » [2.0.0-rc] Make components metadata translatable
Category: Support request » Feature request
grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Assigned: grimreaper » Unassigned
Issue summary: View changes
Status: Active » Needs work

This POC is ok for:
- name/label
- description
- group/category

The remaining metadata that needs to be made translatable:
- links title
- variants title
- variants description
- slots title
- slots description
- props title
- props description
- potentially other props keys depending on the prop itself

pdureau’s picture

pdureau commented
Title: [2.0.0-rc] Make components metadata translatable » [2.0.0-rc1] Make components metadata translatable
pdureau’s picture

pdureau commented

See also this Core issue: #3493076: Props have no (translatable) labels

pdureau’s picture

pdureau commented
Title: [2.0.0-rc1] Make components metadata translatable » [2.0.0-rc2] Make components metadata translatable
pdureau’s picture

pdureau commented
Title: [2.0.0-rc2] Make components metadata translatable » [2.0.x] Make components metadata translatable