Wow, this is really beautiful. Just in time for my next project: a tiny ERP to manage my sister's bakery. Thanks for open sourcing this. :)
Please let us know if you end up using it. We'll post a Wagtail t-shirt to your sister's bakery!
Show HN: Wagtail, our new Django CMS
61–70 of 99 posts
Re: Show HN: Wagtail, our new Django CMS
#62Does it support handling multiple sites? If not, do you have any plans for adding multi site feature?
Re: Show HN: Wagtail, our new Django CMS
#63Very nice! Thanks for the good work! Will check it out. Feedback: I hope for some good documentation like a starter tutorial and video screencast so more people can understand your CMS and use it.
Thanks! In case you missed it elsewhere there's a tutorial by Wagtail contributor Serafeim Papastefanos here: https://gist.github.com/tomdyson/8974456 but we're working hard on official docs and a proper screencast.
> To follow this tutorial you will need to have Python 2.7 installed with a working version of pip and virtualenv.
Is that true in general for this CMS, that Python 2.7 will be needed? Python 3 isn't supported?
Re: Show HN: Wagtail, our new Django CMS
#64Earlier quoted context omitted.
Developer docs: currently https://github.com/torchbox/wagtaildemo/blob/master/README.m... and this tutorial from contributor Serafeim Papastefanos: https://gist.github.com/tomdyson/8974456 Clearly this isn't enough and we're working on proper Sphinx docs which should be ready in the next few days. Extensibility: it's just a Django app, so you can include it in your existing project, or add your own apps / views / mid…
That looks interesting. I've got a CMS which shares some philosophical similarities to Wagtail. It's a lot clunkier and uglier though. I wish I had the time to add some polish. I think the 'pages have types' idea is spot on and something all the other Django CMS's I've seen seem to get wrong. (too much freedom for the user to create 'Frankenstein pages' by arbitrarily combining blocks). The editor and image library i…
Thank you very much for your thoughtful feedback. We're pleased with the UI but obviously it's not perfect - I've just started using slack.com which is also pretty flat but feels like a new benchmark for usability. I'll discuss it with the design team, and if you have any more specific feedback we'd love to hear it.
There are still a couple of Wagtail features which rely on contrib.admin. We have to decide whether to smarten up the contrib.admin UI or pull them into the Wagtail admin. Is your CMS available somewhere public?
Re: Show HN: Wagtail, our new Django CMS
#65Frameworks on frameworks on frameworks.
Whats wrong with that?
Re: Show HN: Wagtail, our new Django CMS
#66Does it support handling multiple sites? If not, do you have any plans for adding multi site feature?
Yes, multiple sites are supported - there's a single tree for all pages in the system, and any number of sites can be 'rooted' at different points in the tree. (Currently this is configured in Django's own admin interface, but we'll be moving this into the Wagtail interface proper.)
Re: Show HN: Wagtail, our new Django CMS
#67Would you gents (upstream wagtail guys) be interested if I took a shot at integrating pelican into this? I'd like a static blog and semi dynamic site and <3 django.
Re: Show HN: Wagtail, our new Django CMS
#68What's API support like? IE if I wanted to create a search widget that uses JSON. Have you considered something like Django REST Framework?
As it happens, the predictive search already returns JSON, but we don't have a general purpose API yet. It's on the list! Pages are just plain Django models under the hood, so Django REST Framework would be a good fit.
Having used piston, then tastypie, and now django-rest-framework for a number of json rest services, drf is hands down the nicest. Also, Tom Christie (main author) is super responsive via twitter or IRC so you can get bugs fixed / prs merged super fast. I literally can't recommend it enough
Re: Show HN: Wagtail, our new Django CMS
#69Earlier quoted context omitted.
Thanks! In case you missed it elsewhere there's a tutorial by Wagtail contributor Serafeim Papastefanos here: https://gist.github.com/tomdyson/8974456 but we're working hard on official docs and a proper screencast.
> To follow this tutorial you will need to have Python 2.7 installed with a working version of pip and virtualenv. Is that true in general for this CMS, that Python 2.7 will be needed? Python 3 isn't supported?
Yes, we focused on Python 2.x support for initial release. I'm afraid we haven't even tried Wagtail on Python 3 yet. Having said that, at Torchbox (where Wagtail originated) we have a general if somewhat vague principle that - as responsible Python developers - we should support the adoption of Python 3, so 3.x support is certainly a goal for the project.
If anyone has time to test Wagtail on Python 3 and report any problems to https://github.com/torchbox/wagtail/issues that will accelerate the work!
Re: Show HN: Wagtail, our new Django CMS
#70Earlier quoted context omitted.
Clients do care about having a stable and bug free software. Tests is one of the best way to achieve this.
I know and I agree, but I feel tests often cover the wrong thing, or what the developers feel is most important. Unit testing libraries within the system: great. Leaving the rest: not so great. Or aiming for 100% code coverage: uggh. Playing devil's advocate here: Testing the system throughout to ensure components play nicely together and that functionally the system works as expected - this is in my opinion more imp…
There are two types of tests.
unit tests - most common and are tightly tied to the code. integration tests - simulate example user behavior and test the pieces work together as expected. For this type of app, selenium is the best tool for the job and splinter is an amazing python abstraction ontop of selenium. For instance, I have Jenkins setup splinter to run chrome and Firefox tests headlessly using a frame buffer (xvfb) to test the apps I'm responsible for as part of $dayjob.
Both types of tests are necessary and equally important.