Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django CMS version 3.3 has been released

django-cms.org

Post reply on HN
Print view View original

21–30 of 30 posts

Re: Django CMS version 3.3 has been released

#21

Post by DanieleProcida »

rdudek wrote: post #18

How's the security of django compared to other CMS'es?

Django takes security extremely seriously: https://docs.djangoproject.com/en/1.9/topics/security/.

Any Django application that follows good practices and doesn't do anything daft will inherit those security benefits.

Django doesn't permit overwriting of its own program files for update procedures, for example, which some systems to.

(A CMS is by nature slightly more vulnerable, because of the potential for mishandling user-submitted content.)

Re: Django CMS version 3.3 has been released

#22

Post by bennylope »

lojack wrote: post #11
collyw wrote: post #7

Anyone got any advice on Django-CMS vs Wagtail vs Mezzanine? We want to build a job site with a blog component. Any reason to choose or not choose any of them?

Can't weigh in on Mezzanine, and haven't built a site in any in over a year so things may have changed, but the big difference between Django-CMS and Wagtail come down to how your content is modeled. If you're looking to have a page with a variety of widgets that can be mixed and matched, then Django-CMS is probably more suited. If you've got a structured page where your users are going to be filling in predefined fi…

I've used both as well and this perfectly crystallizes my thoughts on them. Integrating custom models felt a bit more cumbersome in Wagtail but I've mostly chalked that up to my own experience gap between the two CMSs.

Re: Django CMS version 3.3 has been released

#23

Post by rdudek »

DanieleProcida wrote: post #21
rdudek wrote: post #18

How's the security of django compared to other CMS'es?

Django takes security extremely seriously: https://docs.djangoproject.com/en/1.9/topics/security/ . Any Django application that follows good practices and doesn't do anything daft will inherit those security benefits. Django doesn't permit overwriting of its own program files for update procedures, for example, which some systems to. (A CMS is by nature slightly more vulnerable, because of the potential for mishandli…

Nice, I may have to check this out. I'm looking to setup a small site for myself with a blog and security always worries me if I look at things like Wordpress.

Re: Django CMS version 3.3 has been released

#24

Post by scotu »

rdudek wrote: post #18

How's the security of django compared to other CMS'es?

be careful not to confuse Django the framework (which is not a cms) with Django-CMS the cms built on top of Django the framework by a different set of people. I cannot comment on the security of django-cms because I didn't look into it but Django the framework tends to be "secure by default" i.e. has defaults that enforce csrf protection and other security best practices.

Re: Django CMS version 3.3 has been released

#27

Post by bigmanwalter »

andybak wrote: post #8

We've always had our own hand-rolled CMS in Django (mainly because Django CMS didn't exist when I started). Last time I looked at Django-CMS I found the UX of the admin to be a bit clunky - especially as something I'd want to give to clients and their staff. (Bear in mind I find Wordpress admin to be unbearably clunky too) Just too many things on screen that would require an explanation, a "don't touch that or a "you…

I've just spent months research different CMS alternatives and I've found vanilla Django to be far more pleasurable to work with than any of the add ons. Most of my clients can't be trusted to pick their own URL structures or deal with unnecessary buttons in the back end. Django gives me full control :)

Re: Django CMS version 3.3 has been released

#28

Post by holografix »

collyw wrote: post #7

Anyone got any advice on Django-CMS vs Wagtail vs Mezzanine? We want to build a job site with a blog component. Any reason to choose or not choose any of them?

I'd back Wagtail. I had a look at both Mezzanine and Dj CMS a while ago and was relieved when I stumbled on Wagtail. Much flatter learning curve and the then recently introduced Streamfield was super helpful.

Doesn't hurt that it looks awesome as well.

Re: Django CMS version 3.3 has been released

#29

Post by andybak »

bigmanwalter wrote: post #27
andybak wrote: post #8

We've always had our own hand-rolled CMS in Django (mainly because Django CMS didn't exist when I started). Last time I looked at Django-CMS I found the UX of the admin to be a bit clunky - especially as something I'd want to give to clients and their staff. (Bear in mind I find Wordpress admin to be unbearably clunky too) Just too many things on screen that would require an explanation, a "don't touch that or a "you…

I've just spent months research different CMS alternatives and I've found vanilla Django to be far more pleasurable to work with than any of the add ons. Most of my clients can't be trusted to pick their own URL structures or deal with unnecessary buttons in the back end. Django gives me full control :)

This is one of the other reasons for hand-rolling our CMS - we got to control url structure, page layout, lock down WYSIWYG editing to just the required features (no, you can't have green text!) and countless other things.

The job of a client-facing CMS is NOT to be a flexible general purpose web editor - it's to allow the client to edit their content and enforcing enough constraints that it's hard for them to ruin their nice shiny new web site. :) (if any of my clients are reading - I know you would never do such a thing)

Re: Django CMS version 3.3 has been released

#30

Post by bigmanwalter »

andybak wrote: post #29
bigmanwalter wrote: post #27

Earlier quoted context omitted.

I've just spent months research different CMS alternatives and I've found vanilla Django to be far more pleasurable to work with than any of the add ons. Most of my clients can't be trusted to pick their own URL structures or deal with unnecessary buttons in the back end. Django gives me full control :)

This is one of the other reasons for hand-rolling our CMS - we got to control url structure, page layout, lock down WYSIWYG editing to just the required features (no, you can't have green text!) and countless other things. The job of a client-facing CMS is NOT to be a flexible general purpose web editor - it's to allow the client to edit their content and enforcing enough constraints that it's hard for them to ruin t…

Glad to see I'm on the right track :) I spent too long figuring out that WordPress and Drupal are terrible, and then it took a while for me to find Django. Very little written out there about using Django to build brochureware.

If you don't mind me asking, could you write up a list of all the django apps and python packages that help the most in your projects? I'm new to the ecosystem and picking it up as fast as I can but there's only so many hours in the day. Obviously, I've chosen to do this live in the middle of a contract so it's sorta eating me alive.

Also, I'll take this chance make my short pitch: If you're ever looking for some extra hands on a project, I'm currently looking for freelance work. I do full stack. New to django, but very experienced with MVC frameworks and I'm quite excellent with frontend javascript. I can even hold my own when it comes to design and selecting stock photos :) e@ericwaldman.ca

Post reply on HN