Readme is out of date with current templates

[el1f]

First of all, congrats on the great project!
I've started using it a couple of days ago but I've now started to bump onto some very big hurdles due to the fact that the Readme and all of the currently available documentation is scattered across several docs, the micro bundle project and so on.
I'm afraid this issue will end up being kind of redundant but I was unable to find anywhere else where you were able to address whether you're planning on updating the readme to reflect the current file structure, operating stack, and various configuration use cases.

Kudos on the hard work!

[transitive-bullshit]

Hey @el1f, thanks for the feedback.

What if we added an additional template that supported rollup+babel with full control?

I still believe that microbundle should be the default as it works and is easier to maintain for the majority of expected use cases, but at least this would give an option to opt into more flexibility (and complexity) if desired?

Related #232 #226 #225 #223 and #221

[el1f]

A rollup+babel version that's somewhat able to iterate over what has been made up until v2 would probably serve a lot of people well when it comes to supporting their open projects and making use of the wealth of information that's already available for fixing common issues. On the other hand, if we want to get people to adopt v3 while having an easier time there's probably a discussion to be had on how to better lead them to solutions for their most common problems (#232 seems like a good example of something that the majority of use cases could require)