refactor: Started on the item screen

Also aligned repo with the others

Author: TriPSs

.commitlintrc.js

@@ -0,0 +1,13 @@
+module.exports = {
+  extends: [
+    '@commitlint/config-conventional',
+  ],
+
+  rules: {
+    'subject-case': [
+      2,
+      'always',
+      'sentence-case',
+    ],
+  },
+}

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,17 @@
+## Expected Behavior
+
+
+## Actual Behavior
+
+
+## Steps to Reproduce the Problem
+
+  1.
+  1.
+  1.
+
+## Specifications
+
+  - Version:
+  - Platform:
+  - Subsystem:

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,7 @@
+Fixes #
+
+## Proposed Changes
+
+  -
+  -
+  -

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,5 @@
+module.exports = {
+  hooks: {
+    'commit-msg': 'commitlint -E HUSKY_GIT_PARAMS',
+  },
+}

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,5 @@
+# Change log
+
+All notable changes to this project will be documented in this file. See
+[standard-version](https://github.com/conventional-changelog/standard-version)
+for commit guidelines.

.github/home-bottom.png

@@ -1,46 +1,74 @@
 # Contributor Covenant Code of Conduct
 
+ - [Our Pledge](#our-pledge)
+ - [Our Standards](#our-standards)
+ - [Our Responsibilities](#our-responsibilities)
+ - [Scope](#scope)
+ - [Enforcement](#enforcement)
+ - [Attribution](#attribution)
+
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age,
+body size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual
+identity and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+Examples of behavior that contributes to creating a positive environment
+include:
+ - Using welcoming and inclusive language
+ - Being respectful of differing viewpoints and experiences
+ - Gracefully accepting constructive criticism
+ - Focusing on what is best for the community
+ - Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+ - The use of sexualized language or imagery and unwelcome sexual attention or advances
+ - Trolling, insulting/derogatory comments, and personal or political attacks
+ - Public or private harassment
+ - Publishing others' private information, such as a physical or electronic address, without explicit permission
+ - Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event. Representation of a
+project may be further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at `email` or in [Gitter](https://gitter.im/pct-org/Lobby). The
+project team will review and investigate all complaints, and will respond in a
+way that it deems appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an
+incident. Further details of specific enforcement policies may be posted
+separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4,
+available at http://contributor-covenant.org/version/1/4

.github/home.png

@@ -0,0 +1,124 @@
+# Contributing
+
+So you're interested in giving us a hand? That's awesome! We've put together
+some brief guidelines that should help you get started quickly and easily.
+
+There are lots and lots of ways to get involved, this document covers:
+ - [Raising Issues](#raising-issues)
+   - [Report  A Bug](#report-a-bug)
+   - [Feature Requests](#feature-requests)
+   - [Pull Requests](#pull-requests)
+ - [Commit Messages](#commit-messages)
+ - [Styleguides](#styleguides)
+   - [JavaScript Styleguide](#javascript-styleguide)
+   - [Tests Styleguide](#tests-styleguide)
+   - [Documentation Styleguide](#documentation-styleguide)
+ - [Setting up for development](#setting-up-for-development)
+   - [Yarn scripts](#yarn-scripts)
+   - [Git hooks](#git-hooks)
+
+## Raising Issues
+
+If you're about to raise an issue because you think that you've found a problem
+with the application, or you'd like to make a request for a new feature in the
+codebase, or any other reason… please read this first.
+
+The GitHub issue tracker is the preferred channel for
+[bug reports](#report-a-bug), [feature requests](#feature-requests), and
+[pull requests](#pull-requests) but respect the following restrictions:
+
+* Please **do not** use the issue tracker for personal support requests.
+* Please **do not** derail or troll issues. Keep the discussion on topic and
+respect the opinions of others.
+
+### Report A Bug
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+1. **Use the [GitHub Issues search]** — check if the issue has already been
+reported.
+2. **Check if the issue has been fixed** — try to reproduce it using the
+latest `master` or look for [closed issues].
+3. **Include a screencast if relevant** - Is your issue about a design or front
+end feature or bug? The most helpful thing in the world is if we can *see* what
+you're talking about. Just drop the picture after writing your issue, it'll be
+uploaded and shown to the developers.
+3. Use the Issue tab on GitHub to start [creating a bug report].
+A good bug report shouldn't leave others needing to chase you up for more
+information. Be sure to include all the possible required details and the steps
+to take to reproduce the issue.
+
+### Feature Requests
+
+Feature requests are welcome. Before you submit one be sure to:
+1. **Use the [GitHub Issues search]** and check the feature hasn't already been requested.
+2. Take a moment to think about whether your idea fits with the scope and aims
+of the project, or if it might better fit being an app/plugin.
+3. Remember, it's up to *you* to make a strong case to convince the project's
+leaders of the merits of this feature. Please provide as much detail and
+context as possible, this means explaining the use case and why it is likely to
+be common.
+4. Clearly indicate whether this is a feature request for the application
+itself, or for packages like Providers, Metadatas, or other.
+
+### Pull Requests
+
+Pull requests are awesome. If you're looking to raise a PR for something which
+doesn't have an open issue, please think carefully about
+[raising an issue](#report-a-bug) which your PR can close, especially if you're
+fixing a bug. This makes it more likely that there will be enough information
+available for your PR to be properly tested and merged. To make sure your PR is
+accepted as quickly as possible, you should be sure to have read all the
+guidelines on:
+
+* [Commit Messages](#commit-messages)
+
+## Commit Messages
+
+This project uses the [Conventional Commits](https://conventionalcommits.org/)
+convention. If you are not familiar with this convention please read about it
+first before creating a commit message or a PR.
+
+### Documentation Styleguide
+
+ * Use [Markdown](https://daringfireball.net/projects/markdown).
+ * Reference methods and classes in markdown with the custom `{}` notation:
+   * Reference classes with `{ClassName}`
+   * Reference instance methods with `{ClassName.methodName}`
+   * Reference class methods with `{ClassName#methodName}`
+
+## Setting up for development
+
+Each repo has it's own _Setting up for development_, read that closely before creating new tickets.
+
+### Yarn scripts
+
+The following yarn scripts are available in all repo's in order to help you with the
+development of the project. See the README's of the projects for the project specific scripts.
+
+```
+ $ yarn build       # Create production build of the project
+ $ yarn coveralls   # Upload code coverage to Coveralls
+ $ yarn start:debug # Run the applicaiton in debug mode
+ $ yarn start:dev   # Run the applicaiton in development mode
+ $ yarn lint        # Check linting on the project
+ $ yarn lint:fix    # Fix liting on the project
+ $ yarn test        # Run unit tests of the project
+ $ yarn test:watch  # Run unit tests in watch mode
+```
+
+### Git hooks
+
+The following `git` hooks are available to ensure the changes you are about to
+make follow the [styleguides](#styleguides) and make sure your changes pass the
+tests.
+
+```
+commit-msg          # Checks commit messages
+```
+
+[GitHub Issues search]: https://github.com/popcorn-official/popcorn-api/issues
+[closed issues]: https://github.com/pct-org/getting-started/issues?q=is%3Aissue+is%3Aclosed
+[creating a bug report]: https://github.com/pct-org/getting-started/issues/new

.github/movie.png

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018 Tycho Bokdam
+Copyright (c) 2019 Popcorn Time
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal