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

11–20 of 30 posts

Re: Django CMS version 3.3 has been released

#11

Post by lojack »

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 fields and the pages have more consistency then Wagtail is probably better.

The backend of Wagtail is completely geared towards authors, and a lot easier to use in my opinion, and it's got a media library built in. Django-CMS extends the standard django admin backend, may require a third party plugin for a media library, and tends to encourage more frontend editing, so authors will more immediately be able to see how a page looks. It also tends to be more flexible and can do more (which may be a good thing or a bad thing, depending on your goals). If you need more control over permissioning, workflows, etc. then django-cms may be a better choice.

I personally love both of them, and would recommend either.

Re: Django CMS version 3.3 has been released

#12

Post by mkoistinen »

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…

The clunkiness you describe may be because the CMS includes djangocms-admin-styles, which provides a beautiful style- (and behaviour) "sheet" over Django's Admin. Not only does it make admin look nicer, but it also adds touch-capabilities which doesn't really exist in pure Django.

Re: Django CMS version 3.3 has been released

#13

Post by DanieleProcida »

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?

Try them all! They take different approaches, and one might suit you better than another.

django CMS has addon applications for both jobs (Aldryn Jobs) and weblogs (Aldryn News & Blog).

If you're interested, you can join a free Guided Tour each week that will actually cover some how this all works in django CMS: https://www.divio.com/en/academy/aldryn-cloud-django-cms-gui...

For a fully-blown jobs site by the way you'd probably want to expand the Jobs application but it's open source software already so could be a good start.

Re: Django CMS version 3.3 has been released

#15

Post by DanieleProcida »

nkozyra wrote: post #14

Bummer, getting 403s every time I start a demo. The video looks a little non-intuitive and blackboxy in the way pages are built. Is there a WYSIWYG-esque visual layout concept in Django CMS these days?

I think it's a temporary cache-related glitch. Can you try deleting your browser cache, or simply trying again?

It's working for me here, anyway...

Re: Django CMS version 3.3 has been released

#16

Post by nkozyra »

DanieleProcida wrote: post #15
nkozyra wrote: post #14

Bummer, getting 403s every time I start a demo. The video looks a little non-intuitive and blackboxy in the way pages are built. Is there a WYSIWYG-esque visual layout concept in Django CMS these days?

I think it's a temporary cache-related glitch. Can you try deleting your browser cache, or simply trying again? It's working for me here, anyway...

It's a 403 error, so it's probably unlikely it has anything to do with browser cache (but of course possible, though I don't know what Django would need from cookies/webstorage/cache). I did try on another machine in a incognito window and got the same thing 3 times.

Re: Django CMS version 3.3 has been released

#17

Post by DanieleProcida »

nkozyra wrote: post #16
DanieleProcida wrote: post #15

Earlier quoted context omitted.

I think it's a temporary cache-related glitch. Can you try deleting your browser cache, or simply trying again? It's working for me here, anyway...

It's a 403 error, so it's probably unlikely it has anything to do with browser cache (but of course possible, though I don't know what Django would need from cookies/webstorage/cache). I did try on another machine in a incognito window and got the same thing 3 times.

OK, really sorry about that. We're working on it back here, we can definitely see a caching issue somewhere in the pipeline. Would you try once more in incognito mode?

Re: Django CMS version 3.3 has been released

#19

Post by wslh »

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 chose Mezzanine twice because community support works better than the other options (check GitHub issues and the mailing list traffic and feedback). I can't compare them technically side by side but I found easy to extend Mezzanine just looking into Django docs instead of looking at the specific Mezzanine implementation.

One point that put me in doubt in favor of Django CMS was the support for editing single page sections, you can do that in Mezzanine but it is not "native".

Post reply on HN