Update tested version of Jellyfin Server to v10.11.10

- This can be configured using css variables
- Rearranged code for better manageability

Co-authored-by: Ahmed Hamdy <AhmedRadwan4@users.noreply.github.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,47 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Checklist**
+- [ ] I have read the README.md 
+- [ ] I have searched through the other open and closed issues using the GitHub search bar
+- [ ] I have made sure that my issue is not a duplicate
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**ElegantFin:**
+ - Version [e.g. 24.12.01]
+
+**Jellyfin Server:**
+ - Version [e.g. 10.10.3]
+
+**Desktop:**
+ - OS: [e.g. Windows]
+ - Browser: [e.g. chrome, safari]
+ - Browser Version: [e.g. 22]
+ - Screen Resolution [e.g. 1920x1080]
+
+**Smartphone or TV:**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser: [e.g. stock browser, safari]
+ - Browser Version: [e.g. 22]
+ - Jellyfin App Version: 
+
+
+**Are you using any plugins or extra CSS configuration**
+- Add any third-party plugins or CSS configuration you use.
+- [e.g. Media Bar, Custom Tabs etc]
+- [e.g. other custom css modifications]

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,36 @@
+# Pull Request
+
+Thanks for contributing to ElegantFin! Please review the **contributor guidelines** before submitting.
+
+## Type of Change
+
+- [ ] Bug fix  
+- [ ] New feature
+
+## Description
+
+Explain what you changed and why. Include your reasoning and goals.
+
+## Screenshots
+
+If applicable, provide before/after images and explain what each shows.
+
+## Cross-platform Testing
+
+Describe how you verified your changes on different devices (desktop, mobile, TV, etc.).
+
+## Test Configuration
+
+- Jellyfin server version:  
+- Jellyfin client:  
+- Client browser name and version:  
+- Device:
+- Other info:
+
+## Checklist
+
+- [ ] I performed a self-review of my own code  
+- [ ] I followed the style conventions (`em` units, minimal media queries).
+- [ ] I avoided unnecessary use of `!important`.
+- [ ] I commented my code where applicable.
+- [ ] I tested my changes on multiple devices, layouts and viewport sizes.

.gitignore

@@ -0,0 +1,2 @@
+/tmp.txt
+/commits.csv

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to ElegantFin
+
+Thank you for your interest in contributing to **ElegantFin**, a custom theme for the Jellyfin Web UI. To keep the project clean, maintainable, and compatible across devices, please follow these guidelines when contributing.
+
+---
+
+## 🧩 Pull Request Guidelines
+
+- **Keep PRs focused.** Each pull request should address a single feature, bugfix, or improvement. Avoid bundling unrelated changes.
+
+- **Write clear PR descriptions.** Explain what you changed and why. This helps reviewers and future contributors understand the purpose and reasoning behind the change.
+
+- **Provide screenshots.** Include before/after screenshots for any visual changes, along with a short description of what each image shows.
+
+- **Comment your code.** If you’re adding new CSS rules or modifying complex ones, include inline comments where needed to describe intent.
+
+- **Don't forget responsiveness.** ElegantFin runs on phones, tablets, TVs, and desktops. Ensure your changes are tested across viewports and don't break layouts or interactions on other platforms.
+
+- **Use consistent units.** Follow the theme’s existing use of relative units such as `em` instead of absolute units like `px`.
+
+- **Avoid `!important`.** Only use it when it is absolutely necessary and no alternative exists.
+
+- **Minimize media queries.** Only add new media queries if there is no simpler or existing solution that achieves the same result.
+
+---
+
+## 💬 Propose First for Major Changes
+
+If you are planning to:
+- change the overall layout or structure of key components,
+- modify the core color scheme,
+- or introduce new UI behavioral patterns,
+
+Please open a GitHub issue first to discuss the proposal with maintainers before submitting a PR. This helps avoid duplicate work and ensures alignment with the project's goals.
+
+---
+
+## 📁 File Structure and Naming
+
+- Follow the existing CSS naming conventions and structure.
+- When adding new sections, group related styles logically and use comments to identify the purpose of the block.
+
+---
+
+## 🤝 Communication
+
+- Be respectful, constructive, and collaborative.
+- Be open to feedback and willing to revise your work if needed.
+
+---
+
+We appreciate your help in making ElegantFin better for everyone. Thanks for contributing! 🙌