Author(s):	Will Hughes
Location	Track 2
Date	sep Sun 06	Days Raw Files
Start	13:30	First Raw Start	error-in-template
Duration	00:30:00	Offset	None
End	14:00	Last Raw End
Chapters
Total cuts_time	None min.

https://kiwi.pycon.org/schedule/presentation/88/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Mezzanine_a_brief_primer.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:	Mezzanine is a CMS framework built on top of Django that provides a set of primitives for building rich sites that can be managed by non-technical users. Topics this talk will cover: * Where Mezzanine sits in the broader ecosystem. Mezzanine is not a stand-alone product like Drupal or Wordpress, but a set of tools. There are other tools associated with Mezzanine that provide functionality that Mezzanine itself doesn't provide * Structure of a Mezzanine site * Two techniques for managing content Page-based vs object-based; example and use-cases * Things Mezzanine does well Advantages of using Mezzanine over other CMS systems * Things Mezzanine does not do well Reasons not to use Mezzanine markdown
Comment:	production notes