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

Add a template for classic projects #146

Open
pbauer opened this issue Feb 11, 2025 · 1 comment · May be fixed by #148
Open

Add a template for classic projects #146

pbauer opened this issue Feb 11, 2025 · 1 comment · May be fixed by #148

Comments

@pbauer
Copy link
Member

pbauer commented Feb 11, 2025

We want to have as little duplication as possible, so I wonder if it is possible to create a template project_classic that calls the main project template but hides some questions (e.g. volto_version, frontend_addon_name) and changes other settings (e.g. set __feature_headless to "0").

After creating the project a hook could delete the /frontend folder and some files in devops and the main Makefile would need to be replaced.

@davisagli
Copy link
Member

I don't think it's possible the way cookiecutter works currently. The questions are defined in cookiecutter.json which lives inside the template directory. Possibly things could be refactored so that both project templates run a shared subtemplate.

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

Successfully merging a pull request may close this issue.

2 participants