Description

Regular projects distribute their content through serving pages at their corresponding URL as defined in the page tree. This is achieved by adding path("", include(cms.urls)) to a project's urls.py. Also, the CMS requires CMS_TEMPLATES or CMS_TEMPLATE_DIR to be set.

This PR allows setting up headless-ready projects by:

1. Not requiring path("", include(cms.urls)) being part of the projects URLs. All editing is done in the admin and the edit, structure and preview endpoints.

   The structure endpoint can be used on read-only objects (such as published pages), too, allowing to view the tree and copy plugins. All modifying actions are disabled for read-only objects.

2. Not requiring any templates to be defined. If no templates are available, all interaction runs through the structure endpoint. While the editing experience might be limited, this can be a fast way of setting up a project.

3. This PR moves the create wizard URL to the placeholder admin (which contains all editing endpoints) (but also keeps the previous endpoint in cms.urls for the wizard for compatibility reasons).

4. The data bridge allows the frontend to update the structure board after changes in the plugin tree. This PR changes the HTML response for changes in the plugin tree from inlining the data in a script to a script tag containing JSON objects which are read and passed to the data bridge.

Related resources

• RfC - Headless django CMS via REST API - resolved ✅ #7835
• RfC - make registration of placeholders possible independently from Templates - resolved ✅ #7927

Checklist

• I have opened this pull request against develop-4
• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog
• I have read the contribution guidelines and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.