About composition flexbility

[sveetch]

Almost everything can be switchable from the composed application and structure except for the templates.

We are in 2022 and DjangoCMS + sekizai required tags (cms_toolbar and render_block) cannot be inside a Django template "block" tag, they MUST be directly in HTML without any tags around (spaceless, block, etc..). It's AWFUL.

It forces to insert these tags in the skeleton without any condition or something else. For a CMS site it's ok to have the CMS stuff in skeleton, since the site menu will depend on it and the cms toolbar is almost ok to have everywhere, even in non CMS page.

The only remaining way to condition the CMS usage in templates is to make it from a cookiecutter variable. However this would work only at the project creation stage, once created it can be enabled or disable from composed applications. I don't see yet any proper solution.

Also, there is some project parts which are not ready yet for composition, commonly this is because CMS is involved without conditions but opposed to the sekizai problem, these parts can be managed with composer to make the CMS usage optional.

• CMS, Skeleton and sekizai
• CMS and Initial data
• CMS and tests

[sveetch]

For now the only solution is to keep the really necessarily tags in skeleton and mind to documentate the trick to clean them out of skeleton when CMS is not involved anymore in applications.