[PR #1455] [MERGED] docs: rewrite the Open WebUI Community page around who reads it #1414

New issue

Closed

opened 2026-10-18 14:19:31 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:19:31 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/1455
Author: @silentoplayz
Created: 10/7/2026
Status: ✅ Merged
Merged: 10/7/2026
Merged by: @tjbck

Base: main ← Head: docs/community-page-rewrite

📝 Commits (2)

e26d349 docs: rewrite the Open WebUI Community page around who reads it
c72c181 docs: drop the Posts are not reviewed box from the Community page

📊 Changes

1 file changed (+62 additions, -83 deletions)

View changed files

📝 docs/ecosystem/community.md (+62 -83)

📄 Description

Summary

Rewrites the Open WebUI Community page around the two people who read it: a user who wants to use what others have built and share their own, and the admin who runs the server and needs to know what the site can do to it.

The current page opens with a tour of the site's pages and post types, and its admin answers are spread across several sections. This version drops the tour, starts each section with why the reader would care, and keeps only what they need to act on.

For users, in the order most people need them:

Import a post: three steps, then where each type of post lands and who can import it.
Share what you built: where Share is for each kind of item, and what sharing a Tool or Function publishes.
Review a model: reading reviews from the model selector, and writing one after rating a reply.
Add your usage to the Leaderboard: why to sync, and the steps from openwebui.com to the confirmation dialog on your instance.

For admins, the three questions they come with each get a section:

Who can bring code onto your server: who can import Tools and Functions, and that a plugin's requirements line is installed with pip, with the setting that stops it.
What reaches openwebui.com: the site never connects to the server, shares and stats syncs are the only things a user can send, and the full list of what a sync includes and leaves out.
Turn it off: the Community Sharing setting, its environment variable, and everything it hides.

Next steps are gathered in one Where to go next section at the end. The page is 21 lines shorter than before.

None. This replaces #1452, which documented every control on openwebui.com.

Checklist

I have reviewed the relevant documentation and matched the existing style.
This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility.
I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories.

Notes for reviewers

The Open WebUI side of every step (the Share menus, Community Reviews, the review link after rating a reply, the Sync Usage Stats dialog, what a sync sends, and what Community Sharing hides) is checked against the code on dev.
The openwebui.com labels (Get, Sync Stats, Sync Open WebUI Stats, Write a review and Post) are checked on the site while signed in, without submitting anything.
An import still fills in the editor when you aren't signed in to your instance yet: sign-in returns you to the editor, which then asks the openwebui.com tab for the post again.
npm run build passes with no broken links or anchors.

_{🔄 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/open-webui/docs/pull/1455 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 10/7/2026 **Status:** ✅ Merged **Merged:** 10/7/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `main` ← **Head:** `docs/community-page-rewrite` --- ### 📝 Commits (2) - [`e26d349`](https://github.com/open-webui/docs/commit/e26d3496deafa0cca0b6aee695be0a51ca0dee2b) docs: rewrite the Open WebUI Community page around who reads it - [`c72c181`](https://github.com/open-webui/docs/commit/c72c1812078733d5ae127f396fd68c2ce819aacd) docs: drop the Posts are not reviewed box from the Community page ### 📊 Changes **1 file changed** (+62 additions, -83 deletions) <details> <summary>View changed files</summary> 📝 `docs/ecosystem/community.md` (+62 -83) </details> ### 📄 Description ## Summary Rewrites the [Open WebUI Community](https://docs.openwebui.com/ecosystem/community) page around the two people who read it: a user who wants to use what others have built and share their own, and the admin who runs the server and needs to know what the site can do to it. The current page opens with a tour of the site's pages and post types, and its admin answers are spread across several sections. This version drops the tour, starts each section with why the reader would care, and keeps only what they need to act on. For users, in the order most people need them: - **Import a post**: three steps, then where each type of post lands and who can import it. - **Share what you built**: where **Share** is for each kind of item, and what sharing a Tool or Function publishes. - **Review a model**: reading reviews from the model selector, and writing one after rating a reply. - **Add your usage to the Leaderboard**: why to sync, and the steps from openwebui.com to the confirmation dialog on your instance. For admins, the three questions they come with each get a section: - **Who can bring code onto your server**: who can import Tools and Functions, and that a plugin's `requirements` line is installed with pip, with the setting that stops it. - **What reaches openwebui.com**: the site never connects to the server, shares and stats syncs are the only things a user can send, and the full list of what a sync includes and leaves out. - **Turn it off**: the **Community Sharing** setting, its environment variable, and everything it hides. Next steps are gathered in one **Where to go next** section at the end. The page is 21 lines shorter than before. ## Related issue or discussion None. This replaces #1452, which documented every control on openwebui.com. ## Checklist - [x] I have reviewed the relevant documentation and matched the existing style. - [x] This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility. - [x] I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories. ## Notes for reviewers - The Open WebUI side of every step (the Share menus, **Community Reviews**, the review link after rating a reply, the **Sync Usage Stats** dialog, what a sync sends, and what **Community Sharing** hides) is checked against the code on `dev`. - The openwebui.com labels (**Get**, **Sync Stats**, **Sync Open WebUI Stats**, **Write a review** and **Post**) are checked on the site while signed in, without submitting anything. - An import still fills in the editor when you aren't signed in to your instance yet: sign-in returns you to the editor, which then asks the openwebui.com tab for the post again. - `npm run build` passes with no broken links or anchors. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:19:31 +00:00