should provide disclaimer information

[jonorthwash]

Besides stating the license for the Apertium tools, the main landing page should have a "data statement" that connects the software to the real world (per @emilymbender's recent work).

Types of information that would be good to present (briefly) and/or link to further details on:

• What MT is [good] for, and what it isn't [good] for.
• Sources for data that the pairs were evaluated on.
• Level of involvement or buy-in of the speech communities represented by the various translation pairs (or some statement that all released pairs were the result of native speakers being all or part of the process)
• Perhaps a list of contributors to each language module or pair (in place of a statement on the dialect(s) covered or worse, demographic information on each contributor—we need some balance between transparency and privacy here).
• List of publications, both for more information on background, development, and inner workings of each pair, and for something for people to cite.

Ideally each language module and pair should have metadata on these points (contributor GitHub IDs and for the most part names are currently tracked).

[unhammer]

Maybe when you have a certain pair selected, there could be some ℹ button you can press to read about that specific pair, including data sources, buy-in, and other relevant comments (e.g. for nob→sme, it'd be nice to give some reasons why we don't do sme→nob).

[shrey1608]

It would be a good step IMO, because a beginner as well as an advanced person can get the necessary information directly from the landing page and doesn't have to look around for it . If he wants to contact the contributor it would be easier for him. And i also agree to @unhammer 's view.

[jonorthwash]

an advanced person can get the necessary information directly from the landing page and doesn't have to look around for it .

The problem now is that this information is nowhere. And people have [in many cases understandably] incorrect assumptions or conceptions about MT and potentially what is represented by a given translation system.

[sushain97]

This almost sounds like data that should be fetched at build time from the Wiki. I'm not sure it makes sense to have huge paragraphs of information stored in JSON.