docs: Docusaurus tags for WG and reference (RAG)#599
Conversation
Define docs/tags.yml with audience (internal vs user-facing), product domains (canvas, typography, platform, etc.), and activity types (reference, research). Add frontmatter tags to all docs under wg/ and reference/ for RAG chunking and tag pages. Set format: md on previously unfronted reference and SVG testing pages to preserve MDX safety. Co-authored-by: Universe <universe@grida.co>
Rename Docusaurus tag keys for terser RAG facets: working-group→wg, infrastructure→infra, internationalization→icu. Update labels and permalinks in tags.yml and all affected frontmatter. Co-authored-by: Universe <universe@grida.co>
|
Cursor Agent can help with this pull request. Just |
WalkthroughThis PR introduces a centralized tag vocabulary for documentation and applies tags to 60+ markdown files across the docs directory. A new Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/wg/index.md (1)
1-9:⚠️ Potential issue | 🟡 MinorFrontmatter is missing
format: md.Please add
format: mdin this WG page frontmatter to avoid unnecessary MDX parsing.As per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/index.md` around lines 1 - 9, The frontmatter at the top of the WG page (the block containing id, title, tags) is missing the format key; add a line `format: md` to that frontmatter block so the file opts out of MDX parsing—update the frontmatter near the existing id: intro and title: "Working Group" entries to include format: md.
🟡 Minor comments (22)
docs/wg/feat-editor/ux-surface/selection.md-1-7 (1)
1-7:⚠️ Potential issue | 🟡 MinorAdd
format: mdto the new frontmatter block.This document appears Markdown-only; please set
format: mdin the frontmatter.Suggested patch
--- title: Selection +format: md tags: - internal - wg - editor ---As per coding guidelines, "
docs/{wg,reference}/**/*.{md,mdx}: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by addingformat: mdto the frontmatter".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-editor/ux-surface/selection.md` around lines 1 - 7, The frontmatter for the "Selection" document is missing the MDX opt-out; update the YAML frontmatter block (the initial --- block that contains title: Selection and tags:) to include format: md so the document is parsed as plain Markdown (add a line like format: md within that frontmatter block).docs/reference/index.md-2-6 (1)
2-6:⚠️ Potential issue | 🟡 MinorAdd
format: mdto opt out of MDX parsing.This page appears to be plain Markdown, but frontmatter still lacks
format: md. Please add it while editing frontmatter in this PR.Suggested patch
--- id: intro +format: md tags: - reference - user-facing ---As per coding guidelines, "
docs/{wg,reference}/**/*.{md,mdx}: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by addingformat: mdto the frontmatter".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/reference/index.md` around lines 2 - 6, The frontmatter for this doc (the block containing id: intro and tags:) is missing the required opt-out key; add format: md to that frontmatter block so the top-of-file frontmatter includes format: md (ensure it sits alongside id: intro and tags: in the same YAML/frontmatter section).docs/wg/platform/_history/vercel-domain-configuration-snapshot-pre-byod.md-2-10 (1)
2-10:⚠️ Potential issue | 🟡 MinorPlease add
format: mdin this historical WG page.This document is plain Markdown and should explicitly opt out of MDX parsing.
Suggested patch
--- title: Vercel domain configuration snapshot (pre-BYOD) +format: md status: historical unlisted: true tags: - internal - platform - infra - historicalAs per coding guidelines, "
docs/{wg,reference}/**/*.{md,mdx}: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by addingformat: mdto the frontmatter".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/platform/_history/vercel-domain-configuration-snapshot-pre-byod.md` around lines 2 - 10, This historical WG Markdown file's frontmatter is missing the explicit MDX opt-out; update the YAML frontmatter at the top of the document (the block containing title: "Vercel domain configuration snapshot (pre-BYOD)", status: historical, unlisted: true, tags: ...) to include the key format: md so the file is treated as plain Markdown rather than MDX.docs/wg/feat-paragraph/impl-font-fallback.md-2-9 (1)
2-9:⚠️ Potential issue | 🟡 MinorPlease include
format: mdin frontmatter.This file reads as Markdown-only and should opt out of MDX parsing.
Suggested patch
--- title: Font Fallback Strategy (font-fallback) +format: md tags: - internal - wg - typography - text - fontsAs per coding guidelines, "
docs/{wg,reference}/**/*.{md,mdx}: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by addingformat: mdto the frontmatter".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-paragraph/impl-font-fallback.md` around lines 2 - 9, Add "format: md" to the YAML frontmatter at the top of the document (alongside the existing title and tags) so the file opts out of MDX parsing; update the frontmatter block in impl-font-fallback.md to include format: md before the body content.docs/wg/feat-schema/naming-conventions.md-2-7 (1)
2-7:⚠️ Potential issue | 🟡 MinorFrontmatter is missing
format: md.Since this page is not using MDX/JSX features, add
format: mdto keep parsing deterministic.Suggested patch
--- title: Grida document schema naming conventions +format: md tags: - internal - wg - format-schemaAs per coding guidelines, "
docs/{wg,reference}/**/*.{md,mdx}: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by addingformat: mdto the frontmatter".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-schema/naming-conventions.md` around lines 2 - 7, The frontmatter in the document (keys: title and tags) is missing the required "format: md" entry; update the frontmatter at the top of the file (near the title/tags block) to include format: md so the file opts out of MDX parsing and parses deterministically.docs/wg/feat-vector-network/index.md-2-9 (1)
2-9:⚠️ Potential issue | 🟡 MinorFrontmatter should include
format: md.This WG doc is Markdown-only and should explicitly opt out of MDX parsing.
Suggested patch
--- title: Vector Network Implementation +format: md tags: - internal - wg - canvas - vector - editorAs per coding guidelines, "
docs/{wg,reference}/**/*.{md,mdx}: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by addingformat: mdto the frontmatter".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-vector-network/index.md` around lines 2 - 9, The frontmatter for the "Vector Network Implementation" doc is missing the MDX opt-out; update the frontmatter block at the top of the file (the YAML block containing title: Vector Network Implementation and tags:) to include format: md so the document is parsed as plain Markdown (i.e., add a top-level format: md key in the existing frontmatter).docs/wg/feat-2d/stroke-fill-opacity.md-1-8 (1)
1-8:⚠️ Potential issue | 🟡 MinorMissing
format: mdin WG doc frontmatter.Line 1-8 should include
format: mdsince this is a non-MDX document.As per coding guidelines: "`docs/{wg,reference}/**/*.{md,mdx}`: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding `format: md` to the frontmatter".Suggested patch
--- title: "Stroke-Fill Opacity Compositing" +format: md tags: - internal - wg🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-2d/stroke-fill-opacity.md` around lines 1 - 8, The YAML frontmatter at the top of the document (keys like title and tags) is missing the required "format: md" entry; update the frontmatter for the Stroke-Fill Opacity Compositing doc by adding format: md alongside the existing keys so this non-MDX file opts out of MDX parsing.docs/wg/research/chromium/tiling-and-rasterization.md-1-9 (1)
1-9:⚠️ Potential issue | 🟡 MinorFrontmatter should include
format: md.Line 1-9 is missing
format: md, which is expected for markdown-only docs underdocs/wg/**.As per coding guidelines: "`docs/{wg,reference}/**/*.{md,mdx}`: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding `format: md` to the frontmatter".Suggested patch
--- title: "Chromium Tiling and Rasterization" +format: md tags: - internal - research🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/research/chromium/tiling-and-rasterization.md` around lines 1 - 9, The frontmatter for the document with title "Chromium Tiling and Rasterization" is missing the required `format: md` key; update the YAML frontmatter at the top of the file (the block containing title/tags) to include `format: md` so this markdown-only doc under docs/wg/** opts out of MDX parsing.docs/wg/feat-resources/index.md-1-10 (1)
1-10:⚠️ Potential issue | 🟡 MinorAdd
format: mdto avoid MDX parsing ambiguity.Line 1-10 frontmatter is missing
format: md. This file is markdown-only and includes angle-bracket literals, so it should explicitly opt out of MDX parsing.As per coding guidelines: "`docs/{wg,reference}/**/*.{md,mdx}`: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding `format: md` to the frontmatter".Suggested patch
--- title: Resource Management (resources) +format: md tags: - internal - wg🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-resources/index.md` around lines 1 - 10, The frontmatter block (containing keys like title and tags) in the document is missing the format directive; add a top-level "format: md" entry to the YAML frontmatter so the file explicitly opts out of MDX parsing (i.e., update the existing frontmatter that includes title: Resource Management (resources) and tags: ... to include format: md).docs/wg/feat-paragraph/index.md-1-9 (1)
1-9:⚠️ Potential issue | 🟡 MinorAdd
format: mdfor this non-MDX WG page.Line 1-9 frontmatter should explicitly set
format: mdto match the docs parsing policy.As per coding guidelines: "`docs/{wg,reference}/**/*.{md,mdx}`: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding `format: md` to the frontmatter".Suggested patch
--- title: Paragraph Feature Roadmap +format: md tags: - internal - wg🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-paragraph/index.md` around lines 1 - 9, The frontmatter for the document titled "Paragraph Feature Roadmap" is missing an explicit format opt-out; update the YAML frontmatter (the block containing title: Paragraph Feature Roadmap and tags:) by adding the key "format: md" so the file opts out of MDX parsing per the docs policy.docs/wg/feat-painting/stroke-rect.md-1-9 (1)
1-9:⚠️ Potential issue | 🟡 MinorPlease add
format: mdin frontmatter.Line 1-9 currently adds tags but still omits
format: mdfor this non-MDX WG doc.As per coding guidelines: "`docs/{wg,reference}/**/*.{md,mdx}`: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding `format: md` to the frontmatter".Suggested patch
--- title: Rectangular Stroke Model (stroke-rect) +format: md tags: - internal - wg🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-painting/stroke-rect.md` around lines 1 - 9, The frontmatter for the WG doc (title: Rectangular Stroke Model) is missing the MD opt-out; add a line `format: md` to the existing YAML frontmatter block (near the top alongside title and tags) so the file uses plain Markdown parsing instead of MDX.docs/wg/feat-text-editing/attributed-text.md-1-11 (1)
1-11:⚠️ Potential issue | 🟡 MinorPlease add
format: mdto this markdown-only WG doc.Current frontmatter includes tags but not the MDX opt-out field.
As per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-text-editing/attributed-text.md` around lines 1 - 11, This WG doc's YAML frontmatter (see id: attributed-text and title: "Attributed Text: Data Model Specification") is missing the MDX opt-out; add the key "format: md" to the frontmatter block (alongside tags) so the file opts out of MDX parsing for markdown-only content.docs/wg/feat-text-editing/index.md-1-11 (1)
1-11:⚠️ Potential issue | 🟡 MinorFrontmatter should include
format: md.Please add
format: mdto this WG markdown document.As per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-text-editing/index.md` around lines 1 - 11, The frontmatter for the WG doc (id: feat-text-editing, title: "Text Editing: Manifesto") is missing the format marker; update the YAML frontmatter by adding the line format: md so the document opts out of MDX parsing (add it alongside the existing id/title/tags fields in the top-level frontmatter block).docs/wg/feat-editor/index.md-1-8 (1)
1-8:⚠️ Potential issue | 🟡 MinorAdd
format: mdin frontmatter.This WG page appears markdown-only; please include
format: mdalongside the new tags.As per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-editor/index.md` around lines 1 - 8, The frontmatter block at the top of the document is missing the format key; add a line `format: md` inside the existing YAML frontmatter (alongside title and tags) so the file opts out of MDX parsing; update the frontmatter section that currently contains title and tags to include format: md.docs/wg/feat-ai/tools-image.md-1-8 (1)
1-8:⚠️ Potential issue | 🟡 MinorAdd
format: mdto opt out of MDX parsing.This WG doc appears Markdown-only, but the frontmatter is missing
format: md.Suggested frontmatter patch
--- title: Image Tools (for AI) +format: md tags: - internal - wg - ai - editor ---As per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-ai/tools-image.md` around lines 1 - 8, The frontmatter for the doc with title "Image Tools (for AI)" is missing the opt-out flag for MDX; update the YAML frontmatter at the top of the file (the block containing title/tags) to include format: md so the file is treated as plain Markdown (i.e., add a format: md entry alongside title and tags in the existing frontmatter).docs/wg/research/chromium/glossary.md-1-10 (1)
1-10:⚠️ Potential issue | 🟡 MinorAdd
format: mdto the frontmatter.For this WG markdown doc, include
format: mdwith the new tags.As per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/research/chromium/glossary.md` around lines 1 - 10, The frontmatter at the top of the "Chromium Compositor — Glossary" doc lacks the opt-out field for MDX; add a new field `format: md` into the existing YAML frontmatter block (the same area containing title and tags) so the file explicitly opts out of MDX parsing and keeps the rest of the frontmatter (title: "Chromium Compositor — Glossary", tags) unchanged.docs/wg/feat-masks/index.md-3-8 (1)
3-8:⚠️ Potential issue | 🟡 MinorFrontmatter is missing
format: md.
Since this file is markdown-only, addformat: mdalongside the new tags.Suggested patch
--- title: Masking Model (masks) +format: md tags: - internal - wg - canvasAs per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-masks/index.md` around lines 3 - 8, The frontmatter in the markdown-only docs/wg/feat-masks index is missing the required "format: md" key; update the top YAML frontmatter block (where tags: - internal - wg - canvas - masks - rendering are declared) to include format: md alongside the tags so the file opts out of MDX parsing.docs/wg/feat-2d/optimization.md-3-8 (1)
3-8:⚠️ Potential issue | 🟡 MinorPlease include
format: mdin this WG doc frontmatter.
At Line 3, tag additions are good, but the non-MDX page should explicitly opt out.Suggested patch
--- title: Rendering Optimization Strategies +format: md tags: - internal - wg - canvasAs per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-2d/optimization.md` around lines 3 - 8, The document's YAML frontmatter is missing an explicit MDX opt-out; add the key "format: md" into the frontmatter block (the same YAML section that contains the "tags:" entry) so the non-MDX page explicitly opts out of MDX parsing—insert "format: md" alongside the existing tags in the frontmatter.docs/wg/feat-painting/fe-noise.md-3-8 (1)
3-8:⚠️ Potential issue | 🟡 MinorAdd
format: mdto this WG doc frontmatter.
At Line 3, tags were added, but the file should explicitly opt out of MDX parsing.Suggested patch
--- title: Noise Effects (fe-noise) +format: md tags: - internal - wgAs per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-painting/fe-noise.md` around lines 3 - 8, The frontmatter in this WG doc contains only tags and is missing the explicit MD opt-out; edit the YAML frontmatter (where "tags:" and the list are defined) to add the key "format: md" (above or alongside the existing tags) so the file opts out of MDX parsing and is treated as plain Markdown.docs/wg/feat-2d/investigation-viewport-culling.md-5-10 (1)
5-10:⚠️ Potential issue | 🟡 MinorMissing
format: mdin frontmatter.
At Line 5, the tag update is fine, but this non-MDX WG doc should declareformat: md.Suggested patch
--- title: "Investigation: Viewport Culling & Camera Caching" status: rejected date: 2026-03-22 +format: md tags: - internalAs per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-2d/investigation-viewport-culling.md` around lines 5 - 10, The frontmatter in this WG doc is missing the required opt-out for MDX parsing; update the YAML frontmatter block (the existing tags: - internal - wg - canvas - performance - rendering) to include the entry format: md so the file explicitly opts out of MDX parsing (i.e., add a top-level format: md key in the frontmatter).docs/wg/feat-css/glossary/css_properties.json5.md-4-8 (1)
4-8:⚠️ Potential issue | 🟡 MinorAdd
format: mdin frontmatter for MDX opt-out.
At Line 4, tags were added butformat: mdis still missing for this non-MDX page.Suggested patch
--- title: "css_properties.json5" description: "Chromium Blink's single source of truth for CSS property metadata, used as a reference for browser-grade CSS cascade implementation" +format: md tags: - internal - wg - cssAs per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-css/glossary/css_properties.json5.md` around lines 4 - 8, The frontmatter for docs/wg/feat-css/glossary/css_properties.json5.md is missing the MDX opt-out; add a "format: md" field to the top-level frontmatter (alongside the existing "tags" entry) so this non-MDX page is parsed as plain Markdown—ensure "format: md" appears before or with the tags block in the file header.docs/wg/feat-fig/index.md-4-8 (1)
4-8:⚠️ Potential issue | 🟡 MinorPlease add
format: mdto this frontmatter block.
At Line 4, tags were added, but the page should also opt out of MDX parsing.Suggested patch
--- title: "Figma Import & Translation (io-figma)" description: Implementation details behind importing .fig files into Grida. +format: md tags: - internal - wgAs per coding guidelines: “For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter”.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-fig/index.md` around lines 4 - 8, The frontmatter block that currently contains the tags entry (the block starting with "tags:" and the listed - internal, - wg, - figma, - import) needs to opt out of MDX parsing; add a new key "format: md" to that same frontmatter block (above or alongside the existing tags) so the page is treated as plain Markdown rather than MDX.
🧹 Nitpick comments (13)
docs/wg/feat-editor/ux-surface/index.md (1)
1-8: Consider addingformat: mdfor consistency.📝 Suggested addition
--- title: UX Surface (WG) +format: md tags: - internal - wg - editorAs per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}without JSX features should includeformat: md.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-editor/ux-surface/index.md` around lines 1 - 8, The frontmatter in the markdown file (the YAML block at top of docs/wg/feat-editor/ux-surface/index.md) is missing the required key "format: md"; add format: md inside the top frontmatter block (alongside title and tags) so the file follows the docs/{wg,reference}/**/*.{md,mdx} guideline for non-JSX markdown files.docs/wg/research/chromium/index.md (1)
1-10: Consider addingformat: mdfor consistency.📝 Suggested addition
--- title: "Chromium Compositor Research" +format: md tags: - internal - research - chromium - rendering - compositingAs per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}without JSX features should includeformat: md.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/research/chromium/index.md` around lines 1 - 10, Add "format: md" to the existing YAML frontmatter block (the same block containing title: "Chromium Compositor Research" and tags:) so the document explicitly declares Markdown format; update the frontmatter by inserting the format key (format: md) near the top of that frontmatter to satisfy the docs/{wg,reference} guideline for non-JSX files.docs/wg/feat-fontgen/index.md (1)
1-9: Consider addingformat: mdfor consistency.This file uses only standard markdown features, so adding
format: mdwould align with the coding guidelines.📝 Suggested addition
--- title: Font Generation (fontgen) +format: md tags: - internal - wg - typography - fontsAs per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}without JSX features should includeformat: md.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-fontgen/index.md` around lines 1 - 9, The frontmatter is missing the required format marker; update the YAML frontmatter by adding the key `format: md` alongside existing keys such as `title: Font Generation (fontgen)` and `tags:` so the top matter becomes consistent with the docs guideline for non-JSX markdown files.docs/wg/feat-fig/glossary/fig.kiwi.md (1)
1-9: Consider addingformat: mdfor consistency.This technical document contains many code blocks and tables but no JSX features. Adding
format: mdwould provide an extra safety layer.📝 Suggested addition
--- title: Kiwi Schema for .fig Format +format: md tags: - internal - wg - figma - format-schema ---As per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}without JSX features should includeformat: md.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-fig/glossary/fig.kiwi.md` around lines 1 - 9, The frontmatter of the document (title: "Kiwi Schema for .fig Format") lacks the recommended "format: md" key; update the YAML frontmatter at the top of docs/wg/feat-fig/glossary/fig.kiwi.md by adding format: md to the existing block so the file is explicitly treated as Markdown (confirm there are no JSX features present in the body), preserving existing tags and other frontmatter keys.docs/wg/feat-text-editing/impl-performance.md (1)
1-11: Consider addingformat: mdfor consistency.This file contains no JSX/MDX features, so opting out of MDX parsing would improve consistency with the coding guidelines and provide an extra safety layer.
📝 Suggested addition
--- id: impl-performance title: "Text Editing: Performance Model" +format: md tags: - internal - wg - typography - text - performanceAs per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}that don't use JSX/MDX features should opt out of MDX parsing by addingformat: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-text-editing/impl-performance.md` around lines 1 - 11, Add "format: md" to the YAML frontmatter of the document with id: impl-performance (title: "Text Editing: Performance Model") so the file opts out of MDX parsing; update the frontmatter block at the top of the file to include the key "format: md" directly under the existing metadata to ensure the doc is treated as plain Markdown.docs/wg/feat-authoring/parametric-scaling.md (1)
1-9: Consider addingformat: mdfor consistency.This document uses LaTeX math notation and contains complex tables but no JSX features. Adding
format: mdwould ensure safe parsing.📝 Suggested addition
--- title: Scale tool (K) — parameter-space scaling (A.k.a Apply Scale or K-Scale) +format: md tags: - internal - wg - editor - authoringAs per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}without JSX features should includeformat: md.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-authoring/parametric-scaling.md` around lines 1 - 9, This markdown document's frontmatter is missing the explicit format declaration; update the YAML frontmatter (near the existing "title: Scale tool (K) — parameter-space scaling (A.k.a Apply Scale or K-Scale)" entry) to include the key "format: md" so the file is parsed as plain Markdown (no JSX) per the docs guideline for files under docs/{wg,reference}/**/*.{md,mdx}; ensure you add "format: md" at the top-level of the frontmatter block.docs/wg/feat-authoring/index.md (1)
1-9: Consider addingformat: mdfor consistency.📝 Suggested addition
--- title: Authoring (WG) +format: md tags: - internal - wg - editor - authoringAs per coding guidelines: files under
docs/{wg,reference}/**/*.{md,mdx}without JSX features should includeformat: md.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-authoring/index.md` around lines 1 - 9, The frontmatter for the "Authoring (WG)" document is missing the required format field; update the frontmatter block at the top of the file (the YAML section containing title: "Authoring (WG)" and tags:) to include format: md so the file follows the docs/{wg,reference} guideline for non-JSX Markdown files.docs/wg/feat-text-editing/richtext-persistency.md (1)
1-11: Consider addingformat: mdto the frontmatter.This comprehensive research document doesn't use JSX/MDX features. Adding
format: mdwould opt out of MDX parsing for better performance and safety.📄 Suggested frontmatter addition
--- id: richtext-persistency title: "Rich Text Persistency: Research & Comparative Reference" +format: md tags: - internal - wg - typography - text - editor ---As per coding guidelines: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-text-editing/richtext-persistency.md` around lines 1 - 11, The frontmatter for the "richtext-persistency" doc lacks an explicit format setting; update the YAML frontmatter block that contains id/title/tags in the doc to include format: md so the file opts out of MDX parsing (add the format: md key alongside id, title, and tags in the existing frontmatter).docs/wg/feat-paragraph/impl-opsz-auto.md (1)
1-10: Consider addingformat: mdto the frontmatter.This optical sizing documentation uses standard Markdown without JSX/MDX features. Adding
format: mdwould be beneficial.📄 Suggested frontmatter addition
--- title: Optical Size Automation (opsz-auto) +format: md tags: - internal - wg - typography - text - fonts ---As per coding guidelines: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-paragraph/impl-opsz-auto.md` around lines 1 - 10, The frontmatter block for "Optical Size Automation (opsz-auto)" lacks a format declaration; add the key-value pair format: md to the YAML frontmatter at the top of the file (the same block containing title/tags) so the Markdown is opted out of MDX parsing; update the existing frontmatter rather than creating a new block to ensure parsers pick up format: md alongside title and tags.docs/wg/feat-paragraph/impl-italic.md (1)
1-10: Consider addingformat: mdto the frontmatter.This comprehensive italic implementation documentation uses standard Markdown features (including Mermaid diagrams, which work with
format: md) without JSX/MDX. Addingformat: mdwould be beneficial.📄 Suggested frontmatter addition
--- title: Italic and Oblique Strategy (italic) +format: md tags: - internal - wg - typography - text - fonts ---As per coding guidelines: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-paragraph/impl-italic.md` around lines 1 - 10, Add "format: md" to the document frontmatter to opt out of MDX parsing; update the YAML block at the top (the existing frontmatter containing title/tags) to include a new line "format: md" so the file is parsed strictly as Markdown (e.g., directly beneath the title or tags entry in the existing frontmatter).docs/wg/platform/multi-tenant-custom-domain-vercel.md (1)
1-9: Consider addingformat: mdto the frontmatter.This platform documentation uses standard Markdown without JSX/MDX features. Adding
format: mdwould opt out of MDX parsing.📄 Suggested frontmatter addition
--- title: Multi-tenant Custom Domains on Vercel +format: md tags: - internal - wg - platform - infra ---As per coding guidelines: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/platform/multi-tenant-custom-domain-vercel.md` around lines 1 - 9, The frontmatter block for the document titled "Multi-tenant Custom Domains on Vercel" is missing the MDX opt-out; update the YAML frontmatter (the top --- block) to include the key "format: md" so the file is treated as plain Markdown rather than MDX, ensuring the existing title and tags remain unchanged.docs/wg/feat-2d/curve-decoration.md (1)
1-10: Consider addingformat: mdto the frontmatter.This document uses standard Markdown features (math notation, code blocks, tables) without JSX/MDX. Adding
format: mdwould be beneficial.📄 Suggested frontmatter addition
--- title: Curve Decorations (2D) +format: md tags: - internal - wg - canvas - vector - rendering ---As per coding guidelines: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/feat-2d/curve-decoration.md` around lines 1 - 10, Add the YAML frontmatter key "format: md" to this document's existing frontmatter (the block containing "title: Curve Decorations (2D)" and "tags: ...") so the file opts out of MDX parsing; insert the single line format: md within that top-level frontmatter block so standard Markdown features (math, code blocks, tables) are parsed as plain Markdown.docs/wg/research/chromium/render-surfaces.md (1)
1-10: Consider addingformat: mdto the frontmatter.Since this document doesn't use JSX or MDX features, adding
format: mdwould opt out of MDX parsing, which can improve performance and avoid potential parsing edge cases.📄 Suggested frontmatter addition
--- title: "Chromium Render Surfaces" +format: md tags: - internal - research - chromium - compositing - rendering ---As per coding guidelines: For documentation files that don't use JSX/MDX features, opt out of MDX parsing by adding
format: mdto the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/wg/research/chromium/render-surfaces.md` around lines 1 - 10, Add the frontmatter key "format: md" to the existing YAML frontmatter block (the same block containing title: "Chromium Render Surfaces" and tags) so the document opts out of MDX parsing; update the top YAML to include format: md on its own line under the existing keys to improve performance and avoid MDX parsing edge cases.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@docs/wg/index.md`:
- Around line 1-9: The frontmatter at the top of the WG page (the block
containing id, title, tags) is missing the format key; add a line `format: md`
to that frontmatter block so the file opts out of MDX parsing—update the
frontmatter near the existing id: intro and title: "Working Group" entries to
include format: md.
---
Minor comments:
In `@docs/reference/index.md`:
- Around line 2-6: The frontmatter for this doc (the block containing id: intro
and tags:) is missing the required opt-out key; add format: md to that
frontmatter block so the top-of-file frontmatter includes format: md (ensure it
sits alongside id: intro and tags: in the same YAML/frontmatter section).
In `@docs/wg/feat-2d/investigation-viewport-culling.md`:
- Around line 5-10: The frontmatter in this WG doc is missing the required
opt-out for MDX parsing; update the YAML frontmatter block (the existing tags: -
internal - wg - canvas - performance - rendering) to include the entry format:
md so the file explicitly opts out of MDX parsing (i.e., add a top-level format:
md key in the frontmatter).
In `@docs/wg/feat-2d/optimization.md`:
- Around line 3-8: The document's YAML frontmatter is missing an explicit MDX
opt-out; add the key "format: md" into the frontmatter block (the same YAML
section that contains the "tags:" entry) so the non-MDX page explicitly opts out
of MDX parsing—insert "format: md" alongside the existing tags in the
frontmatter.
In `@docs/wg/feat-2d/stroke-fill-opacity.md`:
- Around line 1-8: The YAML frontmatter at the top of the document (keys like
title and tags) is missing the required "format: md" entry; update the
frontmatter for the Stroke-Fill Opacity Compositing doc by adding format: md
alongside the existing keys so this non-MDX file opts out of MDX parsing.
In `@docs/wg/feat-ai/tools-image.md`:
- Around line 1-8: The frontmatter for the doc with title "Image Tools (for AI)"
is missing the opt-out flag for MDX; update the YAML frontmatter at the top of
the file (the block containing title/tags) to include format: md so the file is
treated as plain Markdown (i.e., add a format: md entry alongside title and tags
in the existing frontmatter).
In `@docs/wg/feat-css/glossary/css_properties.json5.md`:
- Around line 4-8: The frontmatter for
docs/wg/feat-css/glossary/css_properties.json5.md is missing the MDX opt-out;
add a "format: md" field to the top-level frontmatter (alongside the existing
"tags" entry) so this non-MDX page is parsed as plain Markdown—ensure "format:
md" appears before or with the tags block in the file header.
In `@docs/wg/feat-editor/index.md`:
- Around line 1-8: The frontmatter block at the top of the document is missing
the format key; add a line `format: md` inside the existing YAML frontmatter
(alongside title and tags) so the file opts out of MDX parsing; update the
frontmatter section that currently contains title and tags to include format:
md.
In `@docs/wg/feat-editor/ux-surface/selection.md`:
- Around line 1-7: The frontmatter for the "Selection" document is missing the
MDX opt-out; update the YAML frontmatter block (the initial --- block that
contains title: Selection and tags:) to include format: md so the document is
parsed as plain Markdown (add a line like format: md within that frontmatter
block).
In `@docs/wg/feat-fig/index.md`:
- Around line 4-8: The frontmatter block that currently contains the tags entry
(the block starting with "tags:" and the listed - internal, - wg, - figma, -
import) needs to opt out of MDX parsing; add a new key "format: md" to that same
frontmatter block (above or alongside the existing tags) so the page is treated
as plain Markdown rather than MDX.
In `@docs/wg/feat-masks/index.md`:
- Around line 3-8: The frontmatter in the markdown-only docs/wg/feat-masks index
is missing the required "format: md" key; update the top YAML frontmatter block
(where tags: - internal - wg - canvas - masks - rendering are declared) to
include format: md alongside the tags so the file opts out of MDX parsing.
In `@docs/wg/feat-painting/fe-noise.md`:
- Around line 3-8: The frontmatter in this WG doc contains only tags and is
missing the explicit MD opt-out; edit the YAML frontmatter (where "tags:" and
the list are defined) to add the key "format: md" (above or alongside the
existing tags) so the file opts out of MDX parsing and is treated as plain
Markdown.
In `@docs/wg/feat-painting/stroke-rect.md`:
- Around line 1-9: The frontmatter for the WG doc (title: Rectangular Stroke
Model) is missing the MD opt-out; add a line `format: md` to the existing YAML
frontmatter block (near the top alongside title and tags) so the file uses plain
Markdown parsing instead of MDX.
In `@docs/wg/feat-paragraph/impl-font-fallback.md`:
- Around line 2-9: Add "format: md" to the YAML frontmatter at the top of the
document (alongside the existing title and tags) so the file opts out of MDX
parsing; update the frontmatter block in impl-font-fallback.md to include
format: md before the body content.
In `@docs/wg/feat-paragraph/index.md`:
- Around line 1-9: The frontmatter for the document titled "Paragraph Feature
Roadmap" is missing an explicit format opt-out; update the YAML frontmatter (the
block containing title: Paragraph Feature Roadmap and tags:) by adding the key
"format: md" so the file opts out of MDX parsing per the docs policy.
In `@docs/wg/feat-resources/index.md`:
- Around line 1-10: The frontmatter block (containing keys like title and tags)
in the document is missing the format directive; add a top-level "format: md"
entry to the YAML frontmatter so the file explicitly opts out of MDX parsing
(i.e., update the existing frontmatter that includes title: Resource Management
(resources) and tags: ... to include format: md).
In `@docs/wg/feat-schema/naming-conventions.md`:
- Around line 2-7: The frontmatter in the document (keys: title and tags) is
missing the required "format: md" entry; update the frontmatter at the top of
the file (near the title/tags block) to include format: md so the file opts out
of MDX parsing and parses deterministically.
In `@docs/wg/feat-text-editing/attributed-text.md`:
- Around line 1-11: This WG doc's YAML frontmatter (see id: attributed-text and
title: "Attributed Text: Data Model Specification") is missing the MDX opt-out;
add the key "format: md" to the frontmatter block (alongside tags) so the file
opts out of MDX parsing for markdown-only content.
In `@docs/wg/feat-text-editing/index.md`:
- Around line 1-11: The frontmatter for the WG doc (id: feat-text-editing,
title: "Text Editing: Manifesto") is missing the format marker; update the YAML
frontmatter by adding the line format: md so the document opts out of MDX
parsing (add it alongside the existing id/title/tags fields in the top-level
frontmatter block).
In `@docs/wg/feat-vector-network/index.md`:
- Around line 2-9: The frontmatter for the "Vector Network Implementation" doc
is missing the MDX opt-out; update the frontmatter block at the top of the file
(the YAML block containing title: Vector Network Implementation and tags:) to
include format: md so the document is parsed as plain Markdown (i.e., add a
top-level format: md key in the existing frontmatter).
In `@docs/wg/platform/_history/vercel-domain-configuration-snapshot-pre-byod.md`:
- Around line 2-10: This historical WG Markdown file's frontmatter is missing
the explicit MDX opt-out; update the YAML frontmatter at the top of the document
(the block containing title: "Vercel domain configuration snapshot (pre-BYOD)",
status: historical, unlisted: true, tags: ...) to include the key format: md so
the file is treated as plain Markdown rather than MDX.
In `@docs/wg/research/chromium/glossary.md`:
- Around line 1-10: The frontmatter at the top of the "Chromium Compositor —
Glossary" doc lacks the opt-out field for MDX; add a new field `format: md` into
the existing YAML frontmatter block (the same area containing title and tags) so
the file explicitly opts out of MDX parsing and keeps the rest of the
frontmatter (title: "Chromium Compositor — Glossary", tags) unchanged.
In `@docs/wg/research/chromium/tiling-and-rasterization.md`:
- Around line 1-9: The frontmatter for the document with title "Chromium Tiling
and Rasterization" is missing the required `format: md` key; update the YAML
frontmatter at the top of the file (the block containing title/tags) to include
`format: md` so this markdown-only doc under docs/wg/** opts out of MDX parsing.
---
Nitpick comments:
In `@docs/wg/feat-2d/curve-decoration.md`:
- Around line 1-10: Add the YAML frontmatter key "format: md" to this document's
existing frontmatter (the block containing "title: Curve Decorations (2D)" and
"tags: ...") so the file opts out of MDX parsing; insert the single line format:
md within that top-level frontmatter block so standard Markdown features (math,
code blocks, tables) are parsed as plain Markdown.
In `@docs/wg/feat-authoring/index.md`:
- Around line 1-9: The frontmatter for the "Authoring (WG)" document is missing
the required format field; update the frontmatter block at the top of the file
(the YAML section containing title: "Authoring (WG)" and tags:) to include
format: md so the file follows the docs/{wg,reference} guideline for non-JSX
Markdown files.
In `@docs/wg/feat-authoring/parametric-scaling.md`:
- Around line 1-9: This markdown document's frontmatter is missing the explicit
format declaration; update the YAML frontmatter (near the existing "title: Scale
tool (K) — parameter-space scaling (A.k.a Apply Scale or K-Scale)" entry) to
include the key "format: md" so the file is parsed as plain Markdown (no JSX)
per the docs guideline for files under docs/{wg,reference}/**/*.{md,mdx}; ensure
you add "format: md" at the top-level of the frontmatter block.
In `@docs/wg/feat-editor/ux-surface/index.md`:
- Around line 1-8: The frontmatter in the markdown file (the YAML block at top
of docs/wg/feat-editor/ux-surface/index.md) is missing the required key "format:
md"; add format: md inside the top frontmatter block (alongside title and tags)
so the file follows the docs/{wg,reference}/**/*.{md,mdx} guideline for non-JSX
markdown files.
In `@docs/wg/feat-fig/glossary/fig.kiwi.md`:
- Around line 1-9: The frontmatter of the document (title: "Kiwi Schema for .fig
Format") lacks the recommended "format: md" key; update the YAML frontmatter at
the top of docs/wg/feat-fig/glossary/fig.kiwi.md by adding format: md to the
existing block so the file is explicitly treated as Markdown (confirm there are
no JSX features present in the body), preserving existing tags and other
frontmatter keys.
In `@docs/wg/feat-fontgen/index.md`:
- Around line 1-9: The frontmatter is missing the required format marker; update
the YAML frontmatter by adding the key `format: md` alongside existing keys such
as `title: Font Generation (fontgen)` and `tags:` so the top matter becomes
consistent with the docs guideline for non-JSX markdown files.
In `@docs/wg/feat-paragraph/impl-italic.md`:
- Around line 1-10: Add "format: md" to the document frontmatter to opt out of
MDX parsing; update the YAML block at the top (the existing frontmatter
containing title/tags) to include a new line "format: md" so the file is parsed
strictly as Markdown (e.g., directly beneath the title or tags entry in the
existing frontmatter).
In `@docs/wg/feat-paragraph/impl-opsz-auto.md`:
- Around line 1-10: The frontmatter block for "Optical Size Automation
(opsz-auto)" lacks a format declaration; add the key-value pair format: md to
the YAML frontmatter at the top of the file (the same block containing
title/tags) so the Markdown is opted out of MDX parsing; update the existing
frontmatter rather than creating a new block to ensure parsers pick up format:
md alongside title and tags.
In `@docs/wg/feat-text-editing/impl-performance.md`:
- Around line 1-11: Add "format: md" to the YAML frontmatter of the document
with id: impl-performance (title: "Text Editing: Performance Model") so the file
opts out of MDX parsing; update the frontmatter block at the top of the file to
include the key "format: md" directly under the existing metadata to ensure the
doc is treated as plain Markdown.
In `@docs/wg/feat-text-editing/richtext-persistency.md`:
- Around line 1-11: The frontmatter for the "richtext-persistency" doc lacks an
explicit format setting; update the YAML frontmatter block that contains
id/title/tags in the doc to include format: md so the file opts out of MDX
parsing (add the format: md key alongside id, title, and tags in the existing
frontmatter).
In `@docs/wg/platform/multi-tenant-custom-domain-vercel.md`:
- Around line 1-9: The frontmatter block for the document titled "Multi-tenant
Custom Domains on Vercel" is missing the MDX opt-out; update the YAML
frontmatter (the top --- block) to include the key "format: md" so the file is
treated as plain Markdown rather than MDX, ensuring the existing title and tags
remain unchanged.
In `@docs/wg/research/chromium/index.md`:
- Around line 1-10: Add "format: md" to the existing YAML frontmatter block (the
same block containing title: "Chromium Compositor Research" and tags:) so the
document explicitly declares Markdown format; update the frontmatter by
inserting the format key (format: md) near the top of that frontmatter to
satisfy the docs/{wg,reference} guideline for non-JSX files.
In `@docs/wg/research/chromium/render-surfaces.md`:
- Around line 1-10: Add the frontmatter key "format: md" to the existing YAML
frontmatter block (the same block containing title: "Chromium Render Surfaces"
and tags) so the document opts out of MDX parsing; update the top YAML to
include format: md on its own line under the existing keys to improve
performance and avoid MDX parsing edge cases.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 0b6af950-3a0e-4425-8fea-60a40df53179
📒 Files selected for processing (66)
docs/reference/index.mddocs/reference/italic-fonts.mddocs/reference/italic.mddocs/reference/open-type-features.mddocs/reference/open-type-script-tags.mddocs/reference/open-type-variable-axes.mddocs/tags.ymldocs/wg/feat-2d/curve-decoration.mddocs/wg/feat-2d/investigation-viewport-culling.mddocs/wg/feat-2d/optimization.mddocs/wg/feat-2d/stroke-fill-opacity.mddocs/wg/feat-ai/tools-image.mddocs/wg/feat-ai/tools.mddocs/wg/feat-authoring/index.mddocs/wg/feat-authoring/parametric-scaling.mddocs/wg/feat-crdt/id.mddocs/wg/feat-css/glossary/css_properties.json5.mddocs/wg/feat-editor/index.mddocs/wg/feat-editor/ux-surface/index.mddocs/wg/feat-editor/ux-surface/selection.mddocs/wg/feat-fig/glossary/fig.kiwi.mddocs/wg/feat-fig/index.mddocs/wg/feat-fontgen/index.mddocs/wg/feat-hash-nch/index.mddocs/wg/feat-icu-uct/index.mddocs/wg/feat-image-filters/index.mddocs/wg/feat-layout/index.mddocs/wg/feat-masks/index.mddocs/wg/feat-painting/fe-noise.mddocs/wg/feat-painting/stroke-rect.mddocs/wg/feat-paragraph/impl-emoji-placeholder.mddocs/wg/feat-paragraph/impl-font-fallback.mddocs/wg/feat-paragraph/impl-italic.mddocs/wg/feat-paragraph/impl-opsz-auto.mddocs/wg/feat-paragraph/index.mddocs/wg/feat-resources/index.mddocs/wg/feat-schema/naming-conventions.mddocs/wg/feat-svg/pattern.mddocs/wg/feat-svg/testing.mddocs/wg/feat-svg/text-import.mddocs/wg/feat-text-editing/attributed-text.mddocs/wg/feat-text-editing/impl-performance.mddocs/wg/feat-text-editing/index.mddocs/wg/feat-text-editing/richtext-persistency.mddocs/wg/feat-vector-network/index.mddocs/wg/index.mddocs/wg/platform/_history/vercel-domain-configuration-snapshot-pre-byod.mddocs/wg/platform/index.mddocs/wg/platform/multi-tenant-custom-domain-vercel.mddocs/wg/platform/universal-docs-routing.mddocs/wg/research/chromium/compositor-architecture.mddocs/wg/research/chromium/damage-tracking.mddocs/wg/research/chromium/effect-optimizations.mddocs/wg/research/chromium/glossary.mddocs/wg/research/chromium/index.mddocs/wg/research/chromium/interaction-and-quality.mddocs/wg/research/chromium/memory-and-priority.mddocs/wg/research/chromium/paint-recording.mddocs/wg/research/chromium/pinch-zoom-deep-dive.mddocs/wg/research/chromium/property-trees.mddocs/wg/research/chromium/render-surfaces.mddocs/wg/research/chromium/resolution-scaling-during-interaction.mddocs/wg/research/chromium/scheduler.mddocs/wg/research/chromium/svg-pattern.mddocs/wg/research/chromium/tiling-and-rasterization.mddocs/wg/research/chromium/tiling-deep-dive.md
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5f523134b3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| title: Universal Docs Routing (WG) | ||
| tags: | ||
| - internal | ||
| - user-facing |
There was a problem hiding this comment.
The new tags are explicitly meant to drive navigation/search/RAG, and this page is an internal working-group design note (Universal Docs Routing (WG)) under docs/wg/**. Adding user-facing means /tags/user-facing and any retrieval pipeline that uses that audience tag will now return an internal architecture doc alongside real end-user/reference content, which degrades the audience split this commit is introducing.
Useful? React with 👍 / 👎.
2 participants
Summary
Introduces Docusaurus doc tags for high-priority documentation under
docs/wg/**anddocs/reference/**.Changes
docs/tags.yml— Central tag registry with human-readable labels and short descriptions (audience: internal vs user-facing; domains: canvas, typography, platform, chromium research, etc.). Keys are reused in frontmatter for consistent filtering (site navigation, search, RAG).tags:list (3–6 tags typical). WG docs are taggedinternal+ domain;docs/reference/*usesuser-facing+reference+ typography/OpenType where appropriate.titleandformat: mdwhere needed so tables and angle-bracket content stay valid.Verification
pnpm buildinapps/docscompletes successfully (en + ko locales).Summary by CodeRabbit