Skip to content

add onboarding documentation#33

Open
viktordanch wants to merge 1 commit intokoldovsky:mainfrom
viktordanch:add-onboarding-docs
Open

add onboarding documentation#33
viktordanch wants to merge 1 commit intokoldovsky:mainfrom
viktordanch:add-onboarding-docs

Conversation

@viktordanch
Copy link
Copy Markdown

@viktordanch viktordanch commented Mar 27, 2026

Summary by CodeRabbit

  • Documentation
    • Added introduction and getting started guide with documentation structure overview
    • Added comprehensive onboarding guide with setup instructions, architecture overview, daily workflow recommendations, and first-week ramp-up plan

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 27, 2026

📝 Walkthrough

Walkthrough

Two new documentation pages added to the repository: a get-started guide with links to documentation sections and an onboarding guide for new engineers covering monorepo layout, architecture overview, local setup steps, workflows, task routing, and a structured first-week ramp-up plan.

Changes

Cohort / File(s) Summary
Getting Started Documentation
get-started.mdx
New introductory page with "Try now" link to Excalidraw and documentation structure overview linking to various guides and package documentation.
Onboarding Guide
onboarding.mdx
New comprehensive onboarding guide for new engineers including monorepo architecture, local setup instructions, daily workflows, task routing diagrams, first-week ramp-up plan, collaboration expectations, and validation checklists.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Fresh docs are here, so clear and bright,
A guide for newcomers, from setup to flight,
Architecture mapped and workflows aligned,
Welcome aboard—let's code in design! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'add onboarding documentation' accurately reflects the main change: adding a new onboarding.mdx file plus a get-started.mdx documentation page.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
get-started.mdx (1)

12-12: Small copy polish for readability.

Consider “structured in the following way”.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@get-started.mdx` at line 12, Update the sentence "These docs are focused on
developers, and structured in the following way:" to include the definite
article — change it to "These docs are focused on developers, and structured in
the following way:" -> "These docs are focused on developers, and structured in
the following way:" by inserting "the" before "following" (i.e., "structured in
the following way"). Locate this exact sentence in get-started.mdx and apply the
small copy change for readability.
onboarding.mdx (2)

100-101: Consider making Day 1 doc references clickable links.

Using links here improves first-day navigation speed for new joiners.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@onboarding.mdx` around lines 100 - 101, Replace the plain text doc names in
onboarding.mdx with clickable links: change "introduction/development" and
"introduction/contributing" to relative MDX/Markdown links (e.g.,
[Development](/introduction/development) and
[Contributing](/introduction/contributing)) and make the root README reference a
link like [README.md](/README.md); ensure links use the project's relative path
style and keep link text clear for Day 1 readers.

78-81: Use non-mutating checks as default PR gate (avoid blanket snapshot updates).

yarn test:update updates snapshots and can hide unintended UI diffs when run by default. Prefer read-only verification in the standard checklist, and only update snapshots when changes are intentional.

Suggested fix
-1. Run quality gates before opening a PR:
-   - `yarn test:typecheck`
-   - `yarn test:update`
-   - `yarn fix` (if needed)
+1. Run quality gates before opening a PR:
+   - `yarn test:typecheck`
+   - `yarn test` (or repo-standard non-mutating test command)
+   - `yarn fix` (if needed)
+   - Update snapshots only when intentionally changing snapshot outputs.
-- [ ] Tests and snapshots are updated (`yarn test:update`).
+- [ ] Tests pass (`yarn test` or repo-standard non-mutating test command).
+- [ ] Snapshots updated only when expected output intentionally changed.

Also applies to: 126-127

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@onboarding.mdx` around lines 78 - 81, Replace the default snapshot-updating
command "yarn test:update" in the PR checklist with a non-mutating verification
command (e.g., "yarn test" or your CI read-only test target such as "yarn
test:ci") and add a short parenthetical note that snapshot updates must be
performed explicitly when changes are intentional; update both occurrences of
"yarn test:update" so the checklist uses the read-only check by default and
reserve "yarn test:update" for an explicit developer action.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@get-started.mdx`:
- Line 15: The link in get-started.mdx currently points to
/docs/introduction/onboarding but the new page was added as onboarding.mdx
(top-level); update the reference in get-started.mdx to /docs/onboarding or
alternatively add an explicit slug (e.g., "slug: /docs/introduction/onboarding")
inside onboarding.mdx so the existing link resolves—modify either the link
target in get-started.mdx or the frontmatter slug in onboarding.mdx to make them
match.

---

Nitpick comments:
In `@get-started.mdx`:
- Line 12: Update the sentence "These docs are focused on developers, and
structured in the following way:" to include the definite article — change it to
"These docs are focused on developers, and structured in the following way:" ->
"These docs are focused on developers, and structured in the following way:" by
inserting "the" before "following" (i.e., "structured in the following way").
Locate this exact sentence in get-started.mdx and apply the small copy change
for readability.

In `@onboarding.mdx`:
- Around line 100-101: Replace the plain text doc names in onboarding.mdx with
clickable links: change "introduction/development" and
"introduction/contributing" to relative MDX/Markdown links (e.g.,
[Development](/introduction/development) and
[Contributing](/introduction/contributing)) and make the root README reference a
link like [README.md](/README.md); ensure links use the project's relative path
style and keep link text clear for Day 1 readers.
- Around line 78-81: Replace the default snapshot-updating command "yarn
test:update" in the PR checklist with a non-mutating verification command (e.g.,
"yarn test" or your CI read-only test target such as "yarn test:ci") and add a
short parenthetical note that snapshot updates must be performed explicitly when
changes are intentional; update both occurrences of "yarn test:update" so the
checklist uses the read-only check by default and reserve "yarn test:update" for
an explicit developer action.
🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 643fd28e-c813-4206-b0b3-38aec47a8437

📥 Commits

Reviewing files that changed from the base of the PR and between be47f1d and 82109fd.

📒 Files selected for processing (2)
  • get-started.mdx
  • onboarding.mdx

These docs are focused on developers, and structured in the following way:

- [Introduction](/docs/) — development setup and introduction.
- [Onboarding](/docs/introduction/onboarding) — first-week setup and ramp-up guide for new engineers.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Potential broken internal link to onboarding page.

Line 15 points to /docs/introduction/onboarding, but this PR adds onboarding.mdx as a top-level docs page, which usually resolves to /docs/onboarding. Please align the URL (or explicitly set a slug in onboarding.mdx) to avoid a dead link.

Suggested fix
-- [Onboarding](/docs/introduction/onboarding) — first-week setup and ramp-up guide for new engineers.
+- [Onboarding](/docs/onboarding) — first-week setup and ramp-up guide for new engineers.
📝 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
- [Onboarding](/docs/introduction/onboarding) — first-week setup and ramp-up guide for new engineers.
- [Onboarding](/docs/onboarding) — first-week setup and ramp-up guide for new engineers.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@get-started.mdx` at line 15, The link in get-started.mdx currently points to
/docs/introduction/onboarding but the new page was added as onboarding.mdx
(top-level); update the reference in get-started.mdx to /docs/onboarding or
alternatively add an explicit slug (e.g., "slug: /docs/introduction/onboarding")
inside onboarding.mdx so the existing link resolves—modify either the link
target in get-started.mdx or the frontmatter slug in onboarding.mdx to make them
match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant