-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to Django-CMS #581
Conversation
0bda414
to
398c808
Compare
Codecov Report
@@ Coverage Diff @@
## develop #581 +/- ##
===========================================
- Coverage 96.76% 96.17% -0.60%
===========================================
Files 554 564 +10
Lines 19602 19795 +193
===========================================
+ Hits 18968 19037 +69
- Misses 634 758 +124
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed together with Bart, wish is to keep the Django admin style as-is (a la AFS setup) while integration Django CMS (but Bart did this on-the-fly so seems doable).
1fa0b3b
to
b62b6b8
Compare
3cd78ff
to
f2370d5
Compare
@@ -49,6 +49,17 @@ playwright | |||
django-yubin | |||
django-image-cropping | |||
|
|||
# django cms | |||
django-cms | |||
djangocms-text-ckeditor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for now disable djangocms-text/link/file/picture
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be merged, however a few remarks:
- lets remove the djangocms-x plugins for now before merging (to avoid having to style these properly, it'll be quite a bit of work)
- the 'fixed' home-templates are commentted out (which is useful for the transition but will need to be cleaned up later)
- See what's possible with a django cms fixture, but that can be done after merging on the testenvironment. Alternatives would be to use a wizard or setting up the various environments manually.
This installs a basic functional django-cms, using the regular templates.
This as a development basis to start building out and migrating existing apps and features to apphooks and plugins.
For now all new elements have a very ugly CSS style and outline (like the dynamic menu).
The existing homepage is moved to /oldhome so we can have django-cms as root in the url router. This also means url-resolving and reversing is a bit borky as existing urls take precedence.
(this also breaks dajngo-admin-index layout so that is disabled for now)