Consider creation of a template project, eg similar to Angular (ng new my-app)

[viktor-yunenko]

We have djangocms-installer, but its list of packages is rather simple - https://github.com/nephila/djangocms-installer/blob/develop/djangocms_installer/config/data.py#L79

Ideally we would have the ability to customize the setup, eg to include/exclude features as algolia search, url management, djangocms-styles, etc

I'm also maintaining https://gitlab.com/what-digital/djangocms-template, but it lacks documentation and contains a significant amount of what.digital-specific logic.

[viktor-yunenko]

@macolo, @NicolaiRidani, it seems like another potential workgorup :)

[viktor-yunenko]

I would also like to have the docker version, perhaps even as the default. Although as a macos user I dislike docker quite well, it would simplify community deployments tremendously, and would allow us to announce full support for many modern devops platforms.

[yakky]

i toyed with extending the installer to provide a more open architecture to allow adding any application or bundles
this is a PoC commit nephila/djangocms-installer@d0f6bf6 which has been in part extended here https://github.com/nephila/django-app-enabler
the idea is to have some local or remote json which describe the packages and the settings updates to install a set of package like: djangocms -a blog,search mysite and you have a site with a working djangocms-blog and aldryn-search (or django-cms-internalsearch) up and running

[viktor-yunenko]

That sounds great 👍

One of the goals of mine is to make sure that we can use it at what. for all internal projects, since if we manage to organize it then what. dev team is going to signup for its maintenance 😁

But that imposes a set of requirements that usually I wouldn't put into a template builder. Eg right now djangocms-template is based on webpack 5 with plenty of configuration, which in my opinion a template ideally should either leave out or provide a set of options (rollup, webpack, nothing, etc...). Yet of course in what. projects I would be able to use only the webpack 5 setup.

[viktor-yunenko]

Other internal requirements that I could mention:

• it should be deployable to any docker-based service (eg AWS)
• a working & scalable frontend setup with live reloading (eg webpack5 chunks, bootstrap4/5, scss, typescript, vuejs+ts, fonts, etc)
• allauth user model with the email field as its username, email signup confirmation, etc
• for the search we most certainly need djangocms-algolia with its vuejs integration