wagtail

Wagtail core developer here – here are our sprint notes [1] that demonstrate what this funding means for us in practice. The TL;DR; is being able to address long-term technical debt in the UI, improving accessibility throughout, having proper UI customization capabilities – as part of a redesign & new features. [1]: https://github.com/wagtail/wagtail/discussions/7739

I run Torchbox, a small, private tech agency in the UK. We were commissioned by NHS Digital (the state sector organisation behind these tools) to support two related projects: moving NHS.uk to https://github.com/wagtail/wagtail and setting up https://beta.nhs.uk/service-manual/ on Wagtail. NHS Digital's procurement processes are tight and focused. They have an expert in-house team of developers and delivery managers, and they only used us on where we could accelerate the project. As a business owner, I would have liked a bigger contract. As a tax-payer and frequent user of the NHS, I'm very happy with their efficiency.

Not Flask, but still Python: Wagtail - https://github.com/wagtail/wagtail - is a popular headless CMS option. Michael Harrison from rice.edu / Openstax gave a great talk about this at last week's Wagtail Space: https://docs.google.com/presentation/d/1ZYMogOeXKCCmr7hDZnzx... https://www.youtube.com/watch?v=HZT14u6WwdY

I meant in terms of what it's outputting from the models, not what it's accepting as input. Since most apps accepts accept input from users via API endpoints or forms, sanitizing the output strikes me as more important than sanitizing the input, although ideally both should happen. I don't have any good example data, but this is what I'm talking about: https://github.com/wagtail/wagtail/issues/3466 A lot of folks don't care about this if they are making libraries for users, since it's really an issue with Excel, but if people within your company are the ones who are going to be potentially getting pwned then it makes less sense to me to just blame MS or whatever.

We're really excited to see that BetaFEC[0] is running on Wagtail[1], our open source Django CMS. Great job, 18F! [0] https://github.com/18F/fec-cms [1] https://github.com/torchbox/wagtail

Thanks, Ryan! Check out this exciting PR which landed a few hours ago: https://github.com/torchbox/wagtail/pull/1521 This allows Wagtail users to swap in alternative rich text editors, e.g. https://github.com/isotoma/wagtailtinymce

Contributing - there's a big list of Github issues you can help with: https://github.com/torchbox/wagtail/issues How to use it - the docs are pretty comprehensive: http://docs.wagtail.io/en/v0.8.6/ Getting help - join the user group: https://groups.google.com/forum/#!forum/wagtail

Wagtail (our open-source Django CMS [1]) can generate a static HTML export of your site to the filesystem, Amazon S3 or Google App Engine, piggy-backing on the excellent django-medusa library [2]. This feature was commissioned by a security company who didn't want to risk an embarrassing exposure to new vulnerabilities in Drupal, Rails, Django etc. Search is an issue for static HTML sites. Swiftype [3] and Algolia [4] look like solid options - has anyone used these in production? [1] https://github.com/torchbox/wagtail [2] https://github.com/mtigas/django-medusa [3] https://swiftype.com/ [4] https://www.algolia.com

Wagtail (https://github.com/torchbox/wagtail/) does not use the Django admin. It leaves it completely alone. It really is just another Django app. Highly recommended.

Your wish is their command: https://github.com/torchbox/wagtail/commit/860c3e036f2df1596...

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!

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 / middleware etc. There are some hooks, e.g. for including your app into the main admin navigation - see https://github.com/torchbox/wagtail/blob/master/wagtail/wagt... for an example of where a hook gets called. It's a good candidate for developer docs!

See below - there are tests, see https://github.com/torchbox/wagtail/blob/master/wagtail/wagt... and https://github.com/torchbox/wagtail/commit/a77977a31cdfcdf95... but we need more, and to make it more obvious how to run them. You're right that we have to do more to attract contributors. In the meantime we're offering t-shirts for pull requests... https://twitter.com/WagtailCMS/status/432166799464210432/