https://github.com/jellyfin/jellyfin-web
Web Client for Jellyfin
https://github.com/jellyfin/jellyfin-web
jellyfin media videos
Last synced: 3 days ago
JSON representation
Web Client for Jellyfin
- Host: GitHub
- URL: https://github.com/jellyfin/jellyfin-web
- Owner: jellyfin
- License: gpl-2.0
- Created: 2019-01-05T14:26:33.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2024-10-29T08:41:39.000Z (4 months ago)
- Last Synced: 2024-10-29T09:56:02.037Z (4 months ago)
- Topics: jellyfin, media, videos
- Language: JavaScript
- Homepage: https://jellyfin.org
- Size: 161 MB
- Stars: 2,367
- Watchers: 41
- Forks: 1,258
- Open Issues: 348
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
- Support: .github/SUPPORT.md
Awesome Lists containing this project
README
Jellyfin Web
Part of the Jellyfin Project
---
Jellyfin Web is the frontend used for most of the clients available for end users, such as desktop browsers, Android, and iOS. We welcome all contributions and pull requests! If you have a larger feature in mind please open an issue so we can discuss the implementation before you start. Translations can be improved very easily from our Weblate instance. Look through the following graphic to see if your native language could use some work!
## Build Process
### Dependencies
- [Node.js](https://nodejs.org/en/download)
- npm (included in Node.js)
### Getting Started
1. Clone or download this repository.
```sh
git clone https://github.com/jellyfin/jellyfin-web.git
cd jellyfin-web
```
2. Install build dependencies in the project directory.
```sh
npm install
```
3. Run the web client with webpack for local development.
```sh
npm start
```
4. Build the client with sourcemaps available.
```sh
npm run build:development
```
## Directory Structure
> [!NOTE]
> We are in the process of refactoring to a [new structure](https://forum.jellyfin.org/t-proposed-update-to-the-structure-of-jellyfin-web) based on [Bulletproof React](https://github.com/alan2207/bulletproof-react/blob/master/docs/project-structure.md) architecture guidelines.
> Most new code should be organized under the appropriate app directory unless it is common/shared.
```
.
└── src
├── apps
│ ├── dashboard # Admin dashboard app layout and routes
│ ├── experimental # New experimental app layout and routes
│ └── stable # Classic (stable) app layout and routes
├── assets # Static assets
├── components # Higher order visual components and React components
├── constants # Common constant values
├── controllers # Legacy page views and controllers 🧹 ❌
├── elements # Basic webcomponents and React equivalents 🧹
├── hooks # Custom React hooks
├── lib # Reusable libraries
│ ├── globalize # Custom localization library
│ ├── legacy # Polyfills for legacy browsers
│ ├── navdrawer # Navigation drawer library for classic layout
│ └── scroller # Content scrolling library
├── plugins # Client plugins
├── scripts # Random assortment of visual components and utilities 🐉 ❌
├── strings # Translation files (only commit changes to en-us.json)
├── styles # Common app Sass stylesheets
├── themes # CSS themes
├── types # Common TypeScript interfaces/types
└── utils # Utility functions
```
- ❌ — Deprecated, do **not** create new files here
- 🧹 — Needs cleanup
- 🐉 — Serious mess (Here be dragons)