fix(readme): Fix the table formatting errors in the architecture docu…

[yihuishou]

…ment

Fixes #

Why

What users will see

Surface area

• UI — new page / dialog / panel / menu item / setting / empty state in apps/web or apps/desktop (including Electron menu bar)
• Keyboard shortcut — new or changed
• CLI / env var — new od subcommand or flag, new tools-dev / tools-pack / tools-pr flag, or new OD_* env var
• API / contract — new /api/* endpoint, new SSE event, or changed shape in packages/contracts
• Extension point — new entry under skills/, design-systems/, design-templates/, or craft/, or change to the skills protocol
• i18n keys — added new translation keys (see TRANSLATIONS.md for the locale workflow)
• New top-level dependency — adding any new entry to the root package.json (dependencies or devDependencies); workspace-package package.json files are out of scope. Include a paragraph on what we get vs. what bytes we ship (see CONTRIBUTING.md → Code style)
• Default behavior change — changes what existing users experience without opting in (default model, default setting, file/SQLite schema, auto-network on startup, auto-install)
• None — internal refactor, docs, tests, or translation update only

Screenshots

Bug fix verification

Validation

[lefarcen]

All gates green here — flagged for the maintainers. Thanks @yihuishou for the README fix and @Siri-Ray for the review!

[open-design-bot]

🎉 📡 You just leveled up to Giotto

📡 ✨ Sending steady signals.

🙌 Your contributions send a clear signal across the network: you care about making Open Design better.

💛 Thanks for helping Open Design move forward. Keep building in the open. 🚀

---

📊 Rank #198 among 198 contributors.

🔗 Share on X (English) · 分享到 X（中文）

[kokisanai]

Hi @yihuishou!

Your first Open Design PR has been merged! Huge thanks for jumping in and improving the project!

You contributed:

Merged PR: #3926 fix(readme): Fix the table formatting errors in the architecture docu…
#3926

Your first contribution improved docs formatting, so we picked two follow-up issues that stay close to docs and contributor-facing content quality.

For your next contribution, we picked two issues that look like a good follow-up:

1. docs: comprehensive cloud deployment documentation #1021 docs: comprehensive cloud deployment documentation
   docs: comprehensive cloud deployment documentation #1021

This follows naturally from your first docs fix and gives you a larger documentation surface to improve.

2. 8 design-templates missing example.html — clarify policy or backfill #1887 8 design-templates missing example.html — clarify policy or backfill
   8 design-templates missing example.html — clarify policy or backfill #1887

This is a strong fit if you want another content-structure cleanup task with clear contributor impact.

If one of these looks interesting, feel free to comment /claim on the issue and we will help you get started!

Once your second PR gets merged, you will move into our Continuous Contributor tier. We are also starting to highlight repeat contributors more actively in the community, so this is a great time to keep going!

Thanks again for the first PR, and welcome to the Open Design contributor community!

The Open Design team

P.S. We hang out in Discord — come say hi: https://discord.gg/3C6EWXbdQQ
There's a #contributors channel where folks share what they're working on.\n