smov/.github/CONTRIBUTING.md

Contributing Guidelines for movie-web

Thank you for investing your time in contributing to our project! Any contribution you make will be reflected on movie-web.app.

Please make sure you read our Code of Conduct to keep our community approachable and respectable.

Contents

• New Contributor Guide
• Requesting a feature or reporting a bug
  • Discord Server
  • GitHub Issues
• Before you start
• Contributing
  • Recommended Development Environment
  • Tips
  • Language Contributions

New contributor guide

To get an overview of the project, read the README. Here are some resources to help you get started with open source contributions:

• Finding ways to contribute to open source on GitHub
• Set up Git
• GitHub flow
• Collaborating with pull requests

Requesting a feature or reporting an bug

There are two places where to request features or report bugs:

• GitHub Issues
• The movie-web Discord server

Discord Server

If you do not have a GitHub account, or would like to discuss a feature or bug with us before making an issue, you can join our Discord server.

GitHub Issues

To make a GitHub issue for movie-web, please visit the new issue page where you can pick either the "Bug Report" or "Feature Request" template.

When filling out an issue template, please make sure to include as much detail as possible and include any screenshots or console logs as appropriate.

After an issue is created, it will be assigned either the https://github.com/movie-web/movie-web/labels/bug or https://github.com/movie-web/movie-web/labels/feature label, along with https://github.com/movie-web/movie-web/labels/awaiting-approval. One of our maintainers will review your issue and, if it's accepted, will assign the https://github.com/movie-web/movie-web/labels/planned label.

Before you start!

Before starting a contribution, please make your contribution is part of an open issue on our issues page.

GitHub issues are how we track our bugs and feature requests that will be implemented into movie-web - all contributions must have an issue and be approved by a maintainer before a pull request can be worked on.

If a pull-request is opened before an issue is created and accepted, you may be at risk of having your pull request rejected! Always check with us before starting work on a feature - we don't want to waste your time!

Note

The exception to this are language contributions, which are discussed in this section

Also, make sure that the issue you would like to work on has not been got the "awaiting-approval" label by a maintainer. Otherwise, if we reject the issue it means your work will have gone to waste!

Contributing

If you're here because you'd like to work on an issue, amazing! Thank you for even considering contributing to movie-web, it means a lot ❤️

Firstly, make sure you've read the Before you start! section!

When you have found a GitHub issue you would like to work on, you can request to be assigned to the issue by commenting on the GitHub issue.

If you are assigned to an issue but for whatever reason can't complete it, no problem! Just let us know and we will open up the issue to have someone else assigned.

Recommended Development Environment

Our recommended development environment to work on movie-web is:

• Visual Studio Code
• ESLint Extension

Our project is setup to enforce formatting and code style standards using ESLint.

Tips

Here are some tips to make sure that your pull requests are 🤌 first time:

• KISS - Keep It Simple Soldier! - Simple code makes readable and efficient code!
• Follow standard best practices for TypeScript and React.
• Keep as much as possible to the style of movie-web. Have a look round our codebase to familiarise yourself with how we do things!
• Make sure to take note of the ESLint errors and warnings! Do not ignore them! They are there for a reason.
• Test, test, test! Make sure you fully test the features you are contributing.

Language Contributions

Language contritions help movie-web massively allowing people from all across the world to use our app!

Like most apps, our translations are stored in .json files. Each language string has a unique key (For example, notFound.genericTitle) which references a language string in the appropriate language file.

Each language file is called translation.json and are stored in the src/setup/languages/<language code>/ folder. For example, the English language file is located at src/setup/languages/en/translation.json.

Warning

Before you start a translation, please check:

• That there isn't an existing GitHub issue or pull request open for that language.
• That we aren't in the middle of a new feature update! When releasing major versions, we don't accept language until the new version is complete otherwise the language files would be outdated.

Please speak to us before starting a language PR. We don't want to waste your time.

To make a translation:

• Copy the en folder inside the src/setup/languages folder
• Rename the copied folder to the 2 letter code for the country/language you are translating to.
  • Click this link to see a list of codes. Make sure to use the codes in the 639-1 column!
  • For example, Arabic is ar
• Edit the language strings inside the translation.json file
  • Do not edit the keys, only edit the values.
  • e.g. in "stopEditing": "Stop editing", - only change the Stop editing part, not the stopEditing part.
• In the src/setup/i18n.ts file:
  • Import your new translation file, e.g. import ar from "./locales/ar/translation.json";
  • Add your translation to the locales object (Look at other languages for an example)

Once you have made your translation, please open a pull request. We do not accept partial translations so please make sure every language string is translated to the intended language.