DjangoCon 2015

Wagtail, un nuevo CMS para Django

Tom Dyson  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

hi everyone as Edward I said I'm the my name is Tom Dyson and I run torch box which is a UK agency we do digital work for people making the world a better place people like Greenpeace Oxfam Red Cross United Nations we built a content management system

called wagtail and that's what I'm going to talk about for the next 25 minutes this isn't a particularly technical talk so if you're not so interested in this story behind why tell then you can just pretend to listen and you can use the time

productively by building a little wagtail site so inspired by Microsoft I've got a promotional idea and if you showing me a wagtail site that you've built by the end of today i'll post your t-shirt here's the one minute version to help you

get started this gets you as far as the admin interface if you don't have a photographic memory you could take a photo of the screen although that would give the game away here's a link for the extended ten minute version this shows you how to build

your own page models and templates if you get stuck with anything I'd be very happy to help you off to it and finally for the super lazy you could just try out the demo this is running on a little docker container on my colleagues five-dollar digitalocean

box so maybe don't all try this one at once the back to the story torch box has been working with Django since the early days my my brief my fleeting claim to fame in the Django community is that I made the first ever Django screencast in 2005 soon after

that I hired Simon Wilson and Andrew Godwin in fact the first version of South was built by Andrew for a torch box project we have a team of developers a torch box using Django to build things like SMS apps delivering personalized agricultural information

to subsistence farmers in Kenya ecological footprint calculators grant management systems tools for booking beds in care homes but for the last five years for big public content managed web sites we've mainly used Drupal as anyone here use Drupal this

may be about half of you it's easy to be rude about Drupal but it's it's very powerful it it has an enormous community the ecosystem of modules and Drupal is probably as big as the ecosystem of Django applications and most importantly you don't

get fired for choosing Drupal that's especially true in the nonprofit space where most of toolboxes clients come from and we've made some Drupal sites that we're really proud of particularly perhaps Oxford University and the Royal Institute of

Foreign Affairs both of these are high-profile sites big sites with masses of content high traffic they work well for their users and lots of people say nice things about them but Drupal has some big flaws the first of these is that configuration happens in

the database you can imagine why a developer think this is a good idea but it becomes very painful when you move from developer to staging and then production environments and then your client calls you in this lism there's a problem that you can't

replicate because they've configured things differently to your version and on a similar point Drupal is too flexible the power that Drupal gives administrators and particularly around creating new content types who the user interface and generating columns

and tables becomes pain for developers performance is an issue most Drupal sites rely heavily on varnish and that's okay for a mainly static mainly mainly a read heavy site but varnish doesn't help the logged-in editors who have to put up with a sluggish

authoring experience and when we deliver a Drupal site we have to train the editors it's not a disaster but I think ideally if you can sign up for a Netflix account or buy a book on Amazon then you ought to be able to understand the fundamentals of creating

and managing content on a website on a CMS but drupal's worst sin in my opinion is that its opinionated about markup Drupal generates HTML for you this restricts our design in our UI choices and it makes site maintenance slower for our developers most

importantly makes us more expensive for our clients so faced with these frustrations we persuaded one of our clients the royal college of art to commissioned us to build them a new CMS in Django we launched their site in late 2013 and we launched the open

source project in february2014 at django weekend an excellent short conference in Cardiff I guess this was this was half about being a good open source citizen but half commercial we knew that we couldn't persuade new clients to let us use wagtail to build

their sites if the only people maintaining it were a small company in the Oxfordshire countryside to be honest we weren't very well prepared to manage a reasonably sized open source project despite that everything seemed to go perfectly for the first few

[ ... ]

Nota: se han omitido las otras 2.324 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.