docs(getting-started): add Python and Go SDK links

[anjor]

Added community supported language sdks

[rvagg]

Thanks for putting this together @anjor. It's good to see SDK work happening in other languages.

My concern is with the framing: listing these alongside the official TypeScript SDK as "SDKs by Language" suggests they're maintained or endorsed by the team, and we're not in a position to make that claim since we haven't been involved in their development or reviewed them for compatibility with the current contracts or our product goals for FOC. The protocol surface is still moving and we'd rather not create expectations we can't back up.

I'd be happy to have community projects linked from the docs, but with framing that makes the distinction clear; something like a "Community" callout rather than a peer listing. I'd also prefer to keep the Getting Started page focused on the official SDK and leave Python/Go quickstarts to those projects' own docs.

@nijoe1 could you work with Anjor on finding the right way to present this?

[anjor]

I see your point and have amended the PR accordingly. However I would like to flag that these were official docs for foc, and not just the ts synapse SDK (deployed to filecoin.cloud). Surely the interactions with foc should be independent of the sdk used?

In any case, due to the fast moving nature of the protocol I do agree with the explicit callout that go-synapse and pynapse are community maintained (maybe go-synapse less so than pynapse since it's funded by FF?), and have changed the PR accordingly.

[Copilot]

Pull request overview

Adds documentation pointers to community-maintained Synapse SDKs so developers can discover non-TypeScript language options from key entry points in the docs.

Changes:

• Added a “Community SDKs” admonition in Getting Started linking to Python and Go SDK repositories.
• Added the same “Community SDKs” admonition in the Synapse SDK developer guide.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
docs/src/content/docs/getting-started/index.mdx	Adds a Community SDKs note with Python/Go links near installation instructions.
docs/src/content/docs/developer-guides/synapse.md	Adds the same Community SDKs note near the top of the Synapse SDK overview page.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[nijoe1]

I was thinking that a new page inside resources/community-projects would make more sense to me. This would allow us to showcase other example projects as well, and would make it easier to categorize them by type without having to break the docs' structure or maintain it in that sense. It would also eliminate the recurring question of where we can add new community builds, such a page could provide one centralized place for all of them. Open to feedback!

[anjor]

I am fine with whatever.
@nijoe1 it's up to you -- lmk if you would like me to make those changes.

[nijoe1]

Yes I think this is the best solution here! @anjor

[anjor]

Done! I've created a dedicated resources/community-projects.md page and updated the Getting Started and Synapse SDK pages to link to it instead of listing the SDKs inline.

Changes:

• New page: docs/src/content/docs/resources/community-projects.md
• Brief "Other Languages?" tip in Getting Started and Synapse SDK pages linking to the new page
• Community page includes a caution callout making the community-maintained status clear

The new page is also structured to accommodate future community projects (tools, example apps, etc.) in one centralized place.

[nijoe1]

LGTM

[anjor]

@rvagg cool to merge? You will need to remove your request for changes.

[rvagg]

cool, thanks @anjor