mirror of
https://github.com/ggml-org/llama.cpp.git
synced 2026-05-14 13:04:08 +00:00
253ba110bc
* ci: add workflow to publish webui to Hugging Face bucket * ci: add webui release job to release workflow * ci: test webui release job * chore: Return to default minification strategy for build output files * ci: extract webui build into separate workflow and job * chore: Ignore webui static output + clean up references * chore: Delete legacy webui static output * chore: Ignore webui build static output * fix: Workflow * fix: Versioning naming * chore: Update package name * test: Test CI fix * refactor: Naming * server: implement webui build strategy with HF Bucket support * chore: Remove test workflow * chore: Use WebUI build workflow call in other workflows * server: HF Buckets fallback for WebUI build * refactor: App name variable * refactor: Naming * fix: Retrieve loading.html * fix: workflow syntax * fix: Rewrite malformed release.yml * fix: Req param * test: Re-add missing Playwright installation for CI tests * refactor: Logic & security improvements * refactor: Retrieve publishing jobs and DRY the workflows * fix: Test workflow syntax * fix: Upstream Release Tag for test workflow * chore: Remove test workflow * ci: Run WebUI jobs on `ubuntu-24.04-arm` * refactor: Post-CR cleanup Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com> Co-authored-by: Aleksander Grygier <aleksander.grygier@gmail.com> * refactor: CI cleanup * refactor: Cleanup * test: Test workflow * refactor: use LLAMA_BUILD_NUMBER instead of LLAMA_BUILD_TAG for HF Bucket webui downloads * server: add fallback mechanism for HF Bucket webui downloads from latest directory * fix: Incorrect argument order in file(SHA256) calls for checksum verification * refactor: Use cmake script for handling the HF Bucket download on build time * feat: support local npm build for WebUI assets * refactor: add `HF_ENABLED` flag to control WebUI build/download provisioning * refactor: Cleanup * chore: Remove test workflow * fix: remove s390x from release workflow * fix: add webui-build dependency to ubuntu-22-rocm and windows-hip * Revert "fix: remove s390x from release workflow" This reverts commit debcfffa9bc1e3112eae41f2d29741b682e4eb19. * fix: Release workflow file * fix: Proper release tag used for HF Bucket upload * fix: Remove duplicate steps in release workflow --------- Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>
45 lines
1.6 KiB
Plaintext
45 lines
1.6 KiB
Plaintext
import { Meta } from '@storybook/addon-docs/blocks';
|
|
|
|
<Meta title="Introduction" />
|
|
|
|
# llama.cpp Web UI
|
|
|
|
Welcome to the **llama-ui** component library! This Storybook showcases the components used in the modern web interface for the llama-server.
|
|
|
|
## 🚀 About This Project
|
|
|
|
WebUI is a modern web interface for the llama-server, built with SvelteKit and ShadCN UI. Features include:
|
|
|
|
- **Real-time chat conversations** with AI assistants
|
|
- **Multi-conversation management** with persistent storage
|
|
- **Advanced parameter tuning** for model behavior
|
|
- **File upload support** for multimodal interactions
|
|
- **Responsive design** that works on desktop and mobile
|
|
|
|
## 🎨 Design System
|
|
|
|
The UI is built using:
|
|
|
|
- **SvelteKit** - Modern web framework with excellent performance
|
|
- **Tailwind CSS** - Utility-first CSS framework for rapid styling
|
|
- **ShadCN/UI** - High-quality, accessible component library
|
|
- **Lucide Icons** - Beautiful, consistent icon set
|
|
|
|
## 🔧 Development
|
|
|
|
This Storybook serves as both documentation and a development environment for the UI components. Each story demonstrates:
|
|
|
|
- **Component variations** - Different states and configurations
|
|
- **Interactive examples** - Live components you can interact with
|
|
- **Usage patterns** - How components work together
|
|
- **Styling consistency** - Unified design language
|
|
|
|
## 🚀 Getting Started
|
|
|
|
To explore the components:
|
|
|
|
1. **Browse the sidebar** to see all available components
|
|
2. **Click on stories** to see different component states
|
|
3. **Use the controls panel** to interact with component props
|
|
4. **Check the docs tab** for detailed component information
|