enhance Dash boilerplates

[T4rk1n]

With the dash-component-boilerplate, you have to manually replace the name of the component lib. In plotly/dash-component-boilerplate#9, a user suggested we transform the repo in a cookiecutter.

I've looked into it and I think it would be a good fit for the component boilerplate and a dash-app-boilerplate. While it is a command line tool in nature, it allows to be called from Python. This means we can wrap it in our own CLI and have the commands be dash create-component or dash create-app.

@plotly/dash What do you think of this ?

[chriddyp]

That sounds good to me! I would like to hear @bpostlethwaite 's thoughts, as he's always been a strong proponent of "I should be able to just fork this thing and run with it", rather than needing to generate a project from a CLI.

[bpostlethwaite]

I don't mind generating a project from a CLI. I happily use create-react-app for my own things. For the builder archetype specifically I disliked how some configs were linked into the node_modules folder and thought the archetype repo was really difficult to understand.

If the cookiecutter repo looks much more sane than the archetype I'm definitely OK with a "clone, copy && template project info" type CLI.

[valentijnnieman]

I think that's a good idea too. For the dash-component-boilerplate, another option would be to include scripts that do these things (setting name etc) for you, which perhaps makes it a little bit less "magic", and would still allow users to just fork/clone the repo and run with it. Having said that, I think having a great CLI that helps you do all of these things would be a great win for Dash, and would certainly lower the barrier of entry for those new to web development or even to Python.

[byronz]

I was thinking about cookiecutter, and glad found this issue

[erdos2n]

Is this still in Progress? Is there a feature branch for this?