First off — thank you for taking the time to contribute! 🎬
Whether you're fixing a typo, squashing a bug, translating a string, or proposing a new feature, every contribution matters and is genuinely appreciated. PRs are always open - no need to ask first.
This document covers the basics of how things work around here.
Found something broken? Please open an issue and describe what you saw versus what you expected. The more detail you can share (steps to reproduce, browser/OS, screenshots if relevant), the faster we can track it down and fix it.
Have an idea that could make trakt-web better? Start a GitHub Discussion so we can explore it together before anyone writes code. This helps make sure the effort is well-spent and aligns with where the project is headed.
PRs are always welcome - please don't hesitate to open one!
A few guidelines to keep things smooth:
- Bug fixes can be submitted directly as a PR at any time. No prior discussion needed.
- New features or behavioral changes should be discussed in a GitHub Discussion or issue first, just so we're aligned before you invest a lot of time.
- Keep your PR focused — one thing at a time makes review much easier.
- Don't worry about getting it perfect on the first try. We'll work through it together in the review.
Helping make trakt-web available in more languages is a fantastic way to contribute, and no deep technical knowledge is required!
- Find what's missing: Check the
client/i18n/messagesfolder - each language has its own JSON file, and gaps are often obvious. - Add or update translations: Edit the appropriate file with accurate, natural-sounding translations. Context matters - aim for how a native speaker would say it, not a literal word-for-word translation.
- Open a PR: Follow the general PR guidelines above and mention which language(s) you worked on.
We're committed to keeping this a welcoming space for everyone. Please read our CODE_OF_CONDUCT.md — it's simple and sensible.