mirror of
https://github.com/zulip/zulip.git
synced 2025-11-02 21:13:36 +00:00
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:
@@ -1,8 +1,11 @@
|
||||
# Documenting an integration
|
||||
|
||||
Every Zulip integration must be documented in
|
||||
`zerver/webhooks/mywebhook/doc.md` (or
|
||||
`templates/zerver/integrations/<integration_name>.md`, for non-webhook
|
||||
In order for a [Zulip
|
||||
integration](https://zulip.com/api/integrations-overview) to be useful
|
||||
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).
|
||||
|
||||
Usually, this involves a few steps:
|
||||
|
||||
Reference in New Issue
Block a user