Guidance on contributing Go docs

[verdverm]

Relatively new to the project, noticed many places where there are examples for only python vs multiple languages. I'm keen to add Go examples as I make my way through the docs.

Would you prefer these come in one-by-one, per section, not super important?

Anything else that would be helpful know beyond what's in contributing.md?

[verdverm]

related, and more unclear, there are a bunch of function_and_type_names inline code blocks among paragraphs of explainer text spread throughout the docs that don't match Go's idiomatic camelCaseNaming convention

Curious about thoughts on this?

My anecdotal reaction is that it brings uneasy feelings when reading the docs as a long time gopher, occasional pythonista (generally speaking / in the context of both my comments)

Also curious to the implications on DX and adoption w.r.t. Go devs, perhaps Java as well

[ivanmkc]

Hi @verdverm, the docs have seen many contributors across several languages, so coding styles and how snippets are managed are not as strict as they could be. For example, many Py and Java snippets are embedded in markdown whereas we've tried to keep all code (except pseudocode) for ADK Go in executable go files.

Since ADK launched for Python first, there are pages that remain Python-focussed, which understandably can lead to confusion for non-Python audiences. This is something we're actively tracking and in the backlog. If you see any non-idiomatic Go code, let us know.

As for contributing, I would follow the example of how other Go snippets are handled (i.e. in a Go file, with references via tag from a .md file) and open a PR.