Skip to content

Conversation

@Chesars
Copy link
Contributor

@Chesars Chesars commented Jan 19, 2026

Relevant issues

Improves documentation discoverability for non-technical users.

Pre-Submission checklist

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - N/A (docs only change)
  • My PR passes all unit tests on make test-unit - N/A (docs only change)
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

📖 Documentation

Changes

Moved the "Admin UI" section from inside "LiteLLM AI Gateway (Proxy)" to a top-level sidebar entry renamed as "UI Dashboard".

Why? The UI Dashboard is a great feature for non-technical users and management, but it was hard to discover because it was nested 2 levels deep inside the Proxy documentation. Users had to know to look under "LiteLLM AI Gateway (Proxy)" → "Admin UI" to find it.

Before:

├── LiteLLM AI Gateway (Proxy)
│   ├── ...
│   ├── Admin UI
│   │   ├── Quick Start
│   │   └── ...

After:

├── LiteLLM AI Gateway (Proxy)
├── UI Dashboard
│   ├── Quick Start
│   └── ...
├── Supported Endpoints

This makes the UI documentation much more accessible for users who want to manage LiteLLM through the web interface without diving into technical proxy docs.

The Admin UI section was nested inside "LiteLLM AI Gateway (Proxy)" making it
hard to find for non-technical users. Moving it to top-level as "UI Dashboard"
improves visibility and accessibility.
@vercel
Copy link

vercel bot commented Jan 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
litellm Ready Ready Preview, Comment Jan 20, 2026 10:21pm

Request Review

@krrishdholakia
Copy link
Contributor

isn't this confusing, as the UI is for the proxy, not shared across sdk + proxy?

@Chesars
Copy link
Contributor Author

Chesars commented Jan 20, 2026

You're right, the UI is served by the proxy as a static Next.js build (the "frontend" for the proxy).

Options:

  1. Keep it at top-level or/and rename to "Proxy UI Dashboard" to clarify the relationship
  2. Move it back under Proxy but make it more prominent (first item)

The goal is discoverability for non-technical users. Wdyt? I opened this PR also because I find the UI just a couple of weeks ago.

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.

2 participants