[Meta] Standardize exporters docs

[svrnm]

Description

Based on #3355 all exporter pages should follow a similar structure (where applicable). In a second step we can extract common text blocks into snippets managed at one place.

• C++ (C++ exporters update #3998)
• .NET
• Erlang/Elixir
• Go
• Java (Rework the java exporters page #3558)
• JavaScript (Update exporters documentation for JS #3355)
• PHP
• Python (Rework the python exporters page #3515)
• Ruby
• Rust
• Swift

How you can help

Take a language of your choice and use the structure of the JavaScript Exporters page as template (the "browser" part is not applicable for other languages and can be skipped)

[justankiit]

I would also love to add value on this issue!

[svrnm]

I would also love to add value on this issue!

Thanks @kumarankit999, what's a language you feel comfortable with tackling?

[kennykguo]

if this issue is still active, please assign this issue to me, thanks

[svrnm]

@kennykguo this is a meta issue, which will not be assigned. You can take a look at an individual language and see if you can help with that.

[justankiit]

I would like to work in GO!

[svrnm]

@kumarankit999 that's great to hear! Please take a look at some of the docs that are completed already (Python, C++, JS. Pick one as your starting point, pick the underlying markdown file and build the updated version from there.

You can also take a look at this ongoing PR for .NET to see how you can tackle this:

#4016

Thank you