A new Django content management system
github.com
A new Django content management system
1–10 of 43 posts
Re: A new Django content management system
#2At work a client wants to use Django CMS, so I considered this as an alternative, but I'm not sure how the modularity of Wagtail compares to Django CMS.
Can someone help me understand why I should prefer one over the other?
Re: A new Django content management system
#3Quite an interesting project, and was already posted by the dev team (with a bunch more resources & info): https://news.ycombinator.com/item?id=7231164
Re: A new Django content management system
#4[deleted]
Re: A new Django content management system
#5Why there is not the demo; I don't evaluate web products which do not provide a demo in their site
Re: A new Django content management system
#6At work a client wants to use Django CMS, so I considered this as an alternative, but I'm not sure how the modularity of Wagtail compares to Django CMS. Can someone help me understand why I should prefer one over the other?
It's not like django-cms or various PHP-based CMS (Conrete5 comes to mind) where a template defines "slots" into which an administrator can drop different type of content widgets. In spirit, it's much more like Mezzanine, where each Page has a particular type and an associated template. Your page is just a Django model, so if you want three areas for text, an image, and a caption, you'll have a model which has three TextFields, a CharField, and an ImageField.
(Having said that, the rich text editor is in Wagtail really is rich and can support inserting images from the image library and links to documents in the document library, as well as oEmbed stuff, so it has some wriggle room).
The two schools of thought ("each page is designed ahead of time with structured content in mind" vs "each page is a collection of content objects") have their adherents. Personally I prefer the Wagtail and Mezzanine approach, but the right answer depends on what the client needs and the nature of your relationship with them.
Re: A new Django content management system
#7Why there is not the demo; I don't evaluate web products which do not provide a demo in their site
There is a demo, you can run it locally using vagrant and it's linked in the README: https://github.com/torchbox/wagtaildemo/ . If you are asking for a hosted demo, then I don't know if there is one but you could always set up your own one on services like OpenShift.
Re: A new Django content management system
#8At work a client wants to use Django CMS, so I considered this as an alternative, but I'm not sure how the modularity of Wagtail compares to Django CMS. Can someone help me understand why I should prefer one over the other?
It's not like django-cms or various PHP-based CMS (Conrete5 comes to mind) where a template defines "slots" into which an administrator can drop different type of content widgets. In spirit, it's much more like Mezzanine, where each Page has a particular type and an associated template. Your page is just a Django model, so if you want three areas for text, an image, and a caption, you'll have a model which has three…
If you are part of the Wagtail team: Can you elaborate a bit on the differences between Mezzanine and Wagtail? On the website it says:
> But having built content-managed websites for 14 years we have strong opinions about the editor experience and how a CMS should work and be structured, and we need to manage a more rapid pace of development than we can achieve by contributing to existing projects.
.. and your editor does in fact look really nice, but what are the structural differences to mezzanine, why is it not just another backend for Mezzanine? That would be a question your landing page or README.md should answer in my opinion. Maybe you could also add Wagtail to the grid on https://www.djangopackages.com/grids/g/cms/ ?
Re: A new Django content management system
#9I have a couple of sites for friends, which I setup ages ago, for which I used Drupal - only because
a) My design skills weren't that great, and I could use a package called Artisteer to create the theme
b) It was a CMS - so my mates could just add content themselves
Now - turns out that the Drupal interface is still a bit confusing for people that don't care for tech. Plus, I'm having to host it on my own server. Can anyone recommend a really simple CMS I could replace it with, preferably for something I could host for free?
Re: A new Django content management system
#10I have a couple of sites for friends, which I setup ages ago, for which I used Drupal - only because a) My design skills weren't that great, and I could use a package called Artisteer to create the theme b) It was a CMS - so my mates could just add content themselves Now - turns out that the Drupal interface is still a bit confusing for people that don't care for tech. Plus, I'm having to host it on my own server. Ca…
I'd recommend Processwire[1]. It's really easy to use any HTML template with it and I personally find it much easier to work with than Drupal. The catch is, by using this or Drupal, you are storing your models on the database and you can't version control a model in a database without getting really creative.