mirror of https://github.com/zulip/zulip.git
docs: Make it easier to locate docs for how to build integration.
Make it easier to locate docs for how to build an integration by adding a link to the docs at the top of the docs on how to document an integration. Tweaked by tabbott to adjust the whole first paragraph and make the link more contextual.
This commit is contained in:
parent
d4e2abb53a
commit
5fa8cf042d
|
@ -1,8 +1,11 @@
|
||||||
# Documenting an integration
|
# Documenting an integration
|
||||||
|
|
||||||
Every Zulip integration must be documented in
|
In order for a [Zulip
|
||||||
`zerver/webhooks/mywebhook/doc.md` (or
|
integration](https://zulip.com/api/integrations-overview) to be useful
|
||||||
`templates/zerver/integrations/<integration_name>.md`, for non-webhook
|
to users, it must be documented. Zulip's common system for documenting
|
||||||
|
integrations involves writing Markdown files, either at
|
||||||
|
`zerver/webhooks/{webhook_name}/doc.md` (for webhook integrations) or
|
||||||
|
`templates/zerver/integrations/{integration_name}.md` (for other
|
||||||
integrations).
|
integrations).
|
||||||
|
|
||||||
Usually, this involves a few steps:
|
Usually, this involves a few steps:
|
||||||
|
|
Loading…
Reference in New Issue