Currently the documentation live in the github wiki.

The experience with github shows that the wikis got outdated as far as it got created. Another limitation is that contributors can't send a PR to the wiki to update it.

We should move all the documentation in simple markdown file into the repo.

Problem

The TpBot project is becoming quite large with a number of small components that all operate together to make TpBot work. Now would be a good time to show how, from a high level, these components link together.

Solution

Consider using https://github.com/structurizr/java to create an architecture diagram.

Problem

Prior to the hack introduced in v1.1.7 it was possible to receive a NullPointerException when using two instances of Merlin. In issue #163 we stated that we would provide a more comprehensive fix in the future but the current demo does not use multiple instances of Merlin across multiple activities.

Potential Solution

Provide a more comprehensive demo for Merlin s

We should create a wiki page showing the process of performing a release similar to how it is shown on novoda/novoda -> https://github.com/novoda/novoda/wiki/Version-Release-Template

It would be useful to have a task to call the activity manager, so tasks can be written to fire actions on android.

e.g. Launching an action, such as deeplinking to a certain part of your app.

adb shell am start  \
-W \
-a android.intent.action.VIEW  \
-d http://www.thetimes.co.uk/edition/news/some-article

There are should be more info in Violations. It should be added list of Errors and Warnings. Every warning and error has a description, type, file and line in file, where it is located. Then it will be possible to create custom reports. For example, create report to console or Logcat with list of errors and every error will have a link to code with error.

For example,
![image](https://user-im

Problem

We have a lot of public APIs that do not come with any sort of documentation 😭

Potential Solution

Add javadocs for all public APIs with example usages.

Impact

Improve the ease of use of the library.

If the user has not yet accepted the terms and conditions of chrome the snack bar is shown but the url is opened with the fallback navigation.

If the following files:

• CONTRIBUTING.md
• CODE_OF_CONDUCT.md
• SUPPORT.md

are found in your repo, GitHub will automatically link to them when appropriate. Example:

See this repo for examples of these files.

Currently, padding can be added only to the whole landing strip, and not to individual tabs. This padding (more like a margin actually) should work in such a way that the indicator is underlining only the tab text, as in the screenshot below:

<img width="367" alt="screenshot 2017-03-06 10 11 22" src="https://cloud.githubusercontent.com/assets/2426348/23603397/5438f402-0255-11e7-9474-43b5371e92b

Problem

The headings, shown below, whilst useful for Novoda are probably not useful for the average consumer of the webpage. Someone wanting to know about Novodas open source contributions are more likely to want to see examples of where we have done video playback, custom view based libraries, gradle plugins etc.

![screen shot 2017-12-12 at 12 06 50](https://user-images.githubu

when doing this search request is:pr author:eduardb updated:>2016-04-01 on one of our private repo's we get 61 PR's, but on gitHub reports spreadsheet it shows 14

With the current implementation, when no image is available you see a default/placeholder image and then only when you hover you see a name. This isn't very useful as sometimes you see peepz like this:

3 different people with t