Usability, coverage, and maintain metrics for server-side options.

[indolering]

This ticket is inspired by my personal experiences with Mozilla's crappy roll-out of Personas, which relied heavily on community contributions. However, their Wordpress plugin was very poor-quality despite some 17% of all websites being run on Wordpress!

Seamless compatibility with Speech.is requires adding babel.js on the server-side. There are several ways to accomplish this:

• Manually: CDNJS, jsDelivr, Bower, NPM, etc.
• Content Management Systems: Wordpress, Drupal, MediaWiki, etc.
• Content Management Frameworks/Languages: Zend/PHP, Ruby on Rails, Symphony, etc.
• At the hosting level: CPanel, ZPanel, OpenPanel, Dreamhost, HostGator, etc.
• At the server level (via modules?): Apache, NGNX, Microsoft, etc.
• At the DNS level: CloudFlare apps, others?

The idea is to create three metrics for each option:

1. Usability: layman (i.e. hosted Wordpress user), techie (shared hosting/programmer), sysadmin (access to VM).
2. Coverage: 17% of websites run on Wordpress, 50%+ of all sites run on an Apache server, etc. These have to be balanced against actual usage: just because a site runs apache doesn't mean the website owner can add an Apache module.
3. Maintenance difficulty: How hard is it to maintain this solution?

While these metrics will be VERY rough, folding these three metrics into each other should help us maximize our resources to reach the largest possible audience.