Redesign homepage and getting started with seo/geo improvements, wayfinding and brand voice

[peetuhr]

Summary

Overhaul of the homepage and Getting Started/Quick Start section to improve user wayfinding, apply consistent brand voice, and lay groundwork for future visual enhancements.

Changes

Homepage

• Rewrote hero section with clear value proposition.
• Added wayfinding for different deployment methods
• Added "What You Can Do" section highlighting key capabilities
• Elevated privacy/sovereignty messaging throughout
• Added "Free to Use. Built in Public." section combining mission + community
• Refined Enterprise callout with link to full Enterprise section
• Removed redundant content; added forward-linking to many relevant docs

Getting Started

• Added intent-based descriptions for Quick Start, Advanced Topics, and Updating
• Added "What's inside" previews for each section
• Elevated Environment Variables and API Endpoints to Reference section
• Applied brand voice: encouraging, practical, momentum-building

Quick Start

• Added "Choose Your Path" table with time estimates and "Best for" guidance
• Split info boxes: Admin/Roles separate from Privacy/Data Security
• Added "Connect Your Models" section with paths to Ollama, OpenAI, Functions
• Added "Get the Most Out of Your Setup" section (Tailscale, PWA, users)
• Added "Explore What's Possible" forward-links to features
• Condensed tab labels for readability (Compose, Desktop, Swarm, etc.)

Voice & Tone

• Applied brand voice guidelines throughout:
  • Direct over decorative. Warm accents.
  • Honest about complexity
  • Ownership language ("your data," "your rules")
  • Privacy as a feature, (a luxury, even)

Future Work

• Custom card components for visual polish (content-first approach for now)
• Create additional pages (Tailscale tutorial, PWA setup, Voice assistant setup.)

Homepage:

Getting Started:

Quick Start:

[pr-validator-bot]

ℹ️ 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.