Skip to content

Conversation

@peetuhr
Copy link

@peetuhr peetuhr commented Dec 23, 2025

Description

Comprehensive revamp of the "Open WebUI for Enterprise" documentation. The goal was to communicate OWUI values for decision makers, and create a scalable structure for future partners and case studies.

Changes

  • Refactored Index: Updated index.mdx to focus on Enterprise value props.
  • New Architecture Page: Added architecture.md detailing scalability and HA.
  • New Security Page: Added security.md covering compliance (SOC2/HIPAA) and IAM.
  • New Support Page: Added support.md to clearly define paid support tiers vs. community help.
  • New Customization Page: Added customization.md to explain white-labeling and extension boundaries.
  • Partners Page: Created partners.md to funnel Agencies/Resellers away from direct sales pipelines.
  • Customer Stories: Converted the customers folder to use an index.mdx landing page, featuring the Samsung case study and a call-to-action for new stories.
  • Cleanup: Deleted the deprecated _category_.json in the customers folder to support the new index page.

@pr-validator-bot
Copy link

ℹ️ Documentation PR Guidelines

👋 Welcome! This is an automated message posted on all new documentation PRs to help guide our contributors. Just because this comment appeared doesn't mean you have done anything wrong!

Please ensure you're using the correct branches:

Target branch (where you're merging TO):

  • dev branch: For documentation related to upcoming Open WebUI releases (new features, new environment variables, anything dependent on unreleased versions and unreleased features/fixes/changes)
  • main branch: For content that can go live immediately (fixes, tutorials, documentation not dependent on unreleased features)

Source branch (where you're merging FROM):

  • If targeting dev, create your branch from your fork's dev branch
  • If targeting main, create your branch from your fork's main branch
  • ⚠️ Mismatched branches can result in unwanted file changes being included in your PR!

If your docs PR depends on a pending PR in open-webui/open-webui:

  • Convert this PR to DRAFT mode!
  • Link to the related main repo PR in your description for clarity
  • We'll review both together once the PR on the main repo is merged

Please adjust your PR target branch, source branch, and/or draft status accordingly if needed.

Copy link
Contributor

@tjbck tjbck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.

@tjbck tjbck marked this pull request as draft December 25, 2025 17:59
@peetuhr
Copy link
Author

peetuhr commented Dec 27, 2025

Feedback Addressed

Summary of changes:

index.mdx

  • Moved primary CTA ("Let's Talk") above "Why Enterprises Choose Open WebUI"
  • Added "Use Your Work Email" tip with seat count request
  • Added closing CTA ("Ready to Get Started?") at bottom (no qualifier)
  • Removed duplicate lines

architecture.md

  • Updated CTA section: "Planning Your Deployment"
  • Added "Use Your Work Email" tip requesting deployment environment + end user count

security.md

  • Updated CTA section: "Discuss Your Security Requirements"
  • Added "Use Your Work Email" tip requesting compliance requirements + end user count

customization.md

  • Added "Use Your Work Email" qualifier inside the Enterprise License Required info box

support.md

  • Replaced "Email Support" with "Dedicated Support Channels" and reference to Kapa.ai "Support Bot"
  • Removed "Additional Enterprise Services" table
  • Added "Consulting Topics" section framing these as guidance, not deliverables
  • Renamed "Getting Started" → "Find the Right Support Plan"
  • Added "Use Your Work Email" tip requesting team size + support priorities
  • Added softening disclaimer

partners.md

  • Added "Policy on Contribution & Collaboration" warning block
  • Fixed typo (removed artifact [2])

General

  • Consistent CTA format across all pages with page-specific language
  • "Use Your Work Email" qualifier added to all CTAs (except final closing CTA on index)
  • Adopted proper Markdown tooling for consistent formatting and syntax validation
  • Fixed minor formatting inconsistencies throughout

Ready for review! 🚀

@peetuhr peetuhr marked this pull request as ready for review December 27, 2025 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants