The purpose of this talk is to share some of the important insights gained over a couple years of working on custom CMS-type projects serving large organizations. Acknowledging that approx. 30 minutes is a short time to cover a broad subject, the focus of the talk would be on outlining a basic strategy for managing large projects.
Over the past couple of years, Brian and Yann's team have built and worked on several large Django projects for large organizations. They will discuss how to start and manage large CMS projects, with an emphasis on pointing people to the best reference information and breaking down the common operations.
The primary discussion topics would cover:
- Breaking Down the Job: Over the course of the project you'll end up accounting for thousands of details; here's how to figure out the first few Centering Around a Prototype: Hedging your bets for the inevitable "give me a ballpark figure"
- Dealing With Legacy Data Stores: Migrate legacy information early and often.
- Selecting 3rd Party Components: Reuse exiting app, fork it early or Trailblaze
- Bad News: Django Ain't Perfect - where it has weaknesses and how to compensate
At the end of this talk the audience will be able to:
* Break down this type of project into meaningful phases * Migrate large dataset to populate the django models that are still under development. * Have a rational and objective approach to select django reusable component and understand how to refine them during the different stages of the project lifecycle. * Find and evaluate quality information about the tradeoffs Django presents in these types of projects