Should create and configure a second readme for the distribution of the library

[dbfannin]

I wanted to first say thanks for this great tool!

I was wanting to get thoughts on adding a readme to the src directory when initializing a new library, and copying that file over to the dist directory on build (following the same pattern as the package.json). I'm currently doing this as a manual process after I build, and it would be nice to have it automated.

[jvandemo]

@dbfannin — I think that is a great idea 👍

Are you interested in creating a PR for this? Thanks in advance!

[dbfannin]

Sure I can do that!

[dbfannin]

Do you think the route should be to just copy the root readme to the dist directory, or adding a second README to the templates?

[jdjuan]

To keep it simple, I would just leave one. It would be a responsibility of the user to create two sections within it: One for development and another one for usage! 🤓

BTW, @dbfannin thanks for taking thing one! 👍

[jvandemo]

@dbfannin — The generators/app/templates/README.MD file should do. It's already being generated in the root of the generated code. Thanks in advance!

[jvandemo]

Implemented in #85 and released as v10.1.0 👍