docs: restructure docs IA and landing pages#668
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
WalkthroughThis PR updates Next.js from 16.1.6 to 16.2.4 and Docusaurus from 3.9.2 to 3.10.0 across multiple applications, reorganizes documentation structure by introducing new sidebar categories ("With Figma," "Design," "CLI") while removing older concept pages, marks archived documentation with Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
![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: e5f2ccdd0f
ℹ️ 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".
| ## 여기서 시작하세요 | ||
|
|
||
| ❤️ **오픈소스.** Grida 는 전세계 뛰어난 디자이너와 개발자가 함깨 만들어나가고 있습니다. 여러분도 참여하고 싶으신가요? 생각보다 쉽게 세상에 기여할수 있습니다. | ||
| - Grida 에디터 안에서 기능 문서나 작업 흐름 가이드를 찾고 있다면 [Editor](../../editor/features/README.md)를 보세요. |
There was a problem hiding this comment.
The new links in the Korean intro doc use ../../..., but translation files are copied to i18n/<locale>/docusaurus-plugin-content-docs/current/<same-path> (see copy-translations.js), so this page becomes .../current/index.md and those paths resolve outside the docs root (e.g. ../../editor/... resolves to i18n/ko/editor/...). As a result, the “Start here” and section links on the Korean landing page point to non-doc routes instead of localized docs pages.
Useful? React with 👍 / 👎.
Move blog's `onBrokenMarkdownLinks` into `markdown.hooks` (3.10 deprecation).
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/with-figma/index.md (1)
1-17:⚠️ Potential issue | 🟡 MinorAdd SEO frontmatter to this actively maintained page.
This page is being meaningfully edited but still starts directly with the H1. Please add
title,description, andkeywordsfrontmatter.Suggested frontmatter
+--- +title: Grida with Figma +description: Figma integration guides for Grida, including Assistant, import workflows, and supported Figma node behavior. +keywords: + - grida + - figma + - assistant + - figma import + - design assistant +format: md +--- + # Grida with FigmaAs per coding guidelines, actively maintained docs pages under
docs/with-figma/should usetitle,description, andkeywordsin frontmatter when meaningfully edited.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/with-figma/index.md` around lines 1 - 17, The page docs/with-figma/index.md is missing SEO frontmatter; add YAML frontmatter at the top of the file containing title, description, and keywords (e.g., title: "Grida with Figma", a concise description summarizing the page, and an array or comma-separated keywords like "Grida, Figma, design integration") so the actively maintained docs under with-figma include the required metadata; ensure the frontmatter appears before the existing H1 and uses the standard triple-dashed YAML block.apps/docs/manifest.js (1)
4-7:⚠️ Potential issue | 🟠 MajorRemove or retarget the stale Getting Started route.
This still advertises
/docs/getting-started, but this PR archives the legacy getting-started docs underdocs/_history. That leaves the manifest pointing at a no-longer-active docs surface.Suggested cleanup
- { - title: "Getting Started", - path: "/docs/getting-started", - },🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/manifest.js` around lines 4 - 7, Remove or retarget the stale manifest entry that references the archived docs: locate the route object with title "Getting Started" and path "/docs/getting-started" in apps/docs/manifest.js and either delete that object from the manifest array or update its path to the new archived location (e.g., "/docs/_history/getting-started" or another active landing page) so the manifest no longer points to a non-active docs surface.
🧹 Nitpick comments (2)
package.json (1)
48-48: Add pnpm overrides for@next/mdxand@next/third-partiesto align with thenextoverride.The root
pnpm.overridespinsnext@16.2.4, but workspace packages (editor, backgrounds) explicitly use@next/mdx@16.1.3and@next/third-parties@16.1.3. This minor version divergence can cause unexpected behavior. Add the following topnpm.overrides:"@next/mdx": "16.1.3", "@next/third-parties": "16.1.3"This ensures consistent versioning across the Next.js package family in the workspace.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 48, Add entries for "@next/mdx" and "@next/third-parties" to the pnpm.overrides in package.json so they are pinned to "16.1.3" to match workspace packages and avoid divergence from the root "next" override (currently "next": "16.2.4"); update the pnpm.overrides object to include these two keys mapping to "16.1.3".docs/AGENTS.md (1)
37-43: Clarify root archive vs nested_history/guidance.Line 43 says to archive new docs under
_history/, but Lines 70-75 still instruct agents to use_history/folders inside any docs subdirectory. Please distinguish rootdocs/_history/**for IA removals from nested_history/snapshots, or update the older convention to match.Proposed clarification
-- `docs/_history/**` contains archived, code-facing record material. It is not part of the user-facing docs surface; if you archive new docs, move them under `_history/` and mark each page `unlisted: true`. +- `docs/_history/**` contains archived, code-facing record material removed from the active docs IA. It is not part of the user-facing docs surface; if you archive docs from the top-level IA, move them under `docs/_history/` and mark each page `unlisted: true`.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/AGENTS.md` around lines 37 - 43, Clarify the `_history` guidance by distinguishing the root archive from nested snapshots: update the "Special Cases" section text that mentions `docs/_history/**` so it explicitly states that the root `docs/_history/**` is the canonical archive for information-architecture removals and archived pages (use `unlisted: true`), while any `_history/` folders inside subdirectories (e.g., inside topic folders) are local snapshot copies and must follow different rules (do not count as the global archive and should keep original ownership/sync rules); adjust the prose referencing `docs/cli/**` and `docs/@designto-code/**` as needed so they reference the new distinction and remove or reconcile the older instruction that treats nested `_history/` the same as the root archive.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/backgrounds/package.json`:
- Line 19: Update the `@next/third-parties` dependency to match the Next.js
version: change the pinned version of "@next/third-parties" from 16.1.3 to
16.2.2 (or later) so it aligns with "next": "16.2.4"; edit the package.json
dependency entry for "@next/third-parties" accordingly and run the lockfile
update (npm/yarn/pnpm install) to regenerate the lockfile and ensure
compatibility.
In `@apps/docs/sidebars.js`:
- Around line 245-255: The "CLI" top-level category in the sidebar (the object
with label "CLI" and dirName "cli") exposes deprecated docs; update the sidebar
entry to avoid promoting them by either removing that category from the
tutorialSidebar, renaming the label to "CLI (deprecated)", or moving the object
under a new legacy group (e.g., "Legacy" or "Deprecated") so docs/cli/** are not
shown as active top-level content; locate the category object that has type
"category", label "CLI", and dirName "cli" and apply one of these changes
consistently.
In `@docs/AGENTS.md`:
- Around line 115-130: In the Markdown table in docs/AGENTS.md, replace the two
occurrences of the bare "etc" with "etc." in the description cells for the
"working group" row ("working group documents, architecture documents, todo
list, etc") and the "together" row ("Contributing, Support, Community, etc");
ensure you only add the missing period and preserve existing spacing and
formatting for the table.
In `@editor/package.json`:
- Line 154: Update the pinned companion Next packages to match the main next
version: change the dependency versions for "@next/mdx" and
"@next/third-parties" from "16.1.3" to a 16.2.x release (e.g., "16.2.2") so they
align with "next": "16.2.4"; update package.json accordingly and run your
package manager (npm/yarn/pnpm) to refresh the lockfile and verify
compatibility.
---
Outside diff comments:
In `@apps/docs/manifest.js`:
- Around line 4-7: Remove or retarget the stale manifest entry that references
the archived docs: locate the route object with title "Getting Started" and path
"/docs/getting-started" in apps/docs/manifest.js and either delete that object
from the manifest array or update its path to the new archived location (e.g.,
"/docs/_history/getting-started" or another active landing page) so the manifest
no longer points to a non-active docs surface.
In `@docs/with-figma/index.md`:
- Around line 1-17: The page docs/with-figma/index.md is missing SEO
frontmatter; add YAML frontmatter at the top of the file containing title,
description, and keywords (e.g., title: "Grida with Figma", a concise
description summarizing the page, and an array or comma-separated keywords like
"Grida, Figma, design integration") so the actively maintained docs under
with-figma include the required metadata; ensure the frontmatter appears before
the existing H1 and uses the standard triple-dashed YAML block.
---
Nitpick comments:
In `@docs/AGENTS.md`:
- Around line 37-43: Clarify the `_history` guidance by distinguishing the root
archive from nested snapshots: update the "Special Cases" section text that
mentions `docs/_history/**` so it explicitly states that the root
`docs/_history/**` is the canonical archive for information-architecture
removals and archived pages (use `unlisted: true`), while any `_history/`
folders inside subdirectories (e.g., inside topic folders) are local snapshot
copies and must follow different rules (do not count as the global archive and
should keep original ownership/sync rules); adjust the prose referencing
`docs/cli/**` and `docs/@designto-code/**` as needed so they reference the new
distinction and remove or reconcile the older instruction that treats nested
`_history/` the same as the root archive.
In `@package.json`:
- Line 48: Add entries for "@next/mdx" and "@next/third-parties" to the
pnpm.overrides in package.json so they are pinned to "16.1.3" to match workspace
packages and avoid divergence from the root "next" override (currently "next":
"16.2.4"); update the pnpm.overrides object to include these two keys mapping to
"16.1.3".
🪄 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: 853da59f-c71b-4709-b164-7d831c369778
⛔ Files ignored due to path filters (8)
docs/_history/flags/assets/--artwork-flag-example-part-name-editing-only.gifis excluded by!**/*.gifdocs/_history/flags/assets/--h1-flag-example-part-name-editing-only.gifis excluded by!**/*.gifdocs/_history/getting-started/assets/how-to-configure-framework-on-assistant-v2021-11.pngis excluded by!**/*.pngdocs/_history/getting-started/assets/how-to-run-lints-on-your-design-with-grida-assistant-figma-plugin-15s.gifis excluded by!**/*.gifdocs/_history/getting-started/assets/how-to-run-lints-on-your-design-with-grida-assistant-figma-plugin-15s.movis excluded by!**/*.movdocs/design/vector-network/assets/vector-network-implicit-region.pngis excluded by!**/*.pngdocs/with-figma/assistant/assets/assistant-demo-2021.0.1.gifis excluded by!**/*.gifpnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (90)
apps/backgrounds/package.jsonapps/blog/docusaurus.config.tsapps/blog/package.jsonapps/docs/manifest.jsapps/docs/package.jsonapps/docs/scripts/docs-site-gen/copy-docs.jsapps/docs/sidebars.jsapps/viewer/package.jsondocs/AGENTS.mddocs/_history/flags/index.mddocs/_history/getting-started/01-intro.mdxdocs/_history/getting-started/02-clean-design-for-clean-code.mdxdocs/_history/getting-started/03-configuration.mdxdocs/_history/getting-started/04-integrations.mdxdocs/_history/getting-started/05-examples.mdxdocs/_history/getting-started/translations/ko/01-intro.mdxdocs/_history/getting-started/translations/ko/02-clean-design-for-clean-code.mdxdocs/_history/getting-started/translations/ko/03-configuration.mdxdocs/_history/getting-started/translations/ko/04-integrations.mdxdocs/_history/getting-started/translations/ko/05-examples.mdxdocs/_history/getting-started/translations/meta.jsondocs/code/with-css/index.mddocs/code/with-emotion-js/index.mddocs/code/with-expo/index.mddocs/code/with-flutter/index.mdxdocs/code/with-framer-motion/index.mddocs/code/with-headless-ui/index.mddocs/code/with-html/index.mddocs/code/with-jetpack-compose/index.mddocs/code/with-lit/index.mddocs/code/with-mui/index.mddocs/code/with-nextjs/index.mddocs/code/with-nuxtjs/index.mddocs/code/with-preact/index.mddocs/code/with-react-native/index.mddocs/code/with-react/index.mdxdocs/code/with-storybook/index.mddocs/code/with-styled-components/index.mddocs/code/with-svelte/index.mdxdocs/code/with-swiftui/index.mddocs/code/with-tailwindcss/index.mddocs/code/with-vanilla-web/index.mdxdocs/code/with-vue/index.mddocs/code/with-webcomponents/index.mddocs/concepts/01-what-is-scene.mdxdocs/concepts/02-design-linting.mdxdocs/concepts/03-layouts/01-laytout-management.mdxdocs/concepts/03-layouts/02-autolayout.mdxdocs/concepts/03-layouts/03-overflow-and-scrolling.mdxdocs/concepts/03-layouts/04-constraints.mdxdocs/concepts/03-layouts/05-best-practice.mdxdocs/concepts/03-layouts/_category_.jsondocs/concepts/04-components/03-component-management.mdxdocs/concepts/04-components/04-component-base.mdxdocs/concepts/04-components/05-component-variant.mdxdocs/concepts/04-components/_category_.jsondocs/concepts/05-widgets/01-intro.mdxdocs/concepts/05-widgets/_category_.jsondocs/concepts/05-widgets/detection.mdxdocs/concepts/06-motions/01-intro.mdxdocs/concepts/06-motions/_category_.jsondocs/concepts/07-prototyping/01-intro.mdxdocs/concepts/07-prototyping/02-using-figma-prototype.mdxdocs/concepts/07-prototyping/_category_.jsondocs/concepts/07-prototyping/prototype.mdxdocs/concepts/08-events-and-actions/01-intro.mdxdocs/concepts/08-events-and-actions/_category_.jsondocs/concepts/09-props/01-intro.mddocs/concepts/09-props/_category_.jsondocs/concepts/10-flags/01-intro.mddocs/concepts/10-flags/02-things-that-can-be-done-only-by-using-flags.mddocs/concepts/10-flags/03-flags-for-extending-layout.mddocs/concepts/10-flags/_category_.jsondocs/concepts/11-contents-management/_category_.jsondocs/concepts/11-contents-management/design-as-server.mdxdocs/concepts/11-contents-management/design-as-translations.mdxdocs/concepts/99-understand-bts/_category_.jsondocs/concepts/99-understand-bts/design-to-code.mdxdocs/concepts/_category_.jsondocs/concepts/handoff.mdxdocs/design/vector-network/index.mddocs/index.mddocs/tags.ymldocs/translations/ko/index.mddocs/with-figma/assistant/01-intro.mdxdocs/with-figma/assistant/design-assistant/icons-loader.mdxdocs/with-figma/assistant/design-assistant/index.mdxdocs/with-figma/index.mdeditor/package.jsonpackage.json
💤 Files with no reviewable changes (41)
- docs/concepts/11-contents-management/design-as-translations.mdx
- docs/code/with-tailwindcss/index.md
- docs/code/with-css/index.md
- docs/code/with-svelte/index.mdx
- docs/concepts/category.json
- docs/concepts/03-layouts/category.json
- docs/code/with-mui/index.md
- docs/concepts/09-props/category.json
- docs/concepts/handoff.mdx
- docs/code/with-lit/index.md
- docs/concepts/05-widgets/category.json
- docs/concepts/11-contents-management/category.json
- docs/code/with-vanilla-web/index.mdx
- docs/concepts/06-motions/category.json
- docs/concepts/10-flags/category.json
- docs/concepts/03-layouts/04-constraints.mdx
- docs/concepts/99-understand-bts/category.json
- docs/concepts/04-components/category.json
- docs/concepts/05-widgets/detection.mdx
- docs/concepts/07-prototyping/category.json
- docs/code/with-webcomponents/index.md
- docs/concepts/04-components/04-component-base.mdx
- docs/concepts/07-prototyping/prototype.mdx
- docs/concepts/99-understand-bts/design-to-code.mdx
- docs/concepts/05-widgets/01-intro.mdx
- docs/concepts/11-contents-management/design-as-server.mdx
- docs/concepts/04-components/03-component-management.mdx
- docs/concepts/04-components/05-component-variant.mdx
- docs/code/with-flutter/index.mdx
- docs/concepts/08-events-and-actions/category.json
- docs/concepts/10-flags/02-things-that-can-be-done-only-by-using-flags.md
- docs/concepts/03-layouts/05-best-practice.mdx
- docs/concepts/01-what-is-scene.mdx
- docs/concepts/03-layouts/02-autolayout.mdx
- docs/concepts/03-layouts/01-laytout-management.mdx
- docs/concepts/02-design-linting.mdx
- docs/code/with-react/index.mdx
- docs/code/with-html/index.md
- docs/concepts/03-layouts/03-overflow-and-scrolling.mdx
- docs/code/with-nextjs/index.md
- docs/concepts/10-flags/01-intro.md
| "clsx": "^2.1.1", | ||
| "motion": "^12.11.0", | ||
| "next": "16.1.6", | ||
| "next": "16.2.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
For Next.js 16.2.4 projects, is it supported to keep @next/third-partieson 16.1.3, or should@next/* packages match the Next.js patch version?
💡 Result:
No, it is not supported to keep @next/third-parties on 16.1.3 when using Next.js 16.2.4. All @next/* packages should match the Next.js version (same major.minor.patch where possible). @next/third-parties has a 16.2.2 release available that aligns with Next.js 16.2.4. Official docs recommend installing @next/third-parties@latest alongside next@latest, indicating version matching. The package is part of the Next.js monorepo, and mismatches can cause warnings or issues, as seen in similar cases with @next/swc. Peer dependencies are broad (^13+), but best practice is to use matching versions for compatibility, especially since patch releases include fixes.
Citations:
- 1: https://nextjs.org/docs/app/guides/third-party-libraries
- 2: https://nextjs.org/blog/next-16-2
- 3: https://registry.npmjs.org/%40next%2Fthird-parties
- 4: https://security.snyk.io/package/npm/%40next%2Fthird-parties/16.2.2
- 5: https://www.npmjs.com/package/@next/third-parties
- 6: https://nextjs.org/support-policy
- 7: https://nextjs.org/docs/messages/version-staleness
- 8: https://nextjs.org/docs/app/getting-started/installation
- 9: https://github.com/vercel/next.js/tree/HEAD/packages/third-parties
- 10: Unresolvable warnings on latest 15.x: "Mismatching @next/swc version" vercel/next.js#89251
- 11: @next/third-parties peerDependencies does not support Next 15 or React 19 RC vercel/next.js#71185
- 12: Cannot install @next/third-parties in Next.js 15 vercel/next.js#71602
Update @next/third-parties to match Next.js version.
@next/third-parties is pinned to 16.1.3, but next is now 16.2.4. These packages should align—update @next/third-parties to 16.2.2 or later to avoid compatibility issues.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/backgrounds/package.json` at line 19, Update the `@next/third-parties`
dependency to match the Next.js version: change the pinned version of
"@next/third-parties" from 16.1.3 to 16.2.2 (or later) so it aligns with "next":
"16.2.4"; edit the package.json dependency entry for "@next/third-parties"
accordingly and run the lockfile update (npm/yarn/pnpm install) to regenerate
the lockfile and ensure compatibility.
| { | ||
| type: "category", | ||
| label: "CLI", | ||
| collapsed: true, | ||
| items: [ | ||
| { | ||
| type: "autogenerated", | ||
| dirName: "cli", | ||
| }, | ||
| ], | ||
| }, |
There was a problem hiding this comment.
Avoid promoting deprecated CLI docs as a normal top-level category.
docs/AGENTS.md now marks docs/cli/** as deprecated/inactive, but this adds it to the primary user-facing sidebar without any deprecated labeling. Consider removing it from tutorialSidebar, moving it under a legacy grouping, or labeling it CLI (deprecated).
Possible low-friction fix
- label: "CLI",
+ label: "CLI (deprecated)",Based on learnings: Keep docs/cli/** deprecated docs unless a task explicitly removes or rewrites them.
📝 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.
| { | |
| type: "category", | |
| label: "CLI", | |
| collapsed: true, | |
| items: [ | |
| { | |
| type: "autogenerated", | |
| dirName: "cli", | |
| }, | |
| ], | |
| }, | |
| { | |
| type: "category", | |
| label: "CLI (deprecated)", | |
| collapsed: true, | |
| items: [ | |
| { | |
| type: "autogenerated", | |
| dirName: "cli", | |
| }, | |
| ], | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/docs/sidebars.js` around lines 245 - 255, The "CLI" top-level category
in the sidebar (the object with label "CLI" and dirName "cli") exposes
deprecated docs; update the sidebar entry to avoid promoting them by either
removing that category from the tutorialSidebar, renaming the label to "CLI
(deprecated)", or moving the object under a new legacy group (e.g., "Legacy" or
"Deprecated") so docs/cli/** are not shown as active top-level content; locate
the category object that has type "category", label "CLI", and dirName "cli" and
apply one of these changes consistently.
| | directory | name | description | active | | ||
| | ---------------------------------------- | -------------- | ---------------------------------------------------------------------- | ------ | | ||
| | [/docs/wg](./wg) | working group | working group documents, architecture documents, todo list, etc | yes | | ||
| | [/docs/wg/format](./wg/format) | format | Grida IR spec and CSS/HTML/SVG import mapping trackers | yes | | ||
| | [/docs/reference](./reference) | reference | glossary and references (technical documents) | yes | | ||
| | [/docs/math](./math) | math | Math reference, used for internal docs referencing | yes | | ||
| | [/docs/platform](./platform) | platform | Grida Platform (API/Spec) documents | yes | | ||
| | [/docs/editor](./editor) | editor | Grida Editor - User Documentation | yes | | ||
| | [/docs/forms](./forms) | forms | Grida Forms - User Documentation | yes | | ||
| | [/docs/with-figma](./with-figma) | with-figma | Grida with Figma - Grida <-> Figma compatibility and user guides | yes | | ||
| | [/docs/design](./design) | design | Design-oriented docs and visual behavior notes | yes | | ||
| | [/docs/canvas](./canvas) | canvas | Grida Canvas SDK - User Documentation | no | | ||
| | [/docs/cli](./cli) | cli | Deprecated CLI docs kept for compatibility | no | | ||
| | [/docs/@designto-code](./@designto-code) | design-to-code | Externally synced reference docs | no | | ||
| | [/docs/\_history](./_history) | history | Archived, code-facing record docs not meant for user navigation | no | | ||
| | [/docs/together](./together) | together | Contributing, Support, Community, etc | no | |
There was a problem hiding this comment.
Fix the two etc. typos in the structure table.
Static analysis is right here: these should include periods.
Proposed typo fix
-| [/docs/wg](./wg) | working group | working group documents, architecture documents, todo list, etc | yes |
+| [/docs/wg](./wg) | working group | working group documents, architecture documents, todo list, etc. | yes |
...
-| [/docs/together](./together) | together | Contributing, Support, Community, etc | no |
+| [/docs/together](./together) | together | Contributing, Support, Community, etc. | no |🧰 Tools
🪛 LanguageTool
[style] ~117-~117: In American English, abbreviations like “etc.” require a period.
Context: ...nts, architecture documents, todo list, etc | yes | | [/docs/wg/format](....
(ETC_PERIOD)
[style] ~130-~130: In American English, abbreviations like “etc.” require a period.
Context: ... | Contributing, Support, Community, etc | no ...
(ETC_PERIOD)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/AGENTS.md` around lines 115 - 130, In the Markdown table in
docs/AGENTS.md, replace the two occurrences of the bare "etc" with "etc." in the
description cells for the "working group" row ("working group documents,
architecture documents, todo list, etc") and the "together" row ("Contributing,
Support, Community, etc"); ensure you only add the missing period and preserve
existing spacing and formatting for the table.
| "nanoid": "^3.3.11", | ||
| "negotiator": "^1.0.0", | ||
| "next": "16.1.6", | ||
| "next": "16.2.4", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
For Next.js 16.2.4, what versions of @next/mdxand@next/third-parties are recommended/supported? Is mixing with 16.1.3 officially supported?
💡 Result:
For Next.js 16.2.4, the recommended/supported versions are @next/mdx ^16.2.x (latest available 16.2.1 or 16.2.2 per release notes) and @next/third-parties ^16.2.x (latest 16.2.2). Official docs recommend installing the latest versions alongside next@latest. Mixing with 16.1.3 versions is not officially supported; these packages follow Next.js versioning for compatibility within the same major.minor release, and semver dictates using matching patch-level versions to avoid potential breaking changes or regressions (e.g., MDX webpack issues fixed in later 16.2.x).
Citations:
- 1: https://nextjs.org/docs/pages/guides/mdx
- 2: https://nextjs.org/blog/next-16-2
- 3: Update dependency @next/mdx to v16 mdx-js/mdx#2655
- 4: https://www.npmjs.com/package/@next/mdx
- 5: https://www.npmjs.com/package/@next/third-parties
- 6: https://nextjs.org/docs/app/guides/third-party-libraries
- 7: leerob/next-mdx-blog@a62191e
Update Next.js companion packages to match next@16.2.4.
The @next/mdx and @next/third-parties packages are pinned to 16.1.3 while next is at 16.2.4. This version mismatch is not officially supported. Upgrade both to 16.2.x versions (e.g., 16.2.2) to align with the main Next.js version and avoid potential breaking changes or regressions in MDX and third-party integrations.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@editor/package.json` at line 154, Update the pinned companion Next packages
to match the main next version: change the dependency versions for "@next/mdx"
and "@next/third-parties" from "16.1.3" to a 16.2.x release (e.g., "16.2.2") so
they align with "next": "16.2.4"; update package.json accordingly and run your
package manager (npm/yarn/pnpm) to refresh the lockfile and verify
compatibility.
1 participant
Summary
Restructure the docs IA and entry points to better match the current product surface.
getting-startedandflagscontent underdocs/_historyconceptsandcodesections from the active docs treeassistantunderwith-figmavector-networkunderdesign.DS_Storeduring docs syncVerification
pnpm buildinapps/docsenandkoNotes
_historyis treated as code-facing archive material, not part of the user-facing docs surface.docs/@designto-code/**remains in place as externally synced reference material.Summary by CodeRabbit
Release Notes
Chores
Documentation