Vision for djangocms-picture: Centralizing Image Handling, New PictureField, and Multi-Backend Support

[vinitkumar]

Following the recent merge of django CMS 4 support (PR #140), we want to outline the next steps for djangocms-picture and gather community feedback:

Short Term

• Release a new version (4.2.0) to officially deliver django CMS 4 support.

Long Term Vision

• Develop a reusable PictureField and PictureFormField for use in custom models and forms.
• Enable support for multiple image backends (e.g., filer, digital asset management).
• Refactor so that other plugins (like djangocms-frontend) can depend on djangocms-picture for image handling.
• Collect all picture-related functionality in one place for better community support and contribution.

We invite your feedback and ideas!

• What features would you like to see in the new fields?
• What backends do you use or want to use?
• How can we make djangocms-picture the best solution for all image needs in django CMS?

Please join the discussion and help shape the future of this plugin!

@mrbazzan @fsbraun Please have a look and let me know you ideas in this thread.

[fsbraun]

I'd love to have all parameters that go into the <img> template tag to be configurable from one common, reusable PictureFormField:

• Image selection
• Responsiveness (Yes/no)
• Size and Crop area (cover, contain, ...)
• Custom alt text

Exact responsive sizes (i.e., srcsets) can be configured globally, imho.

[fsbraun]

We should also test the new field with Django-filer 4 (or django-finder) by @jrief .

[vinitkumar]

@fsbraun Agreed. Will check and report back!