News for hackers. Stuff that matters.
Re:Django CMS version 3.3 has been released by collyw on Thursday June 09, 2016 @11:09AM (#11869876)
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?
Re:Django CMS version 3.3 has been released by lojack on Thursday June 09, 2016 @11:18AM (#11869956)
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 by bennylope on Thursday June 09, 2016 @12:07PM (#11870292)
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 by wslh on Thursday June 09, 2016 @11:56AM (#11870225)
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".

Re:Django CMS version 3.3 has been released by mkoistinen on Thursday June 09, 2016 @11:17AM (#11869943)
I may be biased =) but, I would use django CMS + Aldryn News & Blog, and perhaps Aldryn Jobs to start.

The thing that drew me to django CMS to start with still exists today, which is that django CMS recognizes that Django is a powerful application framework and the CMS embraces this. It also provides powerful front-end editing capabilities for you and your non-technical stakeholders, even for existing Django apps.

Re:Django CMS version 3.3 has been released by DanieleProcida on Thursday June 09, 2016 @11:24AM (#11870002)
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 by holografix on Thursday June 09, 2016 @09:57PM (#11873789)
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.