https://github.com/torchbox/wagtail http://wagtail.io (marketing site) http://www.rca.ac.uk/
This HN no-link-doctrine is really annoying...
Show HN: Wagtail, our new Django CMS
21–30 of 99 posts
Re: Show HN: Wagtail, our new Django CMS
#22So, were you hired to make a site for the RCA and decided to build a CMS first? I'm interested in how this came about.
Yes, sort of. We evaluated the options of sticking with their commercial CMS or switching to a famous open source CMS which we're very familiar with, but we estimated that it would be cheaper to build the site they wanted from scratch in Django. When we'd finished it felt like a lot of the work was reusable, and the RCA kindly agreed to let us open source the project. We've spent the last few weeks extracting it into a standalone package, but there are definitely still some rough edges: documentation, obviously; more tests; i18n.
Re: Show HN: Wagtail, our new Django CMS
#23So, were you hired to make a site for the RCA and decided to build a CMS first? I'm interested in how this came about.
Yes, sort of. We evaluated the options of sticking with their commercial CMS or switching to a famous open source CMS which we're very familiar with, but we estimated that it would be cheaper to build the site they wanted from scratch in Django. When we'd finished it felt like a lot of the work was reusable, and the RCA kindly agreed to let us open source the project. We've spent the last few weeks extracting it into…
This is pretty awesome. A non-PHP CMS is long, long overdue. I know there already are some, but I think the challenge is that non-technical types are still more able to quickly get started by just dragging some PHP into their shared hosting service and turning it on. I hope this will change, and a project like yours is key to making that transition.
Re: Show HN: Wagtail, our new Django CMS
#24Earlier quoted context omitted.
Some of the tests are the default django assert 1 + 1 = 2, but there are quite a few others scattered about the directories.
I wasn't counting the default django 1 + 1 test, but I did find one actual test. It's obvious that a lot of work was put into this, and I think it has potential. My suggestion to the creators is to start with tests from the beginning. However, it's not too late to start now and add tests for everything. It's a lot of work initially, but it will pay off for years to come.
Agreed, proper test coverage is absolutely something we want to achieve. We're working on it as we speak... https://github.com/torchbox/wagtail/blob/master/wagtail/wagt...
- Matt (lead Wagtail dev)
Re: Show HN: Wagtail, our new Django CMS
#25This looks interesting, but I can't take it seriously. From what I can tell, you haven't written any tests at all.
So a CMS that works as the client requires and has a very nice UI can't be taken seriously because it has no tests?
That's a very developer focused mindset.
I'm glad it's been open sourced and I hope to see tests added by them or the community, but it's not a deal-breaker for me.
And if you contribute tests I hope they'll be full functional tests to spot cross-browser regressions, JS breaks and the rest ;)
Re: Show HN: Wagtail, our new Django CMS
#26Seems really good! Are you planning to compare it with other CMS (especially Django-CMS)? I would like to see its performances (with or without varnish). Would you like to add OAuth support or other auth mechanisms like CAS? =) I didn't find documentation for the "WAGTAIL_PASSWORD_MANAGEMENT_ENABLED" option.
Django CMS definitely has more features than Wagtail (and contributors, and impressive example sites). There's a large grid of CMSs and features at https://code.djangoproject.com/wiki/CMSAppsComparison which we haven't added ourselves to yet. We want to resist getting into a CMS feature race - the focus for Wagtail is providing a thoughtful and attractive user interface, and making it as easy as possible for designers to build beautiful sites. As for performance, we haven't done any proper benchmarking, but it feels very fast!
We already support LDAP auth, and CAS and / or Shibboleth is on the roadmap for the near future. More importantly, we'll have proper Sphinx docs soon, with details of the features that are already available.
Re: Show HN: Wagtail, our new Django CMS
#27Why is npm listed as dependency ? Just curious. Congrats on this, it looks awesome.
We currently need npm for lessc, as part of django-compressor, to compile LESS. We want to reduce the dependencies as much as possible, so we're looking into converting to SASS / SCSS, which has a pure-Python compiler, or simply shipping the compiled CSS / JS files for people who don't need to change them. Thanks for the congrats!
SASS or one of its variants (SCSS, Bourbon, Compass) would be lovely!
Re: Show HN: Wagtail, our new Django CMS
#28I did the whole vagrant setup demo thing - this CMS looks unbelievably nice. Kudos to the design team. Stock Django admin (even with Grappelli) is kinda ugly now.
Like others mentioned, a live demo is definitely preferable - not many will go through the vagrant setup.
Also there's a bug when trying to view a sample page:
'embed_filters' is not a valid tag library
But good stuff otherwise!
Re: Show HN: Wagtail, our new Django CMS
#29Seems really good! Are you planning to compare it with other CMS (especially Django-CMS)? I would like to see its performances (with or without varnish). Would you like to add OAuth support or other auth mechanisms like CAS? =) I didn't find documentation for the "WAGTAIL_PASSWORD_MANAGEMENT_ENABLED" option.
Django CMS definitely has more features than Wagtail (and contributors, and impressive example sites). There's a large grid of CMSs and features at https://code.djangoproject.com/wiki/CMSAppsComparison which we haven't added ourselves to yet. We want to resist getting into a CMS feature race - the focus for Wagtail is providing a thoughtful and attractive user interface, and making it as easy as possible for designer…
> We want to resist getting into a CMS feature race - the focus for Wagtail is providing a thoughtful and attractive user interface, and making it as easy as possible for designers to build beautiful sites.
Yes, please keep that focus. A well-focused project is both refreshing and produces extraordinary results. You also appear to have a 'bigger-picture' view than many CMS creators - i.e. on the designers and the people who end up using it, not just the developers.
Congratulations Tom!
Re: Show HN: Wagtail, our new Django CMS
#30I did the whole vagrant setup demo thing - this CMS looks unbelievably nice. Kudos to the design team. Stock Django admin (even with Grappelli) is kinda ugly now. Like others mentioned, a live demo is definitely preferable - not many will go through the vagrant setup. Also there's a bug when trying to view a sample page: 'embed_filters' is not a valid tag library But good stuff otherwise!
oops, hazards of working off a live Git repo there :-) Fixed now - please run a git pull / pip install -r requirements/dev.txt and try again!