docs: add tiny-pro and tiny-editor in top nav menu

[kagol]

Summary by CodeRabbit

Release Notes

• New Features

  • Added TinyPro to the playground menu with dedicated documentation resources
  • Expanded development documentation with TinyPro and TinyEditor entries

• Documentation

  • Updated documentation pages with demo site URLs for TinyPro
  • Refined menu structure for improved navigation

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

[coderabbitai]

Walkthrough

The changes add TinyPro product entries to the navigation menu configuration, including asset imports and metadata for menu items across playground and documentation sections, plus a demonstration site link in the product documentation.

Changes

Cohort / File(s)	Summary
Menu Configuration packages/common/src/config/header.ts	Added tiny-pro.svg import and TinyPro menu entries in playground section; updated NEXT-SDKs title casing and added TinyPro, TinyEditor, and NEXT-SDKs entries across documentation menu sections.
Documentation packages/opentiny-docs/src/views/vue-pro/start.md	Added demonstration site URL reference for TinyPro product.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 With whiskers aquiver, I add TinyPro so fine,
To menus and docs, in a neat little line,
Logos and links hop and skip all around,
Configuration treasures in headers are found,
This bundle so tiny brings rabbit delight! ✨

🚥 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 accurately describes the main changes: adding TinyPro and TinyEditor entries to the top navigation menu across multiple configuration and documentation files.
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 docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch kagol/docs-add-tiny-pro

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @packages/common/src/config/header.ts:
- Around line 157-163: The TinyEditor entry currently reuses the wrong logo
(tinyRobot); add a dedicated SVG file named tiny-editor.svg into
packages/common/src/assets/appIcon/, import it (e.g. import tinyEditor from
'.../tiny-editor.svg') and update the TinyEditor object in header.ts (the entry
with title 'TinyEditor') to set logo: tinyEditor and keep other fields the same
so the correct asset is used.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8375e5a and 009f1e7.

📒 Files selected for processing (2)

• packages/common/src/config/header.ts
• packages/opentiny-docs/src/views/vue-pro/start.md

🔇 Additional comments (4)

packages/opentiny-docs/src/views/vue-pro/start.md (1)

10-11: LGTM!

The demo site URL is consistent with the playground entry added in header.ts and provides a useful quick link for users to experience TinyPro.

packages/common/src/config/header.ts (3)

6-6: LGTM!

The SVG import follows the existing pattern for other product logos.

---

107-114: LGTM!

The TinyPro playground entry is well-structured and consistent with the other items. The demo URL correctly matches the documentation in start.md.

---

150-156: LGTM!

The TinyPro documentation entry is properly configured with the correct logo and GitHub repository link.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, run the suggested check for editor-related SVG assets
fd -t f -e svg 'editor' packages/common/src/assets/

Repository: opentiny/opentiny.design

Length of output: 50

---

🏁 Script executed:

# Check what imports tinyRobot and understand what it is
cd packages/common/src/config
head -50 header.ts | cat -n

Repository: opentiny/opentiny.design

Length of output: 2085

---

🏁 Script executed:

# Search for where tinyRobot is imported from
rg 'tinyRobot' packages/common/src/config/header.ts -B 5 -A 2

Repository: opentiny/opentiny.design

Length of output: 1309

---

🏁 Script executed:

# Check the assets directory structure to understand available logos
fd -t f -e svg '' packages/common/src/assets/ | head -20

Repository: opentiny/opentiny.design

Length of output: 1021

---

Add dedicated logo asset for TinyEditor.

TinyEditor incorrectly uses tinyRobot logo, which is the asset for the TinyRobot project. Other products (TinyVue, TinyEngine, TinyPro, etc.) each have their own dedicated asset in packages/common/src/assets/appIcon/. Add a tiny-editor.svg asset for TinyEditor to maintain consistency.

🤖 Prompt for AI Agents

In @packages/common/src/config/header.ts around lines 157 - 163, The TinyEditor
entry currently reuses the wrong logo (tinyRobot); add a dedicated SVG file
named tiny-editor.svg into packages/common/src/assets/appIcon/, import it (e.g.
import tinyEditor from '.../tiny-editor.svg') and update the TinyEditor object
in header.ts (the entry with title 'TinyEditor') to set logo: tinyEditor and
keep other fields the same so the correct asset is used.