docs: add docs taxonomy workflow and initial ko/ja/fr translations#671
Merged
softmarshmallow merged 4 commits intomainfrom Apr 20, 2026
Merged
docs: add docs taxonomy workflow and initial ko/ja/fr translations#671softmarshmallow merged 4 commits intomainfrom
softmarshmallow merged 4 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
WalkthroughAdds documentation governance (taxonomy, publishing rules, translation workflow), extensive frontmatter across many docs, many new localized pages (ko/ja/fr) and translation manifest files, and registers Japanese in Docusaurus i18n locales. No application code or public API behavior changed. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/editor/features/tray.md (1)
1-8:⚠️ Potential issue | 🟡 MinorAdd missing
keywordsin frontmatter for this edited active doc.This page is meaningfully edited in frontmatter, but
keywordsis still absent.
As per coding guidelines: “docs/{wg,reference,editor,forms,platform,with-figma,design,math}/**/*.md: Include frontmatter withtitle,description, andkeywordswhen adding or meaningfully editing actively maintained doc pages”.Suggested patch
--- title: Tray description: Organize your canvas with Trays — lightweight containers that group frames without affecting layout or exports. +keywords: + - grida + - editor + - tray + - section + - canvas organization format: md doc_tasks: - enhance - translate ---🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/editor/features/tray.md` around lines 1 - 8, The frontmatter for the edited doc is missing the required keywords field; update the document's YAML frontmatter (the block containing title and description) to add a `keywords` entry (e.g., a short array of relevant terms) alongside `title` and `description` so the frontmatter contains `title`, `description`, and `keywords` as required for active docs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/forms/translations/ko/respondent-email-notifications.md`:
- Line 15: Change the heading "응답자 이메일 알림" from level 3 (###) to level 2 (##) so
the document starts with an h2 as the first content heading; after updating the
"응답자 이메일 알림" heading, scan and adjust subsequent headings in the file to ensure
each lower-level heading only increments by one level to preserve proper
Markdown hierarchy and accessibility.
In `@docs/platform/customers/translations/ko/index.md`:
- Line 73: The link text currently points to the incorrect relative path
`../tags/index.md`; update it to `../../tags/index.md` so from the
`translations/ko/` folder it resolves to the correct tags doc
(docs/platform/customers/tags/index.md). Replace the string `../tags/index.md`
with `../../tags/index.md` in the line containing "[태그 문서](../tags/index.md)도
참고하세요." to fix the broken link.
In `@docs/with-figma/guides/translations/ko/how-to-get-fig-file.md`:
- Line 111: Broken relative link: update the markdown link target used in
"[Figma에서 복사 & 붙여넣기]" which currently points to
../../editor/features/copy-paste-figma.md (resolves incorrectly) to the correct
relative path ../../../editor/features/copy-paste-figma.md so it resolves from
docs/with-figma/guides/translations/ko/ to
docs/with-figma/editor/features/copy-paste-figma.md.
In `@docs/with-figma/translations/ko/index.md`:
- Around line 65-67: The three broken relative links (the link lines with anchor
texts "Figma personal access token 가져오기", "공유 가능한 Figma 디자인 링크 가져오기", and "로컬
`.fig` 파일 저장하기") point to ./guides/... which resolves incorrectly; update each
href to use the correct relative path ../../guides/translations/ko/<filename>
(e.g., replace ./guides/how-to-get-personal-access-token.md with
../../guides/translations/ko/how-to-get-personal-access-token.md) so they
resolve to the Korean guide translations from this index file.
- Around line 29-30: Update the broken relative links in
docs/with-figma/translations/ko/index.md: replace the link target
./assistant/01-intro.mdx with ../../assistant/01-intro.mdx and replace
./assistant/design-assistant/index.mdx with
../../assistant/design-assistant/index.mdx so the paths correctly resolve to
docs/with-figma/assistant/.
- Line 42: The link using the broken relative path
'../editor/features/copy-paste-figma.md' in the "**자세히 보기**: [Figma에서 복사 &
붙여넣기]" anchor should be replaced with a universal routing link; update the link
target to the universal route (e.g. '/editor/features/copy-paste-figma') while
keeping the same link text so the markdown becomes a universal route to the
editor page instead of the relative .md path.
---
Outside diff comments:
In `@docs/editor/features/tray.md`:
- Around line 1-8: The frontmatter for the edited doc is missing the required
keywords field; update the document's YAML frontmatter (the block containing
title and description) to add a `keywords` entry (e.g., a short array of
relevant terms) alongside `title` and `description` so the frontmatter contains
`title`, `description`, and `keywords` as required for active docs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4fc3da72-33f4-4f2f-aae8-333508b0af7e
📒 Files selected for processing (29)
apps/docs/CONTRIBUTING.mdapps/docs/README.mddocs/AGENTS.mddocs/editor/features/tray.mddocs/editor/shortcuts/index.mddocs/editor/shortcuts/translations/ko/index.mddocs/editor/shortcuts/translations/meta.jsondocs/forms/respondent-email-notifications.mddocs/forms/translations/ko/respondent-email-notifications.mddocs/forms/translations/meta.jsondocs/platform/customers/index.mddocs/platform/customers/translations/ko/index.mddocs/platform/index.mddocs/platform/tags/index.mddocs/platform/tags/translations/ko/index.mddocs/platform/tags/translations/meta.jsondocs/platform/translations/ko/index.mddocs/platform/translations/meta.jsondocs/support/index.mdxdocs/with-figma/guides/how-to-get-fig-file.mddocs/with-figma/guides/how-to-get-personal-access-token.mddocs/with-figma/guides/how-to-get-sharable-design-link.mddocs/with-figma/guides/translations/ko/how-to-get-fig-file.mddocs/with-figma/guides/translations/ko/how-to-get-personal-access-token.mddocs/with-figma/guides/translations/ko/how-to-get-sharable-design-link.mddocs/with-figma/guides/translations/meta.jsondocs/with-figma/index.mddocs/with-figma/translations/ko/index.mddocs/with-figma/translations/meta.json
| - update | ||
| --- | ||
|
|
||
| ### 응답자 이메일 알림 |
There was a problem hiding this comment.
Fix heading level structure.
The first content heading should be h2 (##) rather than h3 (###). Markdown heading levels should increment by one level at a time for proper document structure and accessibility.
📝 Proposed fix for heading level
-### 응답자 이메일 알림
+## 응답자 이메일 알림You may also need to adjust subsequent headings to maintain the hierarchy. Based on the content, the structure should likely be:
-### 응답자 이메일 알림
+## 응답자 이메일 알림
-### 시작하기 전에 확인할 점 (CIAM / 검증된 이메일)
+## 시작하기 전에 확인할 점 (CIAM / 검증된 이메일)
-### 응답자 이메일 알림 활성화 방법
+## 응답자 이메일 알림 활성화 방법
-### 이메일 내용 커스터마이즈 방법
+## 이메일 내용 커스터마이즈 방법
-### 어떤 이메일이 발송되나요? (요약)
+## 어떤 이메일이 발송되나요? (요약)
-### 템플릿 변수 (Handlebars)
+## 템플릿 변수 (Handlebars)
#### 사용 가능한 변수
+### 사용 가능한 변수
#### 예시
+### 예시
-### 문제 해결
+## 문제 해결📝 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.
Suggested change
| ### 응답자 이메일 알림 | |
| ## 응답자 이메일 알림 |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 15-15: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/forms/translations/ko/respondent-email-notifications.md` at line 15,
Change the heading "응답자 이메일 알림" from level 3 (###) to level 2 (##) so the
document starts with an h2 as the first content heading; after updating the "응답자
이메일 알림" heading, scan and adjust subsequent headings in the file to ensure each
lower-level heading only increments by one level to preserve proper Markdown
hierarchy and accessibility.
|
|
||
| > **CSV 참고:** CSV 파일에서 `tags`를 전달할 때는 `"tag1,tag2,tag3"`처럼 쉼표로 구분된 문자열을 큰따옴표로 감싸서 입력해야 합니다. | ||
|
|
||
| [태그 문서](../tags/index.md)도 참고하세요. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check if the tags documentation exists and determine the correct path
# Check for English tags doc
if [ -f "docs/platform/tags/index.md" ]; then
echo "✓ English tags doc exists at: docs/platform/tags/index.md"
fi
# Check for Korean tags translation
if [ -f "docs/platform/tags/translations/ko/index.md" ]; then
echo "✓ Korean tags translation exists at: docs/platform/tags/translations/ko/index.md"
fi
# Show correct relative paths
echo ""
echo "From: docs/platform/customers/translations/ko/index.md"
echo "To English: ../../../tags/index.md"
echo "To Korean: ../../../tags/translations/ko/index.md"Repository: gridaco/grida
Length of output: 336
Fix broken relative link to tags documentation.
The relative link ../tags/index.md resolves incorrectly. From docs/platform/customers/translations/ko/, this path would resolve to docs/platform/customers/translations/tags/index.md, which does not exist.
Proposed fix
-[태그 문서](../tags/index.md)도 참고하세요.
+[태그 문서](../../../tags/translations/ko/index.md)도 참고하세요.(Links to the Korean translation of tags documentation.)
📝 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.
Suggested change
| [태그 문서](../tags/index.md)도 참고하세요. | |
| [태그 문서](../../../tags/translations/ko/index.md)도 참고하세요. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/platform/customers/translations/ko/index.md` at line 73, The link text
currently points to the incorrect relative path `../tags/index.md`; update it to
`../../tags/index.md` so from the `translations/ko/` folder it resolves to the
correct tags doc (docs/platform/customers/tags/index.md). Replace the string
`../tags/index.md` with `../../tags/index.md` in the line containing "[태그
문서](../tags/index.md)도 참고하세요." to fix the broken link.
|
|
||
| - [Figma Help: Save a local copy of files](https://help.figma.com/hc/en-us/articles/8403626871063-Save-a-local-copy-of-files) | ||
| - [Figma Help: Download files from Figma](https://help.figma.com/hc/en-us/articles/360041003114-Download-files-from-Figma) | ||
| - [Figma에서 복사 & 붙여넣기](../../editor/features/copy-paste-figma.md) - 클립보드 기반 대안 가져오기 방식 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check if the target file exists and find the correct relative path
# Check if English version exists
if [ -f "docs/editor/features/copy-paste-figma.md" ]; then
echo "✓ English version exists at: docs/editor/features/copy-paste-figma.md"
fi
# Check if Korean translation exists
if [ -f "docs/editor/features/translations/ko/copy-paste-figma.md" ]; then
echo "✓ Korean translation exists at: docs/editor/features/translations/ko/copy-paste-figma.md"
fi
# Show the correct relative paths
echo ""
echo "From: docs/with-figma/guides/translations/ko/how-to-get-fig-file.md"
echo "To English: ../../../../editor/features/copy-paste-figma.md"
echo "To Korean: ../../../../editor/features/translations/ko/copy-paste-figma.md"Repository: gridaco/grida
Length of output: 1774
🏁 Script executed:
#!/bin/bash
# Check if the referenced files exist
find docs -name "copy-paste-figma.md" -type f | sort
# Check the directory structure
echo "---"
echo "docs/editor/features/ structure:"
find docs/editor/features -type f -name "*.md" 2>/dev/null | head -20
echo "---"
echo "docs/with-figma/guides/ structure:"
find docs/with-figma/guides -type f -name "*.md" 2>/dev/null | head -20Repository: gridaco/grida
Length of output: 1143
🏁 Script executed:
#!/bin/bash
# Check if there are any examples of universal routing links in the codebase
rg "https://grida\.co/_/" docs/ --max-count=10 -A 2 -B 2
# Also check the actual content of the file at line 111
echo "---"
sed -n '105,115p' docs/with-figma/guides/translations/ko/how-to-get-fig-file.mdRepository: gridaco/grida
Length of output: 3424
🏁 Script executed:
#!/bin/bash
# Check the universal routing documentation
grep -n "copy-paste" docs/wg/platform/universal-docs-routing.md
# Also check if there's a registration for editor features
grep -A 5 -B 5 "editor/features" docs/wg/platform/universal-docs-routing.md | head -50Repository: gridaco/grida
Length of output: 39
🏁 Script executed:
#!/bin/bash
# Read the universal routing documentation
cat docs/wg/platform/universal-docs-routing.md | head -100Repository: gridaco/grida
Length of output: 2646
🏁 Script executed:
#!/bin/bash
# Check how other docs in with-figma folder link to editor docs
grep -r "\[.*\](" docs/with-figma/ | grep -E "\.md\)" | head -20
# Also check editor docs linking patterns
grep -r "\[.*\](" docs/editor/ | grep -E "\.md\)" | head -20Repository: gridaco/grida
Length of output: 3146
Fix broken relative link path.
The relative link ../../editor/features/copy-paste-figma.md resolves incorrectly. From the current location docs/with-figma/guides/translations/ko/, this path would resolve to docs/with-figma/guides/editor/features/copy-paste-figma.md, which does not exist.
🔗 Proposed fix for the link path
-- [Figma에서 복사 & 붙여넣기](../../editor/features/copy-paste-figma.md) - 클립보드 기반 대안 가져오기 방식
+- [Figma에서 복사 & 붙여넣기](../../../../editor/features/copy-paste-figma.md) - 클립보드 기반 대안 가져오기 방식📝 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.
Suggested change
| - [Figma에서 복사 & 붙여넣기](../../editor/features/copy-paste-figma.md) - 클립보드 기반 대안 가져오기 방식 | |
| - [Figma에서 복사 & 붙여넣기](../../../../editor/features/copy-paste-figma.md) - 클립보드 기반 대안 가져오기 방식 |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/with-figma/guides/translations/ko/how-to-get-fig-file.md` at line 111,
Broken relative link: update the markdown link target used in "[Figma에서 복사 &
붙여넣기]" which currently points to ../../editor/features/copy-paste-figma.md
(resolves incorrectly) to the correct relative path
../../../editor/features/copy-paste-figma.md so it resolves from
docs/with-figma/guides/translations/ko/ to
docs/with-figma/editor/features/copy-paste-figma.md.
Comment on lines
+29
to
+30
| - [Assistant](./assistant/01-intro.mdx) | ||
| - [Design Assistant](./assistant/design-assistant/index.mdx) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the actual locations of assistant documentation files
echo "=== Checking assistant doc locations ==="
fd -t f "01-intro.mdx" docs/with-figma/
fd -t f "index.mdx" docs/with-figma/assistant/design-assistant/Repository: gridaco/grida
Length of output: 189
Fix broken relative links to assistant documentation.
The relative paths ./assistant/01-intro.mdx and ./assistant/design-assistant/index.mdx will resolve incorrectly from the current file location docs/with-figma/translations/ko/index.md.
These should be ../../assistant/01-intro.mdx and ../../assistant/design-assistant/index.mdx to correctly reach the assistant docs in docs/with-figma/assistant/.
🔧 Proposed fix for assistant links
-- [Assistant](./assistant/01-intro.mdx)
-- [Design Assistant](./assistant/design-assistant/index.mdx)
+- [Assistant](../../assistant/01-intro.mdx)
+- [Design Assistant](../../assistant/design-assistant/index.mdx)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/with-figma/translations/ko/index.md` around lines 29 - 30, Update the
broken relative links in docs/with-figma/translations/ko/index.md: replace the
link target ./assistant/01-intro.mdx with ../../assistant/01-intro.mdx and
replace ./assistant/design-assistant/index.mdx with
../../assistant/design-assistant/index.mdx so the paths correctly resolve to
docs/with-figma/assistant/.
| - 벡터 데이터와 경로 | ||
| - 컴포넌트 관계 | ||
|
|
||
| **자세히 보기**: [Figma에서 복사 & 붙여넣기](../editor/features/copy-paste-figma.md) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the actual location of the copy-paste-figma documentation
echo "=== Checking editor copy-paste-figma doc location ==="
fd -t f "copy-paste-figma.md" docs/editor/Repository: gridaco/grida
Length of output: 151
🏁 Script executed:
#!/bin/bash
# Explore the structure to verify the relative path issue
echo "=== Directory structure around with-figma/translations/ko/ ==="
find docs/with-figma/translations -type f -name "*.md" | head -20
echo ""
echo "=== Checking if docs/with-figma/translations/ko/index.md exists ==="
test -f "docs/with-figma/translations/ko/index.md" && echo "File exists" || echo "File does not exist"
echo ""
echo "=== Calculate path from ko/ to editor ==="
# Show full relative path structure
tree -L 4 docs/with-figma/ 2>/dev/null || find docs/with-figma -type d | head -20Repository: gridaco/grida
Length of output: 901
🏁 Script executed:
#!/bin/bash
# Check the exact content around line 42 to verify the link
echo "=== Content around line 42 of the Korean translation ==="
sed -n '35,50p' docs/with-figma/translations/ko/index.mdRepository: gridaco/grida
Length of output: 471
🏁 Script executed:
#!/bin/bash
# Verify the exact path calculation
echo "=== Verifying path resolution ==="
# From docs/with-figma/translations/ko/index.md, trace the relative path
echo "Current file: docs/with-figma/translations/ko/index.md"
echo "Relative path in file: ../editor/features/copy-paste-figma.md"
echo "Would resolve to: docs/with-figma/translations/editor/features/copy-paste-figma.md"
echo ""
echo "Checking if that file exists (it shouldn't):"
test -f "docs/with-figma/translations/editor/features/copy-paste-figma.md" && echo "Exists (BUG!)" || echo "Does not exist (as expected)"
echo ""
echo "Correct file should be at:"
echo "docs/editor/features/copy-paste-figma.md"
test -f "docs/editor/features/copy-paste-figma.md" && echo "Exists (correct)" || echo "Does not exist"
echo ""
echo "Proposed fix path (../../../editor/features/copy-paste-figma.md) should resolve to:"
echo "docs/editor/features/copy-paste-figma.md"Repository: gridaco/grida
Length of output: 577
Use universal routing link instead of broken relative path.
The relative path ../editor/features/copy-paste-figma.md is broken and resolves to docs/with-figma/translations/editor/features/copy-paste-figma.md, which doesn't exist. However, per coding guidelines, this file should use universal routing links for linking to editor pages from user-facing docs.
🔧 Fix: Use universal routing link
-**자세히 보기**: [Figma에서 복사 & 붙여넣기](../editor/features/copy-paste-figma.md)
+**자세히 보기**: [Figma에서 복사 & 붙여넣기](https://grida.co/_/editor/features/copy-paste-figma)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/with-figma/translations/ko/index.md` at line 42, The link using the
broken relative path '../editor/features/copy-paste-figma.md' in the "**자세히
보기**: [Figma에서 복사 & 붙여넣기]" anchor should be replaced with a universal routing
link; update the link target to the universal route (e.g.
'/editor/features/copy-paste-figma') while keeping the same link text so the
markdown becomes a universal route to the editor page instead of the relative
.md path.
Comment on lines
+65
to
+67
| - [Figma personal access token 가져오기](./guides/how-to-get-personal-access-token.md) | ||
| - [공유 가능한 Figma 디자인 링크 가져오기](./guides/how-to-get-sharable-design-link.md) | ||
| - [로컬 `.fig` 파일 저장하기](./guides/how-to-get-fig-file.md) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the actual locations of Korean guide translations
echo "=== Checking Korean guide translation locations ==="
fd -t f "how-to-get-personal-access-token.md" docs/with-figma/ --exec echo "Found: {}"
fd -t f "how-to-get-sharable-design-link.md" docs/with-figma/ --exec echo "Found: {}"
fd -t f "how-to-get-fig-file.md" docs/with-figma/ --exec echo "Found: {}"Repository: gridaco/grida
Length of output: 524
🏁 Script executed:
cat -n docs/with-figma/translations/ko/index.md | sed -n '60,75p'Repository: gridaco/grida
Length of output: 623
🏁 Script executed:
tree -L 4 docs/with-figma/ | head -50Repository: gridaco/grida
Length of output: 673
Fix broken relative links to guide translations.
The relative paths ./guides/ resolve to docs/with-figma/translations/ko/guides/, which does not exist. Korean guide translations are located at docs/with-figma/guides/translations/ko/. From docs/with-figma/translations/ko/index.md, use ../../guides/translations/ko/<filename>.
Proposed fix
-- [Figma personal access token 가져오기](./guides/how-to-get-personal-access-token.md)
-- [공유 가능한 Figma 디자인 링크 가져오기](./guides/how-to-get-sharable-design-link.md)
-- [로컬 `.fig` 파일 저장하기](./guides/how-to-get-fig-file.md)
+- [Figma personal access token 가져오기](../../guides/translations/ko/how-to-get-personal-access-token.md)
+- [공유 가능한 Figma 디자인 링크 가져오기](../../guides/translations/ko/how-to-get-sharable-design-link.md)
+- [로컬 `.fig` 파일 저장하기](../../guides/translations/ko/how-to-get-fig-file.md)📝 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.
Suggested change
| - [Figma personal access token 가져오기](./guides/how-to-get-personal-access-token.md) | |
| - [공유 가능한 Figma 디자인 링크 가져오기](./guides/how-to-get-sharable-design-link.md) | |
| - [로컬 `.fig` 파일 저장하기](./guides/how-to-get-fig-file.md) | |
| - [Figma personal access token 가져오기](../../guides/translations/ko/how-to-get-personal-access-token.md) | |
| - [공유 가능한 Figma 디자인 링크 가져오기](../../guides/translations/ko/how-to-get-sharable-design-link.md) | |
| - [로컬 `.fig` 파일 저장하기](../../guides/translations/ko/how-to-get-fig-file.md) |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/with-figma/translations/ko/index.md` around lines 65 - 67, The three
broken relative links (the link lines with anchor texts "Figma personal access
token 가져오기", "공유 가능한 Figma 디자인 링크 가져오기", and "로컬 `.fig` 파일 저장하기") point to
./guides/... which resolves incorrectly; update each href to use the correct
relative path ../../guides/translations/ko/<filename> (e.g., replace
./guides/how-to-get-personal-access-token.md with
../../guides/translations/ko/how-to-get-personal-access-token.md) so they
resolve to the Korean guide translations from this index file.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/forms/translations/ja/respondent-email-notifications.md`:
- Line 15: The document uses h3 headings where h2 is required; change the main
heading "回答者向けメール通知" from ### to ## and similarly demote each subsequent heading
one level (e.g., any "### ..." → "## ..." and any "#### ..." → "### ...") for
the other section titles referenced (match by heading text occurrences such as
the headings at lines referenced in the review: the other chapter titles in this
file). Ensure all Markdown headings follow proper hierarchy by reducing each
heading level by one.
In `@docs/platform/customers/translations/ja/index.md`:
- Line 73: The relative markdown link "[tags](../tags/index.md)" in the file
should be corrected because it points to a non-existent path; update the link
target for the tags documentation reference in this file (the "[tags](...)"
occurrence) to the correct relative path — either "../../tags/index.md" to point
to the canonical tags page or "../../tags/translations/ja/index.md" to point to
the Japanese translation — ensuring the link resolves to docs/platform/tags/...
.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 2d4e09a7-7fd6-4fe0-8b56-337158646814
📒 Files selected for processing (20)
apps/docs/docusaurus.config.tsdocs/editor/shortcuts/translations/ja/index.mddocs/editor/shortcuts/translations/meta.jsondocs/forms/translations/ja/respondent-email-notifications.mddocs/forms/translations/meta.jsondocs/platform/customers/translations/ja/index.mddocs/platform/customers/translations/meta.jsondocs/platform/tags/translations/ja/index.mddocs/platform/tags/translations/meta.jsondocs/platform/translations/ja/index.mddocs/platform/translations/meta.jsondocs/translations/ja/index.mddocs/translations/ko/index.mddocs/translations/meta.jsondocs/with-figma/guides/translations/ja/how-to-get-fig-file.mddocs/with-figma/guides/translations/ja/how-to-get-personal-access-token.mddocs/with-figma/guides/translations/ja/how-to-get-sharable-design-link.mddocs/with-figma/guides/translations/meta.jsondocs/with-figma/translations/ja/index.mddocs/with-figma/translations/meta.json
✅ Files skipped from review due to trivial changes (13)
- docs/forms/translations/meta.json
- docs/translations/meta.json
- docs/platform/customers/translations/meta.json
- docs/platform/translations/ja/index.md
- apps/docs/docusaurus.config.ts
- docs/translations/ja/index.md
- docs/translations/ko/index.md
- docs/with-figma/guides/translations/ja/how-to-get-sharable-design-link.md
- docs/with-figma/translations/ja/index.md
- docs/with-figma/guides/translations/ja/how-to-get-fig-file.md
- docs/with-figma/guides/translations/ja/how-to-get-personal-access-token.md
- docs/platform/tags/translations/ja/index.md
- docs/editor/shortcuts/translations/ja/index.md
🚧 Files skipped from review as they are similar to previous changes (5)
- docs/platform/tags/translations/meta.json
- docs/with-figma/translations/meta.json
- docs/with-figma/guides/translations/meta.json
- docs/platform/translations/meta.json
- docs/editor/shortcuts/translations/meta.json
| - update | ||
| --- | ||
|
|
||
| ### 回答者向けメール通知 |
There was a problem hiding this comment.
Fix heading level to h2.
The first content heading should be h2 (##) instead of h3 (###) to follow proper Markdown heading hierarchy. This applies to all subsequent h3 headings in the document as well.
📝 Proposed fix
-### 回答者向けメール通知
+## 回答者向けメール通知Apply the same change to all other headings in the document (lines 25, 34, 43, 54, 61, 87), reducing each by one level (h3 → h2, h4 → h3 if any exist).
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 15-15: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/forms/translations/ja/respondent-email-notifications.md` at line 15, The
document uses h3 headings where h2 is required; change the main heading
"回答者向けメール通知" from ### to ## and similarly demote each subsequent heading one
level (e.g., any "### ..." → "## ..." and any "#### ..." → "### ...") for the
other section titles referenced (match by heading text occurrences such as the
headings at lines referenced in the review: the other chapter titles in this
file). Ensure all Markdown headings follow proper hierarchy by reducing each
heading level by one.
|
|
||
| > **CSV Note:** CSV ファイルで `tags` を渡すときは、`"tag1,tag2,tag3"` のようにカンマ区切りの文字列を二重引用符で囲んで指定してください。 | ||
|
|
||
| [tags](../tags/index.md) も参照してください。 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the link target used at Line 73 and check likely candidates.
set -euo pipefail
echo "1) Show link line from JA page:"
rg -n '\[tags\]\(' docs/platform/customers/translations/ja/index.md -n -C1
echo
echo "2) Check whether the filesystem-relative target exists from this file location:"
python - <<'PY'
from pathlib import Path
p = Path("docs/platform/customers/translations/ja/index.md")
target = (p.parent / "../tags/index.md").resolve()
print("Resolved target:", target)
print("Exists:", target.exists())
PY
echo
echo "3) Find candidate tags docs in platform area:"
fd -i 'index.md' docs/platform | rg -n '/tags/'Repository: gridaco/grida
Length of output: 486
Fix broken relative link to tags documentation
Line 73 uses [tags](../tags/index.md) which resolves to a non-existent path. The correct relative link should be ../../tags/index.md to point to the canonical tags documentation at docs/platform/tags/index.md, or ../../tags/translations/ja/index.md to link to the Japanese translated version.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/platform/customers/translations/ja/index.md` at line 73, The relative
markdown link "[tags](../tags/index.md)" in the file should be corrected because
it points to a non-existent path; update the link target for the tags
documentation reference in this file (the "[tags](...)" occurrence) to the
correct relative path — either "../../tags/index.md" to point to the canonical
tags page or "../../tags/translations/ja/index.md" to point to the Japanese
translation — ensuring the link resolves to docs/platform/tags/... .
softmarshmallow
changed the title
There was a problem hiding this comment.
Actionable comments posted: 11
🧹 Nitpick comments (5)
docs/with-figma/translations/fr/index.md (2)
42-42: Switch editor doc links to universal routing.Line 42 and Line 73 should use
https://grida.co/_/<path>links for user-facing editor docs instead of nested relative paths.As per coding guidelines: "Use universal routing links starting with `https://grida.co/_/` instead of tenant-specific canonical paths for user-facing editor page links."Proposed change
-**En savoir plus** : [Copy & Paste from Figma](../editor/features/copy-paste-figma.md) +**En savoir plus** : [Copy & Paste from Figma](https://grida.co/_/with-figma/editor/features/copy-paste-figma) ... -- [Figma Import Technical Spec](../editor/features/copy-paste-figma.md) +- [Figma Import Technical Spec](https://grida.co/_/with-figma/editor/features/copy-paste-figma)Also applies to: 73-73
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/with-figma/translations/fr/index.md` at line 42, Replace the tenant-relative editor doc links in this file (the "En savoir plus" link text pointing to ../editor/features/copy-paste-figma.md at the occurrences referenced) with universal routing URLs of the form https://grida.co/_/<path>; specifically update any ../editor/... links (including the one at line 42 and the one at line 73) to use https://grida.co/_/editor/features/copy-paste-figma.md (and the corresponding editor paths) so all user-facing editor doc links use the global https://grida.co/_/... routing.
21-21: Avoid external markdown links in docs pages.Line 21 and Line 74 point to external URLs. Per repo policy, use internal relative
/docslinks where possible, otherwise keep external references as inline code (not markdown links).As per coding guidelines: "Never link outside
/docsfrom docs markdown files; use relative links within/docsand reference external paths as inline code instead."Also applies to: 74-74
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/with-figma/translations/fr/index.md` at line 21, The French docs page contains external markdown links (the phrase with "signaler un probleme" pointing to https://github.com/gridaco/grida/issues/new in the sentence starting "L'integration presse-papiers..." and another link at the later occurrence around line 74); replace these markdown links with either an internal relative /docs link if an equivalent doc exists, or convert the external URL to inline code (e.g., `https://github.com/gridaco/grida/issues/new`) to comply with the rule "Never link outside /docs" in markdown files; update both the sentence containing "L'integration presse-papiers avec Figma..." and the other occurrence at line ~74 accordingly.docs/with-figma/guides/translations/fr/how-to-get-fig-file.md (1)
18-18: Replace external markdown links with docs-compliant references.Line 18, Line 109, and Line 110 link to external domains from markdown. This conflicts with the docs linking policy and should be converted to inline code references (or internal relative
/docslinks where available).As per coding guidelines: "Never link outside `/docs` from docs markdown files; use relative links within `/docs` and reference external paths as inline code instead."Proposed change
-> **Note:** Le format de fichier .fig est proprietaire et peut changer sans preavis. Si vous rencontrez des problemes lors de l'import de fichiers .fig, veuillez [nous les signaler](https://github.com/gridaco/grida/issues) ou contacter le support. Vos retours nous aident a maintenir les imports operationnels. +> **Note:** Le format de fichier .fig est proprietaire et peut changer sans preavis. Si vous rencontrez des problemes lors de l'import de fichiers .fig, veuillez nous les signaler via `https://github.com/gridaco/grida/issues` ou contacter le support. Vos retours nous aident a maintenir les imports operationnels. ... -- [Figma Help: Save a local copy of files](https://help.figma.com/hc/en-us/articles/8403626871063-Save-a-local-copy-of-files) -- [Figma Help: Download files from Figma](https://help.figma.com/hc/en-us/articles/360041003114-Download-files-from-Figma) +- Figma Help: Save a local copy of files — `https://help.figma.com/hc/en-us/articles/8403626871063-Save-a-local-copy-of-files` +- Figma Help: Download files from Figma — `https://help.figma.com/hc/en-us/articles/360041003114-Download-files-from-Figma`Also applies to: 109-110
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/with-figma/guides/translations/fr/how-to-get-fig-file.md` at line 18, Replace the external GitHub link "https://github.com/gridaco/grida/issues" found in the note about the .fig file format (the line containing "**Note:** Le format de fichier .fig") and the two other occurrences with docs-compliant references: either convert them to an internal relative /docs link if an equivalent docs page exists, or render the external path as inline code (e.g., `https://github.com/gridaco/grida/issues`) instead of a clickable markdown link; update the three instances so no markdown links point outside /docs.docs/forms/translations/fr/respondent-email-notifications.md (1)
45-45: Consider using proper arrow symbols for French typography.The navigation path uses ASCII
->arrows. While functional, French typography typically prefers the proper arrow symbol→or the word "puis" (then) for improved readability.✨ Suggested improvements
Option 1 - Use proper arrow symbol:
-1. Ouvrez [**Connect -> Channels**](https://grida.co/_/connect/channels) -> **Email Notifications** (meme ecran que ci-dessus). +1. Ouvrez [**Connect → Channels**](https://grida.co/_/connect/channels) → **Email Notifications** (même écran que ci-dessus).Option 2 - Use French connector word:
-1. Ouvrez [**Connect -> Channels**](https://grida.co/_/connect/channels) -> **Email Notifications** (meme ecran que ci-dessus). +1. Ouvrez [**Connect puis Channels**](https://grida.co/_/connect/channels) puis **Email Notifications** (même écran que ci-dessus).Apply similar changes to lines 37-39 if adopting this pattern.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/forms/translations/fr/respondent-email-notifications.md` at line 45, The navigation text "Connect -> Channels -> Email Notifications" uses ASCII arrows; update these instances (search for the string "Connect -> Channels" and the occurrences around lines with "Email Notifications") to use proper French typography by replacing "->" with the arrow symbol "→" or the French connector "puis" (e.g., "Connect → Channels → Email Notifications" or "Connect puis Channels puis Email Notifications"); also apply the same replacement pattern to the related navigation lines referenced around lines 37–39 to keep the docs consistent.docs/editor/shortcuts/translations/fr/index.md (1)
11-12: Consider usingtranslateinstead ofupdatefor doc_tasks.Since this is a new French translation file, the
doc_tasksfield might be more semantically accurate withtranslaterather thanupdate.Suggested adjustment
doc_tasks: - - update + - translate🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/editor/shortcuts/translations/fr/index.md` around lines 11 - 12, The front-matter key doc_tasks currently lists the value "update" but for a new French translation it should read "translate"; locate the doc_tasks entry (the YAML key "doc_tasks" and its value "update") in the translation file and replace the value with "translate" so the task semantics correctly reflect a translation rather than an update.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/editor/shortcuts/translations/fr/index.md`:
- Around line 15-197: The document is missing systematic French diacritics
(accents) across headings and body text; perform a comprehensive accent and
orthography pass to restore correct French (e.g., "Raccourcis de l'editeur
Grida" → "Raccourcis de l'éditeur Grida", "Deplacement" → "Déplacement",
"Selectionner" → "Sélectionner", "Mise a l'echelle" → "Mise à l'échelle",
"precedent" → "précédent", etc.). Review and correct all headings and table
entries (notably the title and section headers like "Outils", "Selection et
navigation", "Edition", "Transformation", "Alignement et distribution", "Mise en
forme du texte", "Proprietes des objets", and "Affichage et zoom") using a
French spell-checker or a native French reviewer, ensure all instances of
apostrophes and accented vowels (é, è, ê, à, ù, ô, ï, ç, etc.) are applied
consistently, and run a final pass to confirm no remaining accent-less words
remain.
- Around line 2-3: Update the frontmatter to include proper French accents:
change the `title` field from "Raccourcis de l'editeur Grida" to "Raccourcis de
l'éditeur Grida" and update the `description` field from "Reference des
raccourcis clavier disponibles dans l'editeur Grida pour les outils, la
selection, l'edition, la mise en page et l'affichage." to "Référence des
raccourcis clavier disponibles dans l'éditeur Grida pour les outils, la
sélection, l'édition, la mise en page et l'affichage." Ensure both `title` and
`description` keys are preserved exactly as named.
In `@docs/forms/translations/fr/respondent-email-notifications.md`:
- Line 15: The document uses h3 headings where the first content heading must be
h2; change the heading "### Notifications email aux repondants" to "##
Notifications email aux repondants" and similarly promote all other occurrences
of "###" headings in this file (the headings at the other noted locations: the
lines containing the same pattern headings after this one) to "##" so the
top-level content headings follow from the frontmatter title; update each "###"
to "##" consistently across the file.
- Around line 1-13: Update the frontmatter values to include correct French
accents: change the title value "Notifications email aux repondants" to
"Notifications email aux répondants" and update the description value to use
accented words—replace "Apprenez a envoyer un email de confirmation personnalise
aux repondants apres une soumission de formulaire dans Grida Forms (email
verifie CIAM requis)." with "Apprenez à envoyer un email de confirmation
personnalisé aux répondants après une soumission de formulaire dans Grida Forms
(email vérifié CIAM requis)." Ensure you edit the frontmatter keys exactly as
shown (title, description, keywords) so the SEO metadata is corrected.
- Around line 15-94: The French translation in
docs/forms/translations/fr/respondent-email-notifications.md contains many
missing accents (e.g., "repondants", "personnalise", "etapes", "verifiee",
"editeur", "expediteur", "integre", "Depannage", "Fiabilite"), so update all
occurrences to proper accented forms (répondants, personnalisé, étapes,
vérifiée, éditeur, expéditeur, intégré, Dépannage, Fiabilité, etc.) across the
headings and body (notably the "### Notifications email aux repondants" heading,
the CIAM / email verifié section, the "Comment activer..." and "Comment
personnaliser..." sections, the "Templates" variables and examples, and the
"Depannage" section) ensuring consistent orthography and plural/tense agreement
(e.g., "être envoyées", "formaté", "être ajoutés").
In `@docs/platform/customers/translations/fr/index.md`:
- Around line 50-51: Replace the external Markdown link to
"https://grida.co/tools/e164" with an internal docs reference or inline code per
docs guidelines: update the sentence containing `phone` and the link text "outil
Grida E.164" so it either points to a relative `/docs/...` page if one exists,
or replace the Markdown link with the URL shown as inline code (e.g.
`https://grida.co/tools/e164`) instead of a clickable external link; ensure the
visible text still explains E.164 formatting and keep the backticked `phone`
identifier unchanged.
- Around line 138-140: Change the heading and text that currently say "upsert"
to explicitly say "mise à jour" and clarify this section describes updating
existing customers by matching the `uid` or `uuid` field in the CSV; update the
heading "Mise a jour (instable)" and the sentence "Pour faire un upsert, vous
devez fournir le champ `uid` ou `uuid` dans le fichier CSV." to wording that
states updates are performed by matching `uid` or `uuid` (e.g., "Pour mettre à
jour des enregistrements, fournissez le champ `uid` ou `uuid` dans le fichier
CSV") so it no longer contradicts the earlier line that says CSV upsert is not
supported.
In `@docs/platform/translations/fr/index.md`:
- Around line 1-10: The frontmatter in the translated page is missing the
required taxonomy field `doc_tasks`; update the top YAML block in
docs/platform/translations/fr/index.md to include a `doc_tasks` entry (choose
one of the allowed values: `enhance`, `update`, or `translate`) — e.g., add
`doc_tasks: translate` to mark this as a translation follow-up — so that the
page conforms to the docs/**/*.md guideline and can be tracked for subsequent
work.
In `@docs/translations/fr/index.md`:
- Around line 1-14: The frontmatter for the publishable doc (id: intro, title:
Documentation Grida) is missing the required doc_tasks field; add a doc_tasks
entry with an allowed value (e.g., doc_tasks: translate) to the YAML frontmatter
so the page includes one of the permitted task tags (enhance, update, translate)
for follow-up tracking.
- Around line 53-55: Replace the three external markdown links ("Repository",
"Website", "Slack") with inline code references instead of linking outside
/docs: remove the markdown link syntax for each item and render the external URL
or path as inline code (e.g., `https://github.com/gridaco/grida`,
`https://grida.co`, `https://grida.co/join-slack`) or, if there are equivalent
docs pages, change them to relative /docs links; update the list lines that
currently contain "Repository", "Website", and "Slack" accordingly so no
markdown link points outside /docs.
In `@docs/with-figma/guides/translations/fr/how-to-get-fig-file.md`:
- Line 111: Replace the fragile relative editor link "[Copy & Paste from Figma]
(../../editor/features/copy-paste-figma.md)" with the universal routing URL
form; update the link target to
"https://grida.co/_/editor/features/copy-paste-figma" so the editor-page link
uses the global tenant-agnostic route instead of the deep relative path.
---
Nitpick comments:
In `@docs/editor/shortcuts/translations/fr/index.md`:
- Around line 11-12: The front-matter key doc_tasks currently lists the value
"update" but for a new French translation it should read "translate"; locate the
doc_tasks entry (the YAML key "doc_tasks" and its value "update") in the
translation file and replace the value with "translate" so the task semantics
correctly reflect a translation rather than an update.
In `@docs/forms/translations/fr/respondent-email-notifications.md`:
- Line 45: The navigation text "Connect -> Channels -> Email Notifications" uses
ASCII arrows; update these instances (search for the string "Connect ->
Channels" and the occurrences around lines with "Email Notifications") to use
proper French typography by replacing "->" with the arrow symbol "→" or the
French connector "puis" (e.g., "Connect → Channels → Email Notifications" or
"Connect puis Channels puis Email Notifications"); also apply the same
replacement pattern to the related navigation lines referenced around lines
37–39 to keep the docs consistent.
In `@docs/with-figma/guides/translations/fr/how-to-get-fig-file.md`:
- Line 18: Replace the external GitHub link
"https://github.com/gridaco/grida/issues" found in the note about the .fig file
format (the line containing "**Note:** Le format de fichier .fig") and the two
other occurrences with docs-compliant references: either convert them to an
internal relative /docs link if an equivalent docs page exists, or render the
external path as inline code (e.g., `https://github.com/gridaco/grida/issues`)
instead of a clickable markdown link; update the three instances so no markdown
links point outside /docs.
In `@docs/with-figma/translations/fr/index.md`:
- Line 42: Replace the tenant-relative editor doc links in this file (the "En
savoir plus" link text pointing to ../editor/features/copy-paste-figma.md at the
occurrences referenced) with universal routing URLs of the form
https://grida.co/_/<path>; specifically update any ../editor/... links
(including the one at line 42 and the one at line 73) to use
https://grida.co/_/editor/features/copy-paste-figma.md (and the corresponding
editor paths) so all user-facing editor doc links use the global
https://grida.co/_/... routing.
- Line 21: The French docs page contains external markdown links (the phrase
with "signaler un probleme" pointing to
https://github.com/gridaco/grida/issues/new in the sentence starting
"L'integration presse-papiers..." and another link at the later occurrence
around line 74); replace these markdown links with either an internal relative
/docs link if an equivalent doc exists, or convert the external URL to inline
code (e.g., `https://github.com/gridaco/grida/issues/new`) to comply with the
rule "Never link outside /docs" in markdown files; update both the sentence
containing "L'integration presse-papiers avec Figma..." and the other occurrence
at line ~74 accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6638e91a-7f46-45cf-b06e-e309ab55f7bb
📒 Files selected for processing (19)
apps/docs/docusaurus.config.tsdocs/editor/shortcuts/translations/fr/index.mddocs/editor/shortcuts/translations/meta.jsondocs/forms/translations/fr/respondent-email-notifications.mddocs/forms/translations/meta.jsondocs/platform/customers/translations/fr/index.mddocs/platform/customers/translations/meta.jsondocs/platform/tags/translations/fr/index.mddocs/platform/tags/translations/meta.jsondocs/platform/translations/fr/index.mddocs/platform/translations/meta.jsondocs/translations/fr/index.mddocs/translations/meta.jsondocs/with-figma/guides/translations/fr/how-to-get-fig-file.mddocs/with-figma/guides/translations/fr/how-to-get-personal-access-token.mddocs/with-figma/guides/translations/fr/how-to-get-sharable-design-link.mddocs/with-figma/guides/translations/meta.jsondocs/with-figma/translations/fr/index.mddocs/with-figma/translations/meta.json
✅ Files skipped from review due to trivial changes (4)
- docs/platform/customers/translations/meta.json
- docs/translations/meta.json
- docs/with-figma/guides/translations/fr/how-to-get-personal-access-token.md
- docs/platform/tags/translations/fr/index.md
🚧 Files skipped from review as they are similar to previous changes (6)
- docs/forms/translations/meta.json
- docs/platform/tags/translations/meta.json
- docs/editor/shortcuts/translations/meta.json
- docs/with-figma/guides/translations/meta.json
- docs/with-figma/translations/meta.json
- apps/docs/docusaurus.config.ts
| - update | ||
| --- | ||
|
|
||
| ### Notifications email aux repondants |
There was a problem hiding this comment.
Fix heading level structure.
The document starts with an h3 (###) heading, which violates markdown best practices. Headings should increment one level at a time. Since Docusaurus uses the frontmatter title as the h1, the first content heading should be h2 (##).
📝 Proposed fix for heading structure
-### Notifications email aux repondants
+## Notifications email aux répondantsApply the same change to all other h3 headings throughout the document (lines 25, 34, 43, 54, 61, 87), promoting them to h2 (##).
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 15-15: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/forms/translations/fr/respondent-email-notifications.md` at line 15, The
document uses h3 headings where the first content heading must be h2; change the
heading "### Notifications email aux repondants" to "## Notifications email aux
repondants" and similarly promote all other occurrences of "###" headings in
this file (the headings at the other noted locations: the lines containing the
same pattern headings after this one) to "##" so the top-level content headings
follow from the frontmatter title; update each "###" to "##" consistently across
the file.
Comment on lines
+138
to
+140
| ### Mise a jour (instable) | ||
|
|
||
| Pour faire un upsert, vous devez fournir le champ `uid` ou `uuid` dans le fichier CSV. |
There was a problem hiding this comment.
Use “mise à jour” here, not “upsert”.
Line 105 says CSV upsert is not supported, but this section says “Pour faire un upsert”. That contradiction can mislead users; this should describe update matching by uid or uuid.
Proposed wording fix
-### Mise a jour (instable)
+### Mise a jour (instable)
-Pour faire un upsert, vous devez fournir le champ `uid` ou `uuid` dans le fichier CSV.
+Pour faire une mise a jour, vous devez fournir le champ `uid` ou `uuid` dans le fichier CSV.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/platform/customers/translations/fr/index.md` around lines 138 - 140,
Change the heading and text that currently say "upsert" to explicitly say "mise
à jour" and clarify this section describes updating existing customers by
matching the `uid` or `uuid` field in the CSV; update the heading "Mise a jour
(instable)" and the sentence "Pour faire un upsert, vous devez fournir le champ
`uid` ou `uuid` dans le fichier CSV." to wording that states updates are
performed by matching `uid` or `uuid` (e.g., "Pour mettre à jour des
enregistrements, fournissez le champ `uid` ou `uuid` dans le fichier CSV") so it
no longer contradicts the earlier line that says CSV upsert is not supported.
Comment on lines
+1
to
+10
| --- | ||
| title: Grida Platform | ||
| description: Documentation de plateforme pour les clients Grida, les tags et les fonctionnalites produit associees. | ||
| keywords: | ||
| - grida | ||
| - platform | ||
| - customers | ||
| - tags | ||
| format: md | ||
| --- |
There was a problem hiding this comment.
Add doc_tasks to the publishable translated page.
This new Platform page has SEO metadata but is missing the taxonomy field used elsewhere in the PR. Consider marking it for follow-up, e.g. enhance, if this is an initial translation pass.
Proposed frontmatter update
keywords:
- grida
- platform
- customers
- tags
+doc_tasks:
+ - enhance
format: mdAs per coding guidelines, docs/**/*.md: “Use doc_tasks frontmatter field with allowed values (enhance, update, translate) to track follow-up work on publishable docs”.
📝 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.
Suggested change
| --- | |
| title: Grida Platform | |
| description: Documentation de plateforme pour les clients Grida, les tags et les fonctionnalites produit associees. | |
| keywords: | |
| - grida | |
| - platform | |
| - customers | |
| - tags | |
| format: md | |
| --- | |
| --- | |
| title: Grida Platform | |
| description: Documentation de plateforme pour les clients Grida, les tags et les fonctionnalites produit associees. | |
| keywords: | |
| - grida | |
| - platform | |
| - customers | |
| - tags | |
| doc_tasks: | |
| - enhance | |
| format: md | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/platform/translations/fr/index.md` around lines 1 - 10, The frontmatter
in the translated page is missing the required taxonomy field `doc_tasks`;
update the top YAML block in docs/platform/translations/fr/index.md to include a
`doc_tasks` entry (choose one of the allowed values: `enhance`, `update`, or
`translate`) — e.g., add `doc_tasks: translate` to mark this as a translation
follow-up — so that the page conforms to the docs/**/*.md guideline and can be
tracked for subsequent work.
Comment on lines
+1
to
+14
| --- | ||
| id: intro | ||
| title: Documentation Grida | ||
| description: Guides produit, workflows Figma, docs Forms, docs Platform et références techniques pour Grida. | ||
| keywords: | ||
| - grida | ||
| - documentation | ||
| - canvas editor | ||
| - forms | ||
| - figma | ||
| - assistant | ||
| - platform | ||
| format: md | ||
| --- |
There was a problem hiding this comment.
Add required doc_tasks frontmatter for this publishable doc.
doc_tasks is missing in frontmatter (Line 1-14). Please add an allowed value, likely translate for this page.
Suggested patch
---
id: intro
title: Documentation Grida
description: Guides produit, workflows Figma, docs Forms, docs Platform et références techniques pour Grida.
+doc_tasks:
+ - translate
keywords:
- grida
- documentation
- canvas editorAs per coding guidelines: "Use doc_tasks frontmatter field with allowed values (enhance, update, translate) to track follow-up work on publishable docs".
📝 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.
Suggested change
| --- | |
| id: intro | |
| title: Documentation Grida | |
| description: Guides produit, workflows Figma, docs Forms, docs Platform et références techniques pour Grida. | |
| keywords: | |
| - grida | |
| - documentation | |
| - canvas editor | |
| - forms | |
| - figma | |
| - assistant | |
| - platform | |
| format: md | |
| --- | |
| --- | |
| id: intro | |
| title: Documentation Grida | |
| description: Guides produit, workflows Figma, docs Forms, docs Platform et références techniques pour Grida. | |
| doc_tasks: | |
| - translate | |
| keywords: | |
| - grida | |
| - documentation | |
| - canvas editor | |
| - forms | |
| - figma | |
| - assistant | |
| - platform | |
| format: md | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/translations/fr/index.md` around lines 1 - 14, The frontmatter for the
publishable doc (id: intro, title: Documentation Grida) is missing the required
doc_tasks field; add a doc_tasks entry with an allowed value (e.g., doc_tasks:
translate) to the YAML frontmatter so the page includes one of the permitted
task tags (enhance, update, translate) for follow-up tracking.
Comment on lines
+53
to
+55
| - [Repository](https://github.com/gridaco/grida) | ||
| - [Website](https://grida.co) | ||
| - [Slack](https://grida.co/join-slack) |
There was a problem hiding this comment.
Replace external markdown links with inline code references.
Lines 53-55 link outside /docs using markdown links, which violates docs-linking policy.
Suggested patch
-## Liens du projet
-
-- [Repository](https://github.com/gridaco/grida)
-- [Website](https://grida.co)
-- [Slack](https://grida.co/join-slack)
+## Liens du projet
+
+- Repository: `https://github.com/gridaco/grida`
+- Website: `https://grida.co`
+- Slack: `https://grida.co/join-slack`As per coding guidelines: "Never link outside /docs from docs markdown files; use relative links within /docs and reference external paths as inline code instead".
📝 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.
Suggested change
| - [Repository](https://github.com/gridaco/grida) | |
| - [Website](https://grida.co) | |
| - [Slack](https://grida.co/join-slack) | |
| - Repository: `https://github.com/gridaco/grida` | |
| - Website: `https://grida.co` | |
| - Slack: `https://grida.co/join-slack` |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/translations/fr/index.md` around lines 53 - 55, Replace the three
external markdown links ("Repository", "Website", "Slack") with inline code
references instead of linking outside /docs: remove the markdown link syntax for
each item and render the external URL or path as inline code (e.g.,
`https://github.com/gridaco/grida`, `https://grida.co`,
`https://grida.co/join-slack`) or, if there are equivalent docs pages, change
them to relative /docs links; update the list lines that currently contain
"Repository", "Website", and "Slack" accordingly so no markdown link points
outside /docs.
|
|
||
| - [Figma Help: Save a local copy of files](https://help.figma.com/hc/en-us/articles/8403626871063-Save-a-local-copy-of-files) | ||
| - [Figma Help: Download files from Figma](https://help.figma.com/hc/en-us/articles/360041003114-Download-files-from-Figma) | ||
| - [Copy & Paste from Figma](../../editor/features/copy-paste-figma.md) - methode alternative d'import via le presse-papiers |
There was a problem hiding this comment.
Use universal routing for the editor-page link.
Line 111 should use the universal https://grida.co/_/<path> form for user-facing editor docs links. The current deep relative path is also fragile from this nested translation directory.
Proposed change
-- [Copy & Paste from Figma](../../editor/features/copy-paste-figma.md) - methode alternative d'import via le presse-papiers
+- [Copy & Paste from Figma](https://grida.co/_/with-figma/editor/features/copy-paste-figma) - methode alternative d'import via le presse-papiers🧰 Tools
🪛 LanguageTool
[typographical] ~111-~111: Ce signe est un trait d’union, il ne sert qu’à former des mots composés. Employez un tiret ou un autre signe de ponctuation plus approprié.
Context: ...s-from-Figma) - Copy & Paste from Figma - methode alternative d'import via le presse-papi...
(TIRET)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/with-figma/guides/translations/fr/how-to-get-fig-file.md` at line 111,
Replace the fragile relative editor link "[Copy & Paste from Figma]
(../../editor/features/copy-paste-figma.md)" with the universal routing URL
form; update the link target to
"https://grida.co/_/editor/features/copy-paste-figma" so the editor-page link
uses the global tenant-agnostic route instead of the deep relative path.
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (7)
docs/platform/translations/fr/index.md (1)
1-10:⚠️ Potential issue | 🟡 MinorAdd
doc_tasksin frontmatter for this initial translation page.This page is publishable but appears part of the initial translation pass; add a follow-up task marker for tracking.
As per coding guidelines, `docs/**/*.{md,mdx}`: “Use `doc_tasks` frontmatter field when a publishable page still needs follow-up work such as `enhance`, `update`, or `translate`.”Proposed patch
--- title: Plateforme Grida description: Documentation de plateforme pour les clients Grida, les tags et les fonctionnalités produit associées. keywords: - grida - platform - customers - tags +doc_tasks: + - enhance format: md ---🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/platform/translations/fr/index.md` around lines 1 - 10, The frontmatter in the translation file is missing the required doc_tasks field; update the YAML frontmatter block (the leading --- section in this file) to include a doc_tasks entry such as doc_tasks: ["translate"] or ["translate","enhance"] so the page is tracked for follow-up; ensure you add it alongside title/description/keywords without changing other fields and maintain valid YAML formatting.docs/platform/customers/translations/fr/index.md (2)
50-51:⚠️ Potential issue | 🟡 MinorReplace external Markdown links with inline URL code references.
Docs pages should not use clickable links outside
/docs; keep these URLs as inline code instead.As per coding guidelines, `docs/**/*.{md,mdx}`: “Never link outside `/docs` from markdown files; use inline code references instead.”Proposed patch
-`phone` est le numéro de téléphone du client au format E.164. Si vous ne savez pas comment formater correctement le numéro, vous pouvez utiliser -l'[outil Grida E.164](https://grida.co/tools/e164). +`phone` est le numéro de téléphone du client au format E.164. Si vous ne savez pas comment formater correctement le numéro, vous pouvez utiliser +l'outil Grida E.164 (`https://grida.co/tools/e164`). ... -**Important** : Les tags ne peuvent pas être mis à jour via un fichier CSV. [Contactez le support](https://grida.co/contact) pour plus d'informations. +**Important** : Les tags ne peuvent pas être mis à jour via un fichier CSV. Contactez le support (`https://grida.co/contact`) pour plus d'informations.Also applies to: 155-155
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/platform/customers/translations/fr/index.md` around lines 50 - 51, Replace the external Markdown link `[outil Grida E.164](https://grida.co/tools/e164)` with an inline code-style URL reference (e.g., wrap the URL in backticks) so the docs page does not contain a clickable external link; update the sentence that mentions `phone` to include the URL as inline code rather than a Markdown link.
138-140:⚠️ Potential issue | 🟡 MinorFix contradiction: “upsert” wording in update section conflicts with earlier rule.
Line 105 states CSV upsert is unsupported, but this section still instructs “faire un upsert.” Reword this section to describe CSV update-by-identifier only.
Based on learnings, “Ship minimally meaningful docs that help users complete a task or understand a feature, even if they still need screenshots, examples, or polish.”Proposed patch
### Mise à jour (instable) -Pour faire un upsert, vous devez fournir le champ `uid` ou `uuid` dans le fichier CSV. +Pour mettre à jour des enregistrements, vous devez fournir le champ `uid` ou `uuid` dans le fichier CSV.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/platform/customers/translations/fr/index.md` around lines 138 - 140, The French doc section titled "### Mise à jour (instable)" incorrectly refers to doing an "upsert" and contradicts the earlier rule that CSV upsert is unsupported; change the wording to make it clear this is an update-by-identifier only (e.g., "Mise à jour par identifiant (instable)"), remove the word "upsert", and state that you must provide the `uid` or `uuid` in the CSV to update existing records (not to create new ones).docs/with-figma/guides/translations/fr/how-to-get-fig-file.md (1)
111-111:⚠️ Potential issue | 🟡 MinorUse universal routing for the editor link.
Line 111 still uses a deep relative editor-doc link; this is fragile in localized docs and should use the universal
/_/route.Proposed fix
-- [Copy & Paste from Figma](../../editor/features/copy-paste-figma.md) - méthode alternative d'import via le presse-papiers +- [Copy & Paste from Figma](https://grida.co/_/with-figma/editor/features/copy-paste-figma) - méthode alternative d'import via le presse-papiersAs per coding guidelines: "In user-facing docs, prefer universal routing links using
https://grida.co/_/<path>format instead of tenant-specific canonical paths for editor page instructions".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/with-figma/guides/translations/fr/how-to-get-fig-file.md` at line 111, Replace the fragile deep relative markdown link for "Copy & Paste from Figma" with the universal routing URL format; locate the markdown link text "Copy & Paste from Figma" and change the href from "../../editor/features/copy-paste-figma.md" to the universal route "https://grida.co/_/editor/features/copy-paste-figma.md" (or the equivalent "/_/editor/features/copy-paste-figma.md" if you prefer relative-to-site roots) so the editor documentation link uses the tenant‑agnostic /_/ route.docs/forms/translations/fr/respondent-email-notifications.md (1)
15-15:⚠️ Potential issue | 🟡 MinorFix heading level structure (already flagged in previous review).
The first content heading and all subsequent top-level headings use h3 (
###) instead of h2 (##). Since Docusaurus uses the frontmattertitleas h1, all main content headings should be h2.This issue was flagged in a previous review but remains unaddressed. Apply the fix to all main headings at lines 15, 25, 34, 43, 54, 61, and 87.
📝 Proposed fix for all heading levels
-### Notifications email aux répondants +## Notifications email aux répondants -### Avant de commencer (CIAM / email vérifié) +## Avant de commencer (CIAM / email vérifié) -### Comment activer les notifications email aux répondants +## Comment activer les notifications email aux répondants -### Comment personnaliser l'email +## Comment personnaliser l'email -### Ce qui est envoyé (vue d'ensemble) +## Ce qui est envoyé (vue d'ensemble) -### Templates (variables Handlebars) +## Templates (variables Handlebars) -### Dépannage +## Dépannage🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/forms/translations/fr/respondent-email-notifications.md` at line 15, Change all top-level content headings in this document from h3 (###) to h2 (##); specifically update the heading "Notifications email aux répondants" and the other main content headings that were previously flagged so that every primary section uses ## (since frontmatter supplies the h1). Ensure you replace every occurrence of "### " for those main section titles with "## " and leave nested/subsection headings untouched.docs/translations/fr/index.md (2)
1-14:⚠️ Potential issue | 🟠 MajorAdd required
doc_tasksfrontmatter for this translation.The frontmatter is missing the
doc_tasksfield. For a French translation landing page, this should includetranslateto track ongoing translation maintenance.📋 Suggested addition to frontmatter
--- id: intro title: Documentation Grida description: Guides produit, workflows Figma, docs Forms, docs Platform et références techniques pour Grida. +doc_tasks: + - translate keywords: - gridaAs per coding guidelines: Use
doc_tasksfrontmatter field when a publishable page still needs follow-up work such astranslate.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/translations/fr/index.md` around lines 1 - 14, The frontmatter for the French translation page (id: intro, title: Documentation Grida) is missing the required doc_tasks metadata; add a doc_tasks field to the YAML frontmatter containing the translate task (e.g., doc_tasks: [translate]) so the page is tracked for translation maintenance and follows the project's frontmatter conventions.
53-55:⚠️ Potential issue | 🟠 MajorReplace external markdown links with inline code references.
Lines 53-55 use markdown link syntax for external URLs, which violates the docs linking policy. These should be rendered as inline code references instead.
🔗 Proposed fix to use inline code references
## Liens du projet -- [Repository](https://github.com/gridaco/grida) -- [Website](https://grida.co) -- [Slack](https://grida.co/join-slack) +- Repository: `https://github.com/gridaco/grida` +- Website: `https://grida.co` +- Slack: `https://grida.co/join-slack`As per coding guidelines: Never link outside
/docsfrom markdown files; use inline code references instead since only/docs/**is deployed on Docusaurus.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/translations/fr/index.md` around lines 53 - 55, Replace the external markdown links on the three list items for "Repository", "Website" and "Slack" with inline code references (no external hyperlinking) so the docs stop linking outside /docs; locate the list entries containing "[Repository](https://github.com/gridaco/grida)", "[Website](https://grida.co)" and "[Slack](https://grida.co/join-slack)" in docs/translations/fr/index.md and convert them to inline code form (e.g., use backticks to show the label and/or URL as code text) instead of markdown link syntax.
🧹 Nitpick comments (1)
docs/forms/translations/fr/respondent-email-notifications.md (1)
45-45: Consider using proper arrow symbols for better French typography.The navigation path uses ASCII arrows (
->), but French typography conventions prefer proper arrow symbols (→). This would improve the typographical quality of the documentation.✨ Proposed typography improvement
-1. Ouvrez [**Connect -> Channels**](https://grida.co/_/connect/channels) -> **Email Notifications** (même écran que ci-dessus). +1. Ouvrez [**Connect → Channels**](https://grida.co/_/connect/channels) → **Email Notifications** (même écran que ci-dessus).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/forms/translations/fr/respondent-email-notifications.md` at line 45, Replace ASCII arrows in the navigation path text ("Connect -> Channels" and "-> **Email Notifications**") with proper typographic arrows (→) so the line reads "Connect → Channels → **Email Notifications**"; update the single line in docs/forms/translations/fr/respondent-email-notifications.md that contains "Connect -> Channels -> **Email Notifications**" accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/with-figma/translations/fr/index.md`:
- Line 42: Update the editor-doc links that currently point to a tenant-specific
relative path to use the universal /_/ route format: replace the link target
"../editor/features/copy-paste-figma.md" (anchor text "Copy & Paste from Figma")
with the universal URL using the /_/ prefix, e.g.
"https://grida.co/_/editor/features/copy-paste-figma.md"; do the same for the
other editor link referenced around the same file (the one noted at lines 73) so
both user-facing docs use the https://grida.co/_/... format.
---
Duplicate comments:
In `@docs/forms/translations/fr/respondent-email-notifications.md`:
- Line 15: Change all top-level content headings in this document from h3 (###)
to h2 (##); specifically update the heading "Notifications email aux répondants"
and the other main content headings that were previously flagged so that every
primary section uses ## (since frontmatter supplies the h1). Ensure you replace
every occurrence of "### " for those main section titles with "## " and leave
nested/subsection headings untouched.
In `@docs/platform/customers/translations/fr/index.md`:
- Around line 50-51: Replace the external Markdown link `[outil Grida
E.164](https://grida.co/tools/e164)` with an inline code-style URL reference
(e.g., wrap the URL in backticks) so the docs page does not contain a clickable
external link; update the sentence that mentions `phone` to include the URL as
inline code rather than a Markdown link.
- Around line 138-140: The French doc section titled "### Mise à jour
(instable)" incorrectly refers to doing an "upsert" and contradicts the earlier
rule that CSV upsert is unsupported; change the wording to make it clear this is
an update-by-identifier only (e.g., "Mise à jour par identifiant (instable)"),
remove the word "upsert", and state that you must provide the `uid` or `uuid` in
the CSV to update existing records (not to create new ones).
In `@docs/platform/translations/fr/index.md`:
- Around line 1-10: The frontmatter in the translation file is missing the
required doc_tasks field; update the YAML frontmatter block (the leading ---
section in this file) to include a doc_tasks entry such as doc_tasks:
["translate"] or ["translate","enhance"] so the page is tracked for follow-up;
ensure you add it alongside title/description/keywords without changing other
fields and maintain valid YAML formatting.
In `@docs/translations/fr/index.md`:
- Around line 1-14: The frontmatter for the French translation page (id: intro,
title: Documentation Grida) is missing the required doc_tasks metadata; add a
doc_tasks field to the YAML frontmatter containing the translate task (e.g.,
doc_tasks: [translate]) so the page is tracked for translation maintenance and
follows the project's frontmatter conventions.
- Around line 53-55: Replace the external markdown links on the three list items
for "Repository", "Website" and "Slack" with inline code references (no external
hyperlinking) so the docs stop linking outside /docs; locate the list entries
containing "[Repository](https://github.com/gridaco/grida)",
"[Website](https://grida.co)" and "[Slack](https://grida.co/join-slack)" in
docs/translations/fr/index.md and convert them to inline code form (e.g., use
backticks to show the label and/or URL as code text) instead of markdown link
syntax.
In `@docs/with-figma/guides/translations/fr/how-to-get-fig-file.md`:
- Line 111: Replace the fragile deep relative markdown link for "Copy & Paste
from Figma" with the universal routing URL format; locate the markdown link text
"Copy & Paste from Figma" and change the href from
"../../editor/features/copy-paste-figma.md" to the universal route
"https://grida.co/_/editor/features/copy-paste-figma.md" (or the equivalent
"/_/editor/features/copy-paste-figma.md" if you prefer relative-to-site roots)
so the editor documentation link uses the tenant‑agnostic /_/ route.
---
Nitpick comments:
In `@docs/forms/translations/fr/respondent-email-notifications.md`:
- Line 45: Replace ASCII arrows in the navigation path text ("Connect ->
Channels" and "-> **Email Notifications**") with proper typographic arrows (→)
so the line reads "Connect → Channels → **Email Notifications**"; update the
single line in docs/forms/translations/fr/respondent-email-notifications.md that
contains "Connect -> Channels -> **Email Notifications**" accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: cf75ad17-690b-4d79-87b1-353c9db7360d
📒 Files selected for processing (11)
apps/docs/CONTRIBUTING.mddocs/editor/shortcuts/translations/fr/index.mddocs/forms/translations/fr/respondent-email-notifications.mddocs/platform/customers/translations/fr/index.mddocs/platform/tags/translations/fr/index.mddocs/platform/translations/fr/index.mddocs/translations/fr/index.mddocs/with-figma/guides/translations/fr/how-to-get-fig-file.mddocs/with-figma/guides/translations/fr/how-to-get-personal-access-token.mddocs/with-figma/guides/translations/fr/how-to-get-sharable-design-link.mddocs/with-figma/translations/fr/index.md
✅ Files skipped from review due to trivial changes (1)
- docs/with-figma/guides/translations/fr/how-to-get-personal-access-token.md
🚧 Files skipped from review as they are similar to previous changes (1)
- apps/docs/CONTRIBUTING.md
| - les données vectorielles et les paths | ||
| - les relations entre composants | ||
|
|
||
| **En savoir plus** : [Copy & Paste from Figma](../editor/features/copy-paste-figma.md) |
There was a problem hiding this comment.
Switch editor-doc links to universal /_/ routes.
Both editor links should use the universal route format for user-facing docs.
Proposed fix
- **En savoir plus** : [Copy & Paste from Figma](../editor/features/copy-paste-figma.md)
+ **En savoir plus** : [Copy & Paste from Figma](https://grida.co/_/with-figma/editor/features/copy-paste-figma)
...
- - [Figma Import Technical Spec](../editor/features/copy-paste-figma.md)
+ - [Figma Import Technical Spec](https://grida.co/_/with-figma/editor/features/copy-paste-figma)As per coding guidelines: "In user-facing docs, prefer universal routing links using https://grida.co/_/<path> format instead of tenant-specific canonical paths for editor page instructions".
Also applies to: 73-73
🧰 Tools
🪛 LanguageTool
[typographical] ~42-~42: Pas de correspondance fermante ou ouvrante pour le caractère « ] »
Context: ... entre composants En savoir plus : [Copy & Paste from Figma](../editor/featu...
(UNPAIRED_BRACKETS)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/with-figma/translations/fr/index.md` at line 42, Update the editor-doc
links that currently point to a tenant-specific relative path to use the
universal /_/ route format: replace the link target
"../editor/features/copy-paste-figma.md" (anchor text "Copy & Paste from Figma")
with the universal URL using the /_/ prefix, e.g.
"https://grida.co/_/editor/features/copy-paste-figma.md"; do the same for the
other editor link referenced around the same file (the one noted at lines 73) so
both user-facing docs use the https://grida.co/_/... format.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
draft,unlisted, anddoc_tasksen => ko, ja, fr)Included docs work
docs/AGENTS.md,apps/docs/CONTRIBUTING.md, andapps/docs/README.mddraft: trueonly for non-meaningful docs, reserveunlisted: truefor intentionally non-discoverable docs, and usedoc_tasksfor follow-up work on publishable docs/docs/**are the source of truth and translations flowen => ko, ja, frko,ja, andfrtranslations for:Validation
pnpm content:setupandpnpm buildinapps/docsen,ko,ja, andfrNotes
doc_tasksto track follow-up enhancement, update, or translation workSummary by CodeRabbit