Author(s):	Adam Brenecki
Location	Room 105
Date	aug Fri 12	Days Raw Files
Start	15:00	First Raw Start	error-in-template
Duration	0:40:00	Offset	None
End	15:40	Last Raw End
Chapters
Total cuts_time	None min.

https://2016.pycon-au.org/schedule/102/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf A_Bird_A_Guitarist_And_A_Raised_Platform_Walk_Into_A_Bar_Comparing_Wagtail_Django_CMS_and_Mezzanine.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Django CMS, Mezzanine and Wagtail are the three most popular Django-based content management systems; all three have kept (or, in Wagtail's case, gained) their popularity because they are so different to each other. In many ways, from their fundamental data models right through to how they approach their content editing UIs, each one has a very different take on how a CMS should work. This talk will explore the different approaches, strengths and weaknesses of each CMS, and what they mean for you as a developer and for your content editors. markdown
Comment:	production notes