Fabian Braun

For the first item: Just having started looking at it the obvious and simple solution might be using a `logger.exception` call which can be configured freely, e.g., send an email...

Thanks for the kind words. I appreciate your interest and contributions!

Sounds like a great idea. For the first representation in the app I have been thinking (but not yet working) on an HTML/CSS only version, i.e. rendering by the browser....

I'd assume that the snippet_fragment will not need access to the context, or will it? If not it can be solved by providing the template tag with its own context...

If this is a potential use case the solution probably involves "popping" the updated context after rendering the content: `context.pop()` to uncover the old `object` context. ``` context.update({'object': instance}) #...

Hi @mavoIn ! The current bottleneck is that the iconpicker js library used (https://github.com/victor-valencia/bootstrap-iconpicker) does not support fontawesome 6 as of now. Sorry to not have better news for now....

Hi @mavoIn ! Since version 1.1 [djangocms-frontend](https://github.com/django-cms/djangocms-frontend) does have an icon plugin that supports fontawesome 6. It includes a migration management command that would automatically upgrade your fontawesome 5 icons...

Closed in favour if #226

Hello @TLuesebrinck ! Thanks very much for the suggestion! Would you be interested in creating a pull request with a fix?

@baravkareknath Thanks for picking this up! Usually projects define their own css/js static files based on Bootstrap or Fomantic. djangocms only provides a starter template that loads a version from...