search

django-cms / django-cms-mgmt

21 stars 7 forks source link

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

Open viktor-yunenko opened 3 years ago

viktor-yunenko commented 3 years ago

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 commented 3 years ago

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

viktor-yunenko commented 3 years ago

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 commented 3 years ago

i toyed with extending the installer to provide a more open architecture to allow adding any application or bundles this is a PoC commit https://github.com/nephila/djangocms-installer/commit/d0f6bf6685c088b1f9adb89e7a5fb61ed6872738 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 commented 3 years ago

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 commented 3 years ago

Other internal requirements that I could mention: