reorder menu items

[gkorland]

Summary by CodeRabbit

• Documentation
  • Updated navigation ordering in multiple docs to improve menu placement and discoverability.
  • Reorganized document hierarchy to establish clearer parent-child relationships.
  • Added redirects to preserve existing links and ensure backward compatibility with prior navigation paths.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

PR Summary by Typo

Overview

This PR reorganizes the documentation's navigation structure by reordering existing menu items and relocating the "Migration" section. The changes aim to improve the logical flow and accessibility of documentation pages.

Key Changes

• The migration documentation section, including its sub-pages, was moved under the operations section.
• The nav_order for the "Cloud DBaaS" page was set to 10.
• The "Migration" section's nav_order was updated to 1 within its new parent, and a redirect_from entry was added.
• The nav_order for the "Persistence" page was updated to 2 within the operations section.

Work Breakdown

Category	Lines Changed
New Work	4 (57.1%)
Rework	3 (42.9%)
Total Changes	7

To turn off PR summary, please visit Notification settings.

[coderabbitai]

📝 Walkthrough

Walkthrough

Three documentation files had their YAML front matter updated to adjust navigation ordering and site hierarchy metadata; one file also received a redirect entry.

Changes

Cohort / File(s)	Summary
Cloud doc front matter cloud/index.md	Added nav_order: 10 to front matter.
Operations migration metadata operations/migration/index.md	Updated nav_order (11 → 1); added parent: "Operations" and redirect_from: [/migration.html] in front matter.
Operations persistence ordering operations/persistence.md	Updated nav_order (1 → 2).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I nudged a YAML leaf and set it right,
Orders shuffled softly in the night.
A parent named, a redirect spun,
Three pages tidy, hopping done.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'reorder menu items' directly and clearly describes the primary change: restructuring navigation order across documentation sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[typo-app]

Static Code Review 📊

✅ All quality checks passed!

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @operations/migration/index.md:
- Around line 4-9: The frontmatter contains a duplicated key: remove the
duplicate has_children entry so only one has_children: true remains; edit the
block that currently lists has_children twice (the two has_children lines in the
provided diff) and keep a single declaration to eliminate the duplicate key.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 814133e and 22db379.

📒 Files selected for processing (6)

• cloud/index.md
• operations/migration/index.md
• operations/migration/kuzu-to-falkordb.md
• operations/migration/neo4j-to-falkordb.md
• operations/migration/rdf-to-falkordb.md
• operations/migration/redisgraph-to-falkordb.md

🔇 Additional comments (2)

operations/migration/index.md (1)

6-6: Verify parent Operations page configuration.

Ensure the parent page Operations exists and has has_children: true or equivalent configuration to properly establish the hierarchy.

cloud/index.md (1)

4-4: Verify complete navigation ordering consistency.

The nav_order: 10 placement for Cloud suggests it should appear before Operations (nav_order: 11 in migration/index.md). Confirm that all top-level sections have consistent nav_order values with no gaps or conflicts.

[typo-app]

AI Code Review 🤖

Files Reviewed: 7
Comments Added: 0
Lines of Code Analyzed: 10
Critical Issues: 0

PR Health: Excellent 🔥

_{Give 👍 or 👎 on each review comment to help us improve.}

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In @operations/migration/index.md:
- Around line 4-7: The YAML front matter contains a duplicated property
"has_children" (two occurrences), which is invalid; open the front matter block
and remove one of the duplicate has_children: true entries so only a single
has_children key remains, ensuring the YAML is valid.
- Line 5: The frontmatter key nav_order in the new file currently reads
"nav_order: 1" but the PR states it should be 11; update the nav_order value in
operations/migration/index.md from 1 to 11 (or confirm and change it to the
intended value) so the file's nav_order matches the PR objectives.
- Line 6: Frontmatter in the migration page contains a duplicate has_children
key causing a YAML syntax issue; open the frontmatter block in the file and
remove the redundant has_children entry (keep a single has_children: true if
needed) so the frontmatter has unique keys and valid YAML, then save and verify
the page renders without frontmatter warnings.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 22db379 and ab8a682.

📒 Files selected for processing (2)

• operations/migration/index.md
• operations/persistence.md

✅ Files skipped from review due to trivial changes (1)

• operations/persistence.md