Description
Heya!
I'm thinking... What about if we just provide users with a CLI that asks for just few questions and on the web - a form that has 1-2 inputs and 1-2 check boxes.
Most of our community and etc stuff is any way on NPM registry, if not on it is on Github, so we can just rely on the given (by user) package name, so we can scrape the needed information like keywords, proper description, proper homepage and github/bitbucket repo, markdown readme and etc. Basically everything, so we can surely generate CDN urls (unpkg [please dont use it], packd or rawgit) to show.
Above is when given library is on the npm registry, otherwise user should pass username/reponame and the path to production file (OR, path to "main" file, so we can use some bundler to provide different builds and urls).
The case when package is on npm registry is absolutely easy and gives a lot of power. Second one is a bit tricky, but not so hard too.