Compensated for 2. Text was revised in T27677.

It sounds nice, but I also think that we can run into cumbersome situations w.r.t. package management and version control with this approach: If the web app is located within the package, for each change to the package itself, it has to be investigated how the change affects the web app. The developer also has to adapt and test the web app then. This also means that for each package release, a corresponding web app has to be provided. In my opinion it makes more sense to focus either on the package or the web app during the development. Probably, we want to improve the web app that is based on a fixed package version x most frequently. This use case is then hampered by this approach as the package itself also evolves.

The plot functions that are used in the report have Roxygen documentation now. There's also a vignette called "Visualizations" that shows and explains the plots along with the corresponding plot function.

Thank you for clarification!

I started with the roxygen documentation and found that the NAMESPACE file can be generated automatically by using the "export" tag.

I did not try it yet. Did you? Currently, I don't want to take the risk of breaking my running development environment.

The legend could be moved to the bottom.

What is the issue with the current implementation?

Another solution is to use a numeric input field that does not accept other characters.