[PR #220] [MERGED] docs: add external provider integration guide #218

Closed
opened 2026-10-15 18:02:44 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/SillyTavern/SillyTavern-Docs/pull/220
Author: @Wolfsblvt
Created: 10/2/2026
Status: ✅ Merged
Merged: 10/2/2026
Merged by: @Wolfsblvt

Base: main ← Head: docs/provider-integration-guide


📝 Commits (4)

  • 14f157c docs: add external provider integration guide
  • 79d82c3 docs: link external provider integration guide
  • 8b4277e docs: route provider authors to integration guide
  • fdc30bd docs: normalize provider guide newline

📊 Changes

3 files changed (+167 additions, -0 deletions)

View changed files

➕ For_Contributors/Provider-Integrations.md (+157 -0)
📝 For_Contributors/index.md (+6 -0)
📝 Usage/API_Connections/openai.md (+4 -0)

📄 Description

Summary

  • add a canonical contributor guide for choosing between Custom OpenAI-compatible setup, UI extensions, server plugins, provider-neutral core improvements, and prior discussion for official integrations;
  • include a copyable provider-owned setup-guide template;
  • link the guide from the contributor landing page and the Custom OpenAI-compatible endpoint documentation.

Why

New provider proposals currently reach several disconnected documentation pages without one public route explaining which integration surface fits. This guide gives provider teams a useful alternative to adding permanent named integrations in core or official extensions, while keeping provider-specific setup and support with the provider that owns them.

The page also makes clear that existing integrations are not precedent and that first-party official integrations remain exceptional and require product discussion before implementation.

Companion contribution guidance: SillyTavern/SillyTavern#6099

Scope

Documentation only. This does not add, remove, or change any provider integration.

Verification

  • reviewed the new page frontmatter and route;
  • checked the contributor-index and Custom-endpoint links against the proposed route;
  • inspected the complete branch diff for unrelated changes.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/SillyTavern/SillyTavern-Docs/pull/220 **Author:** [@Wolfsblvt](https://github.com/Wolfsblvt) **Created:** 10/2/2026 **Status:** ✅ Merged **Merged:** 10/2/2026 **Merged by:** [@Wolfsblvt](https://github.com/Wolfsblvt) **Base:** `main` ← **Head:** `docs/provider-integration-guide` --- ### 📝 Commits (4) - [`14f157c`](https://github.com/SillyTavern/SillyTavern-Docs/commit/14f157c84ea9952b7c70f584fe7bcb4b1d706429) docs: add external provider integration guide - [`79d82c3`](https://github.com/SillyTavern/SillyTavern-Docs/commit/79d82c3e614d5b2b6addb644801acbd0cf5a79cd) docs: link external provider integration guide - [`8b4277e`](https://github.com/SillyTavern/SillyTavern-Docs/commit/8b4277ee51b73addc87a91500c52c384881f0024) docs: route provider authors to integration guide - [`fdc30bd`](https://github.com/SillyTavern/SillyTavern-Docs/commit/fdc30bd153c02eb892e1129ebd3a504a56615669) docs: normalize provider guide newline ### 📊 Changes **3 files changed** (+167 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `For_Contributors/Provider-Integrations.md` (+157 -0) 📝 `For_Contributors/index.md` (+6 -0) 📝 `Usage/API_Connections/openai.md` (+4 -0) </details> ### 📄 Description ## Summary - add a canonical contributor guide for choosing between Custom OpenAI-compatible setup, UI extensions, server plugins, provider-neutral core improvements, and prior discussion for official integrations; - include a copyable provider-owned setup-guide template; - link the guide from the contributor landing page and the Custom OpenAI-compatible endpoint documentation. ## Why New provider proposals currently reach several disconnected documentation pages without one public route explaining which integration surface fits. This guide gives provider teams a useful alternative to adding permanent named integrations in core or official extensions, while keeping provider-specific setup and support with the provider that owns them. The page also makes clear that existing integrations are not precedent and that first-party official integrations remain exceptional and require product discussion before implementation. Companion contribution guidance: SillyTavern/SillyTavern#6099 ## Scope Documentation only. This does not add, remove, or change any provider integration. ## Verification - reviewed the new page frontmatter and route; - checked the contributor-index and Custom-endpoint links against the proposed route; - inspected the complete branch diff for unrelated changes. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-15 18:02:44 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SillyTavern/SillyTavern-Docs#218
No description provided.