Fix: Removed the bottom border from the last row in the credits box

dev: TVs don't have Dashboard settings, so TV users were unable to check the version they were running. Also, in future dashboard theming might not be allowed, so I needed a different place to show the version number for debugging purposes.

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

.github/pull_request_template.md

@@ -1,28 +0,0 @@
-# Description
-
-Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
-
-Fixes # (issue)
-
-## Type of change
-
-- [ ] Bug fix
-- [ ] New feature 
-
-# How Has This Been Tested?
-
-Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
-
-**Test Configuration**:
-* Jellyfin server version:
-* Jellyfin client:
-* Client browser name and version:
-* Device:
-
-# Checklist:
-
-- [ ] I have performed a self-review of my own code
-- [ ] I have commented my code in hard-to-understand areas
-- [ ] I have included relevant comparison screenshots where nececssary
-- [ ] I have tested my changes on the TV layout and Default layout of Jellyfin
-- [ ] I have also tested my changes on multiple devices and screen sizes

.gitignore

@@ -1 +1,2 @@
-/tmp.txt
+/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! 🙌