@@ -66,8 +66,8 @@ projects, this is often not the case.
66
66
67
67
** Limitations and considerations in headless mode:**
68
68
69
- - Inline editing and content preview are currently only available in a structured view. (Solutions
70
- are currently being evaluated) .
69
+ - Inline editing and content preview are available as JSON views on both edit and preview mode. Turn
70
+ JSON rendering on and of using the ` REST_JSON_RENDERING ` setting .
71
71
- Not all features of a standard Django CMS are available through the API (eg. templates and tags).
72
72
- The API focuses on fetching plugin content and page structure as JSON data.
73
73
- Website rendering is entirely decoupled and must be implemented in the frontend framework.
@@ -140,12 +140,15 @@ class CustomHeadingPluginModel(CMSPlugin):
140
140
Yes, djangocms-rest provides out of the box support for any and all django CMS plugins whose content
141
141
can be serialized.
142
142
143
+ Custom DRF serializers can be declared for custom plugins by setting its ` serializer_class ` property.
143
144
144
145
## Does the TextPlugin (Rich Text Editor, RTE) provide a json representation of the rich text?
145
146
146
147
Yes, djangocms-text has both HTML blob and structured JSON support for rich text.
147
148
148
- URLs to other CMS objects are dynamic, in the form of ` <app-name>.<object-name>:<uid> ` , for example
149
+ URLs to other Django model objects are dynamic and resolved to API endpoints if possible. If the referenced model
150
+ provides a ` get_api_endpoint() ` method, it is used for resolution. If not, djangocms-rest tries to reverse ` <model-name>-detail ` .
151
+ If resolution fails dynamic objects are returned in the form of ` <app-name>.<object-name>:<uid> ` , for example
149
152
` cms.page:2 ` . The frontend can then use this to resolve the object and create the appropriate URLs
150
153
to the object's frontend representation.
151
154
0 commit comments