Installation instructions unclear #6

The repository is a bit rendundant, which leads to confusion: if one clones it, there is a trident.Rproj environment, but the installation file is not in its namespace. One has to unzip the InstallTrident_1.3.8.zip which contains another environment project. So the environment is nested. That seems a wrong practice to me, because:

1. Storing binary files in a repo is not advised, because they cannot be subject to version control
2. More importantly, the tab Releases contains the binary file for download, generated by GitHub, and therefore not messing up with version control.

If a user only wants the binary to download the file, they should use the files in Releases. Everyone else will clone the repo and then it is confusing why the package is zipped and has a nested environment. This way it is unclear if this a repo of the package source code or of the paper (including the example case studies in the manuscript)?