Skip to content

[configuration] Improve transport configuration docs #3976

Closed
@lobsterkatie

Description

@lobsterkatie

Core or SDK?

Platform/SDK

Which part? Which one?

multiple

Description

Two (and a half) issues to fix here:

1) Some of our SDKs have a Transports section in the main configuration docs. (Here's the Go one, for example.) Where those exist, we should link to them in the transport entry on the main options page.

2) Ideally the various Transports pages can be consolidated into one template with includes. When we do this, we should create includes for node as well.

2a) As part of a larger initiative to encourage more folks to open-source custom integrations and transports they build, we should add a Community section to said Transports template. Once we do that, we can add a link to the new Forge transport to the node include.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions