Help release the fastest and smartest django CMS version ever!

django CMS 4 is the next major release. It includes versioning, better ways of managing static content (example: footer or menu), better ways of managing URLs and linking to django CMS URLs and more. The release is already quite progressed, but help is always needed.

Milestones 

Help out at a key point of the django CMS project and contribute immensely to the success of the django CMS open source project.

Reviewing PRs and issues from other contributors according to PR submission guidelines. 

Bring the cutting edge rich text editor to Django CMS community!

At the moment for rich text editing we're using a heavily outdated CKEditor 4, which has a singiifcant amount of UX issues and bugs. We're moving to ES6-based CKEditor framework.

Milestones 

Create and improve django CMS documentation, empowering beginners and advanced users to better understand and resolve issues with django CMS. 

Review documentation. Agree on and document a naming convention for plugin models and classes, General documentation on best practices.

Research multisite features of other frameworks and possible ways of implementing that in django-cms 

Document multisite strategy with Divio, The old way to do multisite was to use a multisite plugin and have all sites in one single instance. Divio has a new, improved way that scales better, by sharing one single database across multiple instances. Each instance uses the same code repository. The site id is controlled via an env var in every instance. This new approach does not require any multisite addons / code, which reduces complexity a lot. 

Implement Github Actions to improve test performance. 

The goal of this temporary work group is to replace Travis CI with Github Action. The team is currently working on migrating a main project, and in the process creating a migration guide so that volunteers can then use the guide to migrate other projects from the django CMS Github organisation. 

Help us to make django CMS compatible with Django 3.2 

This group is newly formed. Current status: Preparing for a django-cms package that is django 3.2 compatible.

This group is ought to coordinate and execute the marketing efforts of the django CMS Association. The group has not been formed yet. If you want to kick start this group, please sign up and receive assistance from the core contributor team. 

The current website is old-fashioned and outdated and could use a new design. A fresh website design can create new momentum and drive overall success of the project. If you want to kick start this group, please sign up and receive assistance from the core contributor team. 

Drop code that we don't need anymore (eg forms without email notificaiton), fix email notifcation UX where user needs to save form before he can add an email notification, allow to send email notification to the user on the Form plugin, not EmailField plugin. Don't allow to break pages by adding Field plugins outside of a Form plugin. Migrate to djangocms-forms

Avoid "video plugin inside video plugin", simplify UI eg by creatin a YouTube plugin and Video plugin (for mp4 and etc files)

Improve UX for responsiveness (bootstrap4 rows / columns), Create a UI widget that has an (even) better interface to control responsiveness, replacing the boostrap4 grid numbers input (i.e. 6 for 'md'). And move some fields to a hidden advanced section.

For some type of plugins, like images, we don't want the plugin to be linked to a specific language. Indeed when a user changes an image in a placeholder, s.he does not expect to have to change it on all languages... The idea is to make the "language" field on the Plugin model not required. And when this field is set to None (cross language plugin), the same instance of plugin is used for all languages.

Unlimited number of frontends; Can be combined with different software languages; More flexible design of the frontend; Continuity through decoupling Dynamic data

User cannot log in locally anymore after login in via SSO password gets removed when user logs in via SSO

Site front-end breaks when previewing published and resizing window When after publishing a page with the structure mode open on desktop, front-end interferes with scroll after window resize (scroll is locked).

Currently requires django-haystack that has been left behind recent Elastic Search changes.

add sub pages for each section. If there are many modules, the page becomes unresponsive, and difficult to manage.

If a plugin on a page has an error the entire page is uneditable.

extend djangocms-transfer to export/import CMS page trees, we also have an existing proposal: https://gitlab.com/what-digital/djangocms-transfer

top CMS bar is accidentially switched to mobile sometimes and doesnt switch back to desktop breakpoint even if the window is wide again

When we drill down to see a page's children, all children are fetched. If a page has several thousands of pages, it can take a long time or even fail. Ideally, we should paginate sub pages and provide a search box. Other Ux are possible.

Follow up on the admin panel simplification that's currently in progress, add a button that clarifies that the user needs to open the page in order to edit the content of a blog

To present the content of several sites under a unique umbrella