Generally speaking, django CMS is wholly frontend-agnostic. It doesn’t care what yoursite’s frontend is built on or uses.
The exception to this is when editing your site, as the django CMS toolbar and editingcontrols use their own frontend code, and this can sometimes affect or be affected byyour site’s code.
The content reloading introduced in django CMS 3.5 for plugin operations (whenmoving/adding/deleting etc) pull markup changes from the server. This may require a JSwidget to be reinitialised, or additional CSS to be loaded, depending on your ownfrontend set-up.
For example, if using Less.js, you may notice that content loads without expected CSSafter plugin saves.
In such a case, you can use thecms-content-refresh event to take care of that, byadding something like:
{%ifrequest.toolbarandrequest.toolbar.edit_mode_active%}<script>CMS.$(window).on('cms-content-refresh',function(){less.refresh();});</script>{%endif%}
after the toolbar JavaScript.