Infer config options from existing files

[elwayman02]

When generating a new field-guide, the default config for name, copyright, and github could all be inferred from existing files in the project. For example, the default name can be read from the name property in package.json, the github property can come from repository in package.json, and copyright could be pulled from COPYRIGHT.md. Instead of providing defaults we know will have to be changed, we could proactively provide intelligent defaults that may not need changing!

[mansona]

That's a great idea 🎉

The right place to implement this is in the blueprint index: https://github.com/empress/field-guide/blob/master/blueprints/field-guide/index.js#L43

I think it would be worthwhile just assuming that the files you're talking are available in process.cwd() but we should fall back sensibly if they are missing for some reason i.e. if the smart behaviour fails for whatever reason we have the same functionality as today 👍