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.
|2022 Q1||2022Q2||2022 Q3||2022 Q4|
|alias clean up|
This work group is dedicated to monitoring and resolving issues raised on Github. The work ranges from setting the correct labels to resolving the issues. By working on this team, you will provide core support to the project and be instrumental in delivering a positive user experience.
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.Join
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.
|2021 Q1||2021 Q2||2021 Q3||2021 Q4|
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.Join
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.Join
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.Join
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.Join
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.Join
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.
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-formsJoin