-
Notifications
You must be signed in to change notification settings - Fork 27
New Crowdin updates #248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
New Crowdin updates #248
Conversation
📝 WalkthroughWalkthroughThis pull request restructures API documentation navigation across six language versions, adds machine translations and data migrations navigation entries, implements German component documentation translations, and applies extensive French localization updates including gender-inclusive language, terminology corrections, and UI label standardization. Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~50 minutes The pull request involves substantial scope with 60+ affected files across six language versions. While primarily documentation-focused, the heterogeneous nature of changes—including API navigation restructuring with numerous nested references, German translations requiring semantic accuracy, French terminology mappings with path corrections, and gender-inclusive language updates—demands careful verification of cross-references and contextual consistency across multiple files and languages. Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 16
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/fr/modules/admin/pages/features/social_features/newsletters.adoc (1)
47-47: Terminology inconsistency: "appel à l'action" vs "appel à action".Line 47 uses "appel à l'action" (with the article "l'"), while lines 77, 90, and 94 use "appel à action" (without the article). For consistency, the same form should be used throughout the document.
Suggested fix for terminology consistency
Option 1: Use "appel à l'action" everywhere (more formal):
-.Formulaire Nouvelle newsletter "Image, texte et bouton d'appel à action" +.Formulaire Nouvelle newsletter "Image, texte et bouton d'appel à l'action"-|Texte du bouton d'appel à action +|Texte du bouton d'appel à l'action-|URL du bouton d'appel à action +|URL du bouton d'appel à l'actionOption 2: Use "appel à action" everywhere (matches current usage in most places):
-* Bouton Image, texte et appel à l'action : recommandé pour des contenus plus élaborés +* Bouton Image, texte et appel à action : recommandé pour des contenus plus élaborésAlso applies to: 77-77, 90-94
🤖 Fix all issues with AI agents
In `@docs/de/modules/admin/pages/components/accountability.adoc`:
- Line 15: The German text uses mixed forms of address — change the sentence "In
diesem Abschnitt der Dokumentation findest du Informationen dazu, wie du all
diese Elemente konfigurierst und verwaltest:" to match the rest of the
document's formal tone (use "Sie"); update both occurrences of "du" in that
sentence to "Sie" (e.g., "In diesem Abschnitt der Dokumentation finden Sie
Informationen dazu, wie Sie all diese Elemente konfigurieren und verwalten:") so
the phrasing aligns with other sections; verify other nearby sentences in
accountability.adoc for any remaining "du" instances and convert them to "Sie"
for consistency.
In `@docs/de/modules/admin/pages/components/blog.adoc`:
- Line 65: The translation of the header ".Schritteinstellungen" for "Step
settings" is correct, but the surrounding content in this German docs file still
contains substantial English; update the remaining English section headers,
descriptions, and field explanations in the file so the page is fully localized
— search for English strings such as "Step settings", other section headers and
field descriptions within docs/de/modules/admin/pages/components/blog.adoc and
replace them with their appropriate German counterparts, keeping terminology
consistent with ".Schritteinstellungen".
In `@docs/de/modules/releases/pages/index.adoc`:
- Line 12: Replace the incorrect blog URL slug in the markdown list entry that
currently reads "https://decidim.org/blog/2022-02-new-version-0-26-0/" (the line
starting with "* https://decidim.org/blog/2022-02-new-version-0-26-0/[Version
0.26 (2022-02-22)]") with the correct slug
"https://decidim.org/blog/2022-02-22-new-version-0-26-0/" so the link resolves
(keep the surrounding list item text "[Version 0.26 (2022-02-22)]" unchanged).
In `@docs/fr/modules/admin/pages/components/accountability.adoc`:
- Around line 20-22: The two xref strings
"xref:admin:components/Accounability/statuses.adoc" and
"xref:admin:components/Accounability/import.adoc" contain a typo and incorrect
capitalization; change both occurrences to use the correct, lowercase directory
name "accountability" (i.e.,
"xref:admin:components/accountability/statuses.adoc" and
"xref:admin:components/accountability/import.adoc") so the cross-references
resolve properly.
In `@docs/fr/modules/admin/pages/components/proposals.adoc`:
- Around line 15-16: The xref path in proposals.adoc contains a typo:
"xref:admin:components/proposs/special_configurations/collaborative_drafts.adoc"
should reference "components/proposals"; open
docs/fr/modules/admin/pages/components/proposals.adoc and replace the broken
xref string (the entry linking to Brouillons collaboratifs) with the correct
path
"xref:admin:components/proposals/special_configurations/collaborative_drafts.adoc"
so the link resolves.
In
`@docs/fr/modules/admin/pages/components/proposals/special_configurations.adoc`:
- Around line 16-17: The xref on line containing
"xref:admin:components/proposs/special_configurations/collaborative_drafts.adoc"
has a typo ("proposs") that breaks the link; update that token to "proposals" so
the entry reads
"xref:admin:components/proposals/special_configurations/collaborative_drafts.adoc"
(keep the rest of the xref text intact and ensure spelling matches the existing
"proposals" directory used by the other entry such as the "amendements" xref).
In `@docs/fr/modules/admin/pages/features/participant_actions/notifications.adoc`:
- Around line 209-220: Replace the misspelled component name "Brouillon de
roposition" with the correct "Brouillon de proposition" in all notification rows
shown (search for the exact string "Brouillon de roposition"); update each
occurrence so the component name column is consistently spelled, e.g., in the
notification lines referencing contributor access, acceptance, rejection,
removal, and user actions.
In `@docs/fr/modules/admin/pages/features/social_features/badges.adoc`:
- Line 68: Update the image caption text on the badges page so the verb is
correct: change the alt/caption string "La proposition soutien le badge" to "La
proposition soutient le badge" where the image reference is defined (the line
containing image:features/badges/proposal_supports_badge.png[La proposition
soutien le badge]); ensure only the caption text is modified and
punctuation/spacing around the image macro remains unchanged.
In `@docs/fr/modules/admin/pages/index.adoc`:
- Around line 46-47: Two consecutive xref entries use the same link label
"Fonctionnalités" causing ambiguity; update one of the xref labels to clearly
differentiate the targets by editing the lines referencing admin:components.adoc
and admin:features.adoc—for example keep
xref:admin:components.adoc[Fonctionnalités] as-is and change
xref:admin:features.adoc[Fonctionnalités] to xref:admin:features.adoc[Autres
fonctionnalités] or xref:admin:features.adoc[Fonctionnalités générales] so the
components vs platform features are explicit.
In `@docs/fr/modules/admin/pages/participants.adoc`:
- Around line 25-28: Update the two inclusive-form typos in the xref link
labels: replace "Groupes d'utilisateur·trixces" with "Groupes
d'utilisateur·trice·s" and replace "Utilisateur·trixces représenté·exs" with
"Utilisateur·trice·s représenté·e·s" so the link texts use the standard
inclusive spellings; locate and edit the xref lines containing those exact
strings to apply the corrections.
In `@docs/fr/modules/admin/pages/settings/scopes.adoc`:
- Line 9: Fix the French typos: replace “peuventt” with “peuvent” in the
sentence containing "Les secteurs peuvent également avoir des types..." (the
fragment shown in the diff) and replace “posiible defiltrer” with the correct
phrase “possible de filtrer” where it appears around line 93; ensure spacing and
accents are correct to read “possible de filtrer”.
- Line 96: The sentence uses the old term "portée" whereas the document has been
renamed to "secteur"; update that sentence to consistently use "secteur" (e.g.,
replace both occurrences of "portée" with "secteur") so it reads "...le filtrage
ne concerne qu'une seule secteur et ses secteurs enfants. Par exemple,
imaginons..." ensuring plural/agreement is correct with the surrounding text.
In `@docs/fr/modules/admin/pages/spaces/initiatives.adoc`:
- Around line 38-41: Update the inconsistent xref module name in the link string
starting with
"xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du
comité]" to use the correct module "espaces" so it matches the other links (i.e.
change "xref:admin:espace:..." to "xref:admin:espaces:..."); ensure the
corrected xref exactly mirrors the neighboring xref patterns like
"xref:admin:espaces:initiatives/..." to avoid broken links.
In `@docs/fr/modules/admin/pages/spaces/initiatives/manage.adoc`:
- Line 8: Update the broken xref entry shown as
"xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du
comité]" by correcting the namespace and filename: change "espace:" to
"espaces:" and "commissione.adoc" to "committee.adoc" so the final xref reads
"xref:admin:espaces/initiatives/author_manage/committee.adoc[Membres du
comité]".
In `@docs/pt/modules/admin/pages/components/meetings/meetings.adoc`:
- Around line 44-45: Remove the repeated phrase "Dicas de localização:
informações adicionais" so the table row contains a single instance followed by
the example sentence ("Example: the floor of the building...") and ensure the
duplicate occurrences of the same phrase elsewhere in the document are
deduplicated as well; locate the table cells containing the string "Dicas de
localização: informações adicionais" and replace the triple repetition with one
copy plus the example text.
In `@docs/ro/modules/ROOT/nav.adoc`:
- Line 28: nav.adoc contains 134 broken xref targets because it references
non-existent modules (develop, services, customize, install, configure) — for
example the xref services:machine_translation.adoc at the top — so either remove
or replace those xref entries in nav.adoc or add the missing Romanian module
files; update the NAV by deleting or commenting out all xref targets whose
module prefix is develop:, services:, customize:, install:, or configure:, or
alternatively add corresponding translated module files under docs/ro/modules
with the referenced article names (e.g., machine_translation.adoc) so the xref
targets resolve.
🧹 Nitpick comments (2)
docs/fr/modules/admin/pages/features/social_features/newsletters.adoc (1)
174-176: Action verb standardization improved, but check line 176.The changes standardize action names to infinitive form and use "Modifier" (preferred in French UI) instead of "Editer". However, line 176 still contains "Éditer la newsletter" in the definition, which may create a terminology inconsistency.
Consider whether line 176 should also use "Modifier" for consistency:
Optional terminology alignment
-|Éditer la newsletter. +|Modifier la newsletter.Also applies to: 190-190
docs/de/modules/admin/pages/components/meetings.adoc (1)
8-8: German translation is correct but file remains partially translated.The German translation is grammatically correct and appropriately uses the informal "du" form. However, this file contains mixed English and German content, which may create an inconsistent user experience.
Consider completing the German localization for the entire file to maintain consistency, or indicate this is work-in-progress documentation.
| image::components/accountability/example02.png[Example of a result] | ||
|
|
||
| In this documentation section, you can find how to configure and manage all of those items: | ||
| In diesem Abschnitt der Dokumentation findest du Informationen dazu, wie du all diese Elemente konfigurierst und verwaltest: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Align form of address across the German doc.
Line 15 uses “du”, while later sections use “Sie”. Consider standardizing the tone (formal vs. informal) for consistency in the German localization.
🤖 Prompt for AI Agents
In `@docs/de/modules/admin/pages/components/accountability.adoc` at line 15, The
German text uses mixed forms of address — change the sentence "In diesem
Abschnitt der Dokumentation findest du Informationen dazu, wie du all diese
Elemente konfigurierst und verwaltest:" to match the rest of the document's
formal tone (use "Sie"); update both occurrences of "du" in that sentence to
"Sie" (e.g., "In diesem Abschnitt der Dokumentation finden Sie Informationen
dazu, wie Sie all diese Elemente konfigurieren und verwalten:") so the phrasing
aligns with other sections; verify other nearby sentences in accountability.adoc
for any remaining "du" instances and convert them to "Sie" for consistency.
| |=== | ||
|
|
||
| .Step settings | ||
| .Schritteinstellungen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Translation is correct.
The German translation "Schritteinstellungen" for "Step settings" is accurate and appropriate for this context.
However, note that this German documentation file contains substantial English content (section headers, descriptions, field explanations). While this is typical of incremental localization efforts, German-speaking administrators may experience a mixed-language interface that could affect usability.
🤖 Prompt for AI Agents
In `@docs/de/modules/admin/pages/components/blog.adoc` at line 65, The translation
of the header ".Schritteinstellungen" for "Step settings" is correct, but the
surrounding content in this German docs file still contains substantial English;
update the remaining English section headers, descriptions, and field
explanations in the file so the page is fully localized — search for English
strings such as "Step settings", other section headers and field descriptions
within docs/de/modules/admin/pages/components/blog.adoc and replace them with
their appropriate German counterparts, keeping terminology consistent with
".Schritteinstellungen".
| * https://decidim.org/blog/2023-12-20-new-version-0-28-0/[Version 0.28 (2023-12-20)] | ||
| * https://decidim.org/blog/2022-09-30-new-version-0-27-0/[Version 0.27 (2022-09-30)] | ||
| * https://decidim.org/blog/2022-02-22-new-version-0-26-0/[Version 0.26 (2022-02-22)] | ||
| * https://decidim.org/blog/2022-02-new-version-0-26-0/[Version 0.26 (2022-02-22)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
https://decidim.org/blog/2022-02-new-version-0-26-0/ URL validity
💡 Result:
The URL you gave returns "404 Not Found" (invalid). [2]
The correct post exists at https://decidim.org/blog/2022-02-22-new-version-0-26-0/ — try that URL. [1]
Sources: [1] Decidim blog — "New version 0.26.0" (22/02/2022). [2] Fetch of the original URL returned 404.
Revert the blog URL to the correct slug with the full date.
The URL slug change is incorrect. The current URL (https://decidim.org/blog/2022-02-new-version-0-26-0/) returns 404 Not Found. The correct URL is https://decidim.org/blog/2022-02-22-new-version-0-26-0/ — it requires the full date 2022-02-22 in the slug, not just 2022-02.
🤖 Prompt for AI Agents
In `@docs/de/modules/releases/pages/index.adoc` at line 12, Replace the incorrect
blog URL slug in the markdown list entry that currently reads
"https://decidim.org/blog/2022-02-new-version-0-26-0/" (the line starting with
"* https://decidim.org/blog/2022-02-new-version-0-26-0/[Version 0.26
(2022-02-22)]") with the correct slug
"https://decidim.org/blog/2022-02-22-new-version-0-26-0/" so the link resolves
(keep the surrounding list item text "[Version 0.26 (2022-02-22)]" unchanged).
| * xref:admin:components/Accounability/statuses.adoc[Progrès] | ||
| * xref:admin:components/accountability/milestone.adoc[Étapes] | ||
| * xref:admin:components/Accounability/import.adoc[Importer et exporter les résultats] | ||
| * xref:admin:components/Accounability/import.adoc[Importer et exporter les réalisations] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify the correct path for accountability component documentation
echo "=== Searching for accountability documentation structure ==="
fd -t d "accountability" docs/fr/modules/admin/pages/components/
echo -e "\n=== Checking for statuses.adoc ==="
fd -t f "statuses.adoc" docs/fr/modules/admin/pages/components/
echo -e "\n=== Checking for import.adoc ==="
fd -t f "import.adoc" docs/fr/modules/admin/pages/components/
echo -e "\n=== Listing all directories in components ==="
ls -la docs/fr/modules/admin/pages/components/ 2>/dev/null || echo "Path not found"
echo -e "\n=== Checking the exact file being reviewed ==="
if [ -f "docs/fr/modules/admin/pages/components/accountability.adoc" ]; then
cat -n docs/fr/modules/admin/pages/components/accountability.adoc | sed -n '18,24p'
fiRepository: decidim/documentation
Length of output: 1836
Fix broken cross-references with typos.
The xref paths on lines 20 and 22 contain "Accounability" (missing 't' in "accountability"). Additionally, the capitalized 'A' is inconsistent with the lowercase "accountability" used on lines 19 and 21, and with the actual directory structure. These broken paths will prevent documentation links from resolving.
🔧 Proposed fix
-* xref:admin:components/Accounability/statuses.adoc[Progrès]
+* xref:admin:components/accountability/statuses.adoc[Progrès]
* xref:admin:components/accountability/milestone.adoc[Étapes]
-* xref:admin:components/Accounability/import.adoc[Importer et exporter les réalisations]
+* xref:admin:components/accountability/import.adoc[Importer et exporter les réalisations]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * xref:admin:components/Accounability/statuses.adoc[Progrès] | |
| * xref:admin:components/accountability/milestone.adoc[Étapes] | |
| * xref:admin:components/Accounability/import.adoc[Importer et exporter les résultats] | |
| * xref:admin:components/Accounability/import.adoc[Importer et exporter les réalisations] | |
| * xref:admin:components/accountability/statuses.adoc[Progrès] | |
| * xref:admin:components/accountability/milestone.adoc[Étapes] | |
| * xref:admin:components/accountability/import.adoc[Importer et exporter les réalisations] |
🤖 Prompt for AI Agents
In `@docs/fr/modules/admin/pages/components/accountability.adoc` around lines 20 -
22, The two xref strings "xref:admin:components/Accounability/statuses.adoc" and
"xref:admin:components/Accounability/import.adoc" contain a typo and incorrect
capitalization; change both occurrences to use the correct, lowercase directory
name "accountability" (i.e.,
"xref:admin:components/accountability/statuses.adoc" and
"xref:admin:components/accountability/import.adoc") so the cross-references
resolve properly.
| ** xref:admin:components/proposals/special_configurations/amendements.adoc[Amendements] | ||
| ** xref:admin:components/proposs/special_configurations/collaborative_drafts.adoc[Brouillons collaboratifs] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix broken xref path typo (proposs).
Line 16 still points to components/proposs/..., which likely doesn’t exist.
🔧 Proposed fix
-** xref:admin:components/proposs/special_configurations/collaborative_drafts.adoc[Brouillons collaboratifs]
+** xref:admin:components/proposals/special_configurations/collaborative_drafts.adoc[Brouillons collaboratifs]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ** xref:admin:components/proposals/special_configurations/amendements.adoc[Amendements] | |
| ** xref:admin:components/proposs/special_configurations/collaborative_drafts.adoc[Brouillons collaboratifs] | |
| ** xref:admin:components/proposals/special_configurations/amendements.adoc[Amendements] | |
| ** xref:admin:components/proposals/special_configurations/collaborative_drafts.adoc[Brouillons collaboratifs] |
🤖 Prompt for AI Agents
In `@docs/fr/modules/admin/pages/components/proposals.adoc` around lines 15 - 16,
The xref path in proposals.adoc contains a typo:
"xref:admin:components/proposs/special_configurations/collaborative_drafts.adoc"
should reference "components/proposals"; open
docs/fr/modules/admin/pages/components/proposals.adoc and replace the broken
xref string (the entry linking to Brouillons collaboratifs) with the correct
path
"xref:admin:components/proposals/special_configurations/collaborative_drafts.adoc"
so the link resolves.
| * Le filtrage dans la barre latérale est également disponible dans certains composants, où vous pouvez contrôler si ces filtres sont affichés avec la case à cocher "Scopes activés" dans les paramètres. Il active également le sélecteur de portée dans le formulaire de création de ressource. | ||
|
|
||
| Vous pouvez également configurer un espace participatif de sorte que le filtrage ne concerne qu'une seule portée et ses portées enfants. Par exemple, imaginons que votre organisation ait 3 portées différentes pour 3 villes, chacune ayant des portées enfants pour les quartiers urbains. | ||
| Vous pouvez également configurer un espace participatif de sorte que le filtrage ne concerne qu'une seule portée et ses portées enfants. Par exemple, imaginons que votre organisation ait 3 secteurs différents pour 3 villes, chacune ayant des secteurs enfants pour les quartiers urbains. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terminology drift: “portée” vs “secteur”.
Line 96 reintroduces “portée”, which conflicts with the rest of the rename to “secteur”. Consider aligning this sentence to the new terminology.
✅ Suggested fix
-Vous pouvez également configurer un espace participatif de sorte que le filtrage ne concerne qu'une seule portée et ses portées enfants. Par exemple, imaginons que votre organisation ait 3 secteurs différents pour 3 villes, chacune ayant des secteurs enfants pour les quartiers urbains.
+Vous pouvez également configurer un espace participatif de sorte que le filtrage ne concerne qu'un seul secteur et ses secteurs enfants. Par exemple, imaginons que votre organisation ait 3 secteurs différents pour 3 villes, chacune ayant des secteurs enfants pour les quartiers urbains.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Vous pouvez également configurer un espace participatif de sorte que le filtrage ne concerne qu'une seule portée et ses portées enfants. Par exemple, imaginons que votre organisation ait 3 secteurs différents pour 3 villes, chacune ayant des secteurs enfants pour les quartiers urbains. | |
| Vous pouvez également configurer un espace participatif de sorte que le filtrage ne concerne qu'un seul secteur et ses secteurs enfants. Par exemple, imaginons que votre organisation ait 3 secteurs différents pour 3 villes, chacune ayant des secteurs enfants pour les quartiers urbains. |
🤖 Prompt for AI Agents
In `@docs/fr/modules/admin/pages/settings/scopes.adoc` at line 96, The sentence
uses the old term "portée" whereas the document has been renamed to "secteur";
update that sentence to consistently use "secteur" (e.g., replace both
occurrences of "portée" with "secteur") so it reads "...le filtrage ne concerne
qu'une seule secteur et ses secteurs enfants. Par exemple, imaginons..."
ensuring plural/agreement is correct with the surrounding text.
| ** xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du comité] | ||
| ** xref:admin:espaces/initiatives/admin_manage/components.adoc[Fonctionnalités] | ||
| ** xref:admin:espaces/initiatives/admin_manage/attachments.adoc[Pièces jointes] | ||
| ** xref:admin:espaces/initiatives/admin_manage/moderations.adoc[Modérations] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Align xref module name (espace vs espaces).
Line 38 uses admin:espace:... but neighboring links use admin:espaces:.... If the module is espaces, this link will break.
🔧 Proposed fix
-** xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du comité]
+** xref:admin:espaces:initiatives/author_manage/commissione.adoc[Membres du comité]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ** xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du comité] | |
| ** xref:admin:espaces/initiatives/admin_manage/components.adoc[Fonctionnalités] | |
| ** xref:admin:espaces/initiatives/admin_manage/attachments.adoc[Pièces jointes] | |
| ** xref:admin:espaces/initiatives/admin_manage/moderations.adoc[Modérations] | |
| ** xref:admin:espaces:initiatives/author_manage/commissione.adoc[Membres du comité] | |
| ** xref:admin:espaces/initiatives/admin_manage/components.adoc[Fonctionnalités] | |
| ** xref:admin:espaces/initiatives/admin_manage/attachments.adoc[Pièces jointes] | |
| ** xref:admin:espaces/initiatives/admin_manage/moderations.adoc[Modérations] |
🤖 Prompt for AI Agents
In `@docs/fr/modules/admin/pages/spaces/initiatives.adoc` around lines 38 - 41,
Update the inconsistent xref module name in the link string starting with
"xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du
comité]" to use the correct module "espaces" so it matches the other links (i.e.
change "xref:admin:espace:..." to "xref:admin:espaces:..."); ensure the
corrected xref exactly mirrors the neighboring xref patterns like
"xref:admin:espaces:initiatives/..." to avoid broken links.
| * xref:admin:espaces/initiatives/admin_manage/components.adoc[Components] | ||
| * xref:admin:espaces/initiatives/admin_manage/attachments.adoc[Attachments] | ||
| * xref:admin:espaces/initiatives/admin_manage/moderations.adoc[Moderations] | ||
| * xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du comité] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Find the correct path for initiative author management documentation
echo "=== Searching for initiatives author_manage directory ==="
fd -t d "author_manage" docs/fr/modules/admin/pages/
echo -e "\n=== Searching for files under initiatives directory ==="
fd -t f . docs/fr/modules/admin/pages/spaces/initiatives/ --max-depth 3
echo -e "\n=== Searching for committee-related files ==="
rg -l "comité" docs/fr/modules/admin/pages/spaces/initiatives/ 2>/dev/null || echo "No matches found"
echo -e "\n=== Check what exists in espace vs espaces directories ==="
fd -t d "espace" docs/fr/modules/admin/pages/
echo -e "\n=== Look for commissione or similar files ==="
fd -t f . docs/fr/modules/admin/pages/ -name "*commission*" -o -name "*commissione*"Repository: decidim/documentation
Length of output: 1828
🏁 Script executed:
cat -n docs/fr/modules/admin/pages/spaces/initiatives/manage.adoc | head -15Repository: decidim/documentation
Length of output: 1119
Fix broken cross-reference path.
The xref path contains two errors that break the documentation link:
- "espace:" should be "espaces:" (inconsistent with the actual path and other xrefs on lines 9-12)
- "commissione.adoc" should be "committee.adoc" (the correct filename)
Correct path: xref:admin:espaces/initiatives/author_manage/committee.adoc[Membres du comité]
🤖 Prompt for AI Agents
In `@docs/fr/modules/admin/pages/spaces/initiatives/manage.adoc` at line 8, Update
the broken xref entry shown as
"xref:admin:espace:initiatives/author_manage/commissione.adoc[Membres du
comité]" by correcting the namespace and filename: change "espace:" to
"espaces:" and "commissione.adoc" to "committee.adoc" so the final xref reads
"xref:admin:espaces/initiatives/author_manage/committee.adoc[Membres du
comité]".
| |Dicas de localização: informações adicionais Dicas de localização: informações adicionais Dicas de localização: informações adicionais Example: the floor of the building if it is an in-person meeting, or the meeting password | ||
| if it is an online meeting with restricted access. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove duplicated sentence in “Dicas de localização”.
The description is repeated three times in both table rows, which reads like a translation glitch.
🔧 Proposed fix
-|Dicas de localização: informações adicionais Dicas de localização: informações adicionais Dicas de localização: informações adicionais Example: the floor of the building if it is an in-person meeting, or the meeting password
+|Dicas de localização: informações adicionais. Example: the floor of the building if it is an in-person meeting, or the meeting passwordAlso applies to: 226-227
🤖 Prompt for AI Agents
In `@docs/pt/modules/admin/pages/components/meetings/meetings.adoc` around lines
44 - 45, Remove the repeated phrase "Dicas de localização: informações
adicionais" so the table row contains a single instance followed by the example
sentence ("Example: the floor of the building...") and ensure the duplicate
occurrences of the same phrase elsewhere in the document are deduplicated as
well; locate the table cells containing the string "Dicas de localização:
informações adicionais" and replace the triple repetition with one copy plus the
example text.
| *** xref:services:activestorage.adoc[Active Storage] | ||
| *** xref:services:aitools.adoc[AI Tools] | ||
| *** xref:services:etherpad.adoc[Etherpad] | ||
| *** xref:services:machine_translation.adoc[Machine Translations] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify that xref targets in docs/ro/modules/ROOT/nav.adoc map to existing files.
python - <<'PY'
import re, os, pathlib, sys
nav_path = pathlib.Path("docs/ro/modules/ROOT/nav.adoc")
text = nav_path.read_text(encoding="utf-8")
# capture xref:module:docpath[Label]
targets = re.findall(r"xref:([^:\[]+):([^\[]+)\[", text)
missing = []
found = []
for module, doc in targets:
doc = doc.strip()
# doc may already include .adoc
rel = pathlib.Path("docs/ro/modules") / module / "pages" / doc
if rel.exists():
found.append((module, doc))
else:
missing.append((module, doc, str(rel)))
print(f"Found {len(found)} valid xref targets")
print(f"Missing {len(missing)} xref targets")
if missing:
print("\nMissing xref targets:")
for module, doc, path in missing:
print(f" - xref:{module}:{doc} -> {path}")
PYRepository: decidim/documentation
Length of output: 151
🏁 Script executed:
#!/bin/bash
# Check if nav.adoc exists and its size
if [ ! -f "docs/ro/modules/ROOT/nav.adoc" ]; then
echo "nav.adoc file not found"
exit 1
fi
wc -l docs/ro/modules/ROOT/nav.adoc
echo "---"
# Extract xref targets more efficiently using rg
rg "xref:([^:\[]+):([^\[]+)\[" docs/ro/modules/ROOT/nav.adoc -o -r '$1:$2' | sort -uRepository: decidim/documentation
Length of output: 10033
🏁 Script executed:
#!/bin/bash
# Verify all extracted xref targets exist as files
# Create a list of unique xref targets
cat > /tmp/targets.txt << 'EOF'
admin:components.adoc
admin:components/accountability.adoc
admin:components/accountability/import.adoc
admin:components/accountability/milestone.adoc
admin:components/accountability/results.adoc
admin:components/accountability/statuses.adoc
admin:components/blog.adoc
admin:components/budgets.adoc
admin:components/budgets/budgets.adoc
admin:components/budgets/projects.adoc
admin:components/debates.adoc
admin:components/meetings.adoc
admin:components/meetings/agenda.adoc
admin:components/meetings/close.adoc
admin:components/meetings/meetings.adoc
admin:components/meetings/polls.adoc
admin:components/meetings/registrations.adoc
admin:components/pages.adoc
admin:components/proposals.adoc
admin:components/proposals/answers.adoc
admin:components/proposals/proposals.adoc
admin:components/proposals/special_configurations.adoc
admin:components/proposals/special_configurations/amendments.adoc
admin:components/proposals/special_configurations/collaborative_drafts.adoc
admin:components/proposals/special_configurations/participatory_texts.adoc
admin:components/sortitions.adoc
admin:components/surveys.adoc
services:machine_translation.adoc
develop:machine_translations.adoc
EOF
python - <<'PY'
import pathlib
# Read targets
targets = []
with open('/tmp/targets.txt', 'r') as f:
targets = [line.strip() for line in f if line.strip()]
missing = []
found = []
for target in targets:
parts = target.split(':', 1)
if len(parts) != 2:
continue
module, docpath = parts
# Try with .adoc already included or add it
file_path = pathlib.Path("docs/ro/modules") / module / "pages" / docpath
if file_path.exists():
found.append(target)
else:
missing.append((target, str(file_path)))
print(f"Found: {len(found)} targets")
print(f"Missing: {len(missing)} targets")
if missing:
print("\nMissing targets:")
for target, path in missing[:10]:
print(f" {target} -> {path}")
if len(missing) > 10:
print(f" ... and {len(missing) - 10} more")
PYRepository: decidim/documentation
Length of output: 151
🏁 Script executed:
#!/bin/bash
# Check what modules exist
echo "=== Modules in docs/ro/modules/ ==="
ls -1 docs/ro/modules/ | grep -v "^ROOT$"
echo ""
echo "=== Check if services module has pages directory ==="
ls -la docs/ro/modules/services/ 2>/dev/null | head -10 || echo "services module not found"
echo ""
echo "=== Check for machine_translation.adoc ==="
find docs/ro/modules/services -name "*machine_translation*" 2>/dev/null
echo ""
echo "=== Check for machine_translations.adoc in develop ==="
find docs/ro/modules/develop -name "*machine_translations*" 2>/dev/null
echo ""
echo "=== Check admin module pages directory ==="
ls docs/ro/modules/admin/pages/ 2>/dev/null | head -5 || echo "admin pages not found"Repository: decidim/documentation
Length of output: 435
🏁 Script executed:
#!/bin/bash
# Check the structure of modules more carefully
echo "=== Full structure of admin module ==="
find docs/ro/modules/admin -type f -name "*.adoc" | head -20
echo ""
echo "=== Looking for pages directories in any module ==="
find docs/ro/modules -type d -name "pages"
echo ""
echo "=== Checking nav.adoc for xref format samples ==="
head -40 docs/ro/modules/ROOT/nav.adocRepository: decidim/documentation
Length of output: 3477
🏁 Script executed:
#!/bin/bash
# Check if missing modules exist in other language docs
echo "=== Looking for missing modules in docs structure ==="
find docs -maxdepth 2 -type d -name "modules" | xargs -I {} ls -1 {} | sort | uniq
echo ""
echo "=== Checking English docs for missing modules ==="
ls -1 docs/en/modules/ 2>/dev/null || echo "No en/modules"
echo ""
echo "=== Check if service files exist anywhere ==="
find docs -name "*machine_translation*" 2>/dev/null
echo ""
echo "=== Count of xref targets by module in nav.adoc ==="
rg "xref:([^:\[]+):" docs/ro/modules/ROOT/nav.adoc -o -r '$1' | sort | uniq -c | sort -rnRepository: decidim/documentation
Length of output: 630
Navigation contains 134 broken xref targets—multiple referenced modules do not exist in Romanian docs.
The nav.adoc file references 277 xref targets across 11 modules, but 5 modules (develop, services, customize, install, configure) do not exist in docs/ro/modules/. This breaks 134 navigation links:
developmodule (92 targets) — does not existservicesmodule (10 targets) — does not exist, including line 28'sservices:machine_translation.adoccustomizemodule (14 targets) — does not existinstallmodule (4 targets) — does not existconfiguremodule (4 targets) — does not exist
Only these modules are available in the Romanian docs: admin, contribute, features, publications, releases, understand, whitepaper, and ROOT.
Either remove these xref targets from nav.adoc or add the missing module translations to docs/ro/modules/.
🤖 Prompt for AI Agents
In `@docs/ro/modules/ROOT/nav.adoc` at line 28, nav.adoc contains 134 broken xref
targets because it references non-existent modules (develop, services,
customize, install, configure) — for example the xref
services:machine_translation.adoc at the top — so either remove or replace those
xref entries in nav.adoc or add the missing Romanian module files; update the
NAV by deleting or commenting out all xref targets whose module prefix is
develop:, services:, customize:, install:, or configure:, or alternatively add
corresponding translated module files under docs/ro/modules with the referenced
article names (e.g., machine_translation.adoc) so the xref targets resolve.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.