docs(website): drop apologetic tone from /community

[IamCoder18]

Removes the 'Synapse is new' / 'one team confirmed' disclaimer from the community page and reframes the page around contribution.

Changes

• Replace the disclaimer block with a positive lede.
• Describe the listed team as 'Running Synapse on their robot' instead of 'One confirmed team using Synapse.'
• Add an invitation below the list for other FTC teams to add themselves via PR.

Files

• website/src/pages/community.astro

[coderabbitai]

Warning

Review limit reached

Next included review available in 27 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: daf003ab-bd0b-43aa-bf41-c8442c660964

📥 Commits

Reviewing files that changed from the base of the PR and between 1ee471d and c1d234d.

📒 Files selected for processing (1)

• website/src/pages/community.astro

---

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

[kilo-code-bot]

SUGGESTION: Grammar / parallel structure is broken in the lede

The sentence reads as three options joined by commas, but the third option switches verbs: Pitch in on [code], pitch in on [docs], or share what your team built. The share clause drops pitch in on, so the line trails off awkwardly and the parallelism between the three contributions is lost.

Suggested rewrite:

Synapse is built in the open by FTC teams and contributors. Pitch in on code or docs, or share what your team built.

Other viable alternatives:

• Pitch in on code, docs, or your team's build.
• Help with code or docs, or share what your team built.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The previously flagged parallel-structure issue in the community lede has been resolved in commit c1d234d. The lede now reads "Pitch in on code or docs, or share what your team built.", which restores parallelism between the three contribution options.

Files Reviewed (1 files)

• website/src/pages/community.astro

Previous Review Summary (commit a4aa17b)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit a4aa17b)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
website/src/pages/community.astro	21	Broken parallel structure in the lede — Pitch in on code, docs, or share what your team built. mixes two verbs across three listed options.

Files Reviewed (1 files)

• website/src/pages/community.astro - 1 issue

Notes

• The rename from .cm__disclaimer → .cm__lede and the removal of the card-style chrome are consistent with the PR's stated goal of dropping the apologetic tone; no stale references to the old class remain in the repo.
• The new "Open a PR" call-to-action correctly points to CONTRIBUTING.md, which is the right entry point for first-time contributors, so no change recommended there.
• The teams list retains role="list", preserving the Safari-safe list-reset pattern.
• No security, runtime, or logic issues found in the changed lines.

Fix these issues in Kilo Cloud

---

_{Reviewed by minimax-m3 · Input: 0 · Output: 0 · Cached: 0}

[IamCoder18]

Fixed in c1d234d — lede now reads: "Pitch in on code or docs, or share what your team built."