Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need cookiecutter? #12

Open
adrn opened this issue Dec 12, 2019 · 0 comments
Open

Do we need cookiecutter? #12

adrn opened this issue Dec 12, 2019 · 0 comments

Comments

@adrn
Copy link
Contributor

adrn commented Dec 12, 2019

👋 I'm just starting to look through some of the code here with the eventual goal of replacing the astropy-tutorials build machinery with nbpages. I'm confused about the current design. It looks like the current setup procedure for a new repository that will depend on nbpages is to use cookiecutter to copy over relevant code from nbpages and set up a directory structure to put the notebooks in. Is this really necessary? I would find it more natural to allow the user to structure their notebooks however they want, install nbpages as a package, and run, e.g.,:

nbpages build path/to/my/notebooks --output-dir=path/to/website/root

or something like that.

Could someone clarify the design decision here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant