Adjust landing page to requirements of NAR WSI

[holtgrewe]

Is your feature request related to a problem? Please describe.
There are some requirements that we must fulfill.

Describe the solution you'd like
Check the following points.

Web Servers must:

• be functional on the date of the proposal submission. Access to the server must be through a web browser.
• use the HTTPS protocol and run on the http standard port (443).
• Must provide a cookie consent form when cookies are used.
• include a simple mechanism to try out sample data provided by the authors, for example, a button for automatic loading of the data. Sample data must be accessible to users so that they can confirm data formatting requirements.
• contain help pages and/or a tutorial with links to sample output that performs interactively in the same way as real output. The help pages must include information on how to interpret the results returned by the web server.
• keep every user's submitted data private and not viewable by anyone other than the user or those given permission by the user.
• provide a web link to the results if the website is not able to return results immediately. The link should be provided at the time of data submission and allow the user to bookmark and access the results later. Ideally, the link will report the status of the job (queued, running, or finished). Any request for an email must state that it is optional.
• provide a clear benefit over similar applications or over using R packages.
• provide rich data output (e.g. hyperlinks and visualisations).
• have a free access statement or a licence link on the landing page.

Web Servers must not:

• require users to log in, to register, or to leave an email address unless they handle sensitive human data (see below). Any registration must be optional e.g. for data sharing or access restriction to the user's own data.
• be restricted to a single (or few) species except for humans and common model organisms.
• require excessive data preprocessing with other tools (e.g. by creating Rdata frames) before it can be used.
• cover single steps in the middle of a pipeline.
• be new classifiers which do not produce rich output.
• be mere portals for download or visualisation of static data without the option to analyse user data.
• be updates/enhancements/copies of web servers which have been published within the last two years.
• use Flash and/or Java plugins due to security risks.
• use tracking cookies
• Websites that use a guest login will not be approved.
• Web Servers that handle sensitive human data (e.g. health records or genetic data) may require registration and login. In these cases, users must be able to register themselves without providing their email address. Registration must be handled automatically by the website. Access to non-human data must be possible without registration.

Describe alternatives you've considered
N/A

Additional context
Other TODOs:

• add a note regarding cookies and local storage to the terms of use
• link to that on the login and case editor
• only use the BRCA1 examples for dev

[holtgrewe]

Notes regarding cookies and local storage

• We only use
  • cookie login of users so that is OK, e.g., as explained here: https://law.stackexchange.com/a/94054
  • local storage for storing the case that is also OK as explained above