Re: CMS 'power' getting started

[Michael Powell]

Hello,

Mentioned before, coming at this from a 'power' user standpoint, with dotnet C++ dev background across platforms, some exposure to Python, familiar with what django is, and competitors i.e. OrchardCore/CMS.

Interested in being CMS productive and eventually also potentially adding tenants/apps to the overall solution.

From the 'power' getting started, what else do I need to know?

* Docker might be a possibility eventually, but not to start.

* Aiming for a postgres backed environment

* Have various Python3 versions installed, the latest is 3.10.2, I think, just now

Also looking for guidance re: project structures, directory layout, editors perhaps, or is a VS Code sufficient, possibly Eclipse, I don't know, that sort of thing.

From OrchardCore/CMS, somewhat familiar with what/how to treat as 'source', from the code behind it all, to the content database(s) themselves, etc, and in potentially multi-author scenarios, with dev/staging/prod phase lines.

Let me know if that makes sense or I can clarify anything getting started.

Thanks!

Michael W. Powell

[MR INDIA]

Django is a web framework not a CMS,  if you want to use a CMS then use wagtail which is a Django based CMS. And Vscode would be sufficient for working with Django. 

If you want many custom features for the CMS then you can use wagtail, as whatever you can do in python you can do in wagtail. 

[MR INDIA]

Django is opinionated so it has a starter directory layout,  you should stick to that. 

[Stu]

Well, they do have the DjangoCMS. I agree though, WagtailCMS is vastly better, in my opinion.