2. INTRODUCTION
Ben Weaver Travis Dunn
http://benweaver.com http://blahed.com
@bwvr @blahed
Noah Burney Rob Righter
http://noahburney.com http://robrighter.com
@nwah @robrighter
3. WHY A CMS?
+ Web Content needs to be easily edited by everyone
4. WHY A CMS?
+ Web Content needs to be easily edited by everyone
+ Web Content is (usually) the unique part of the website
5. WHY MESSAGE?
“ There are 100’s of content management
systems out there, so why make
”
another one?
6. WHY MESSAGE?
+ Web content doesn’t map well to relational databases
Relational DB Sitemap: Object DB Sitemap:
Image
Home News Products Home News Products
Gallery
N I P N P P
N I P N
N
I P P
N I P N N I N I
7. WHY MESSAGE?
+ Web content doesn’t map well to relational databases
+ Web content doesn't do well in a single database
Web Developer’s DB Content Author’s DB
8. WHY MESSAGE?
+ Web content doesn’t map well to relational databases
+ Web content doesn't do well in a single database
+ Web content needs to be revertible
9. WHY MESSAGE?
+ Web content doesn’t map well to relational databases
+ Web content doesn't do well in a single database
+ Web content needs to be revertible
+ Web content editing needs a simple UI
10. WHY MESSAGE?
+ Web content doesn’t map well to relational databases
+ Web content doesn't do well in a single database
+ Web content needs to be revertible
+ Web content editing needs a simple UI
+ Web Developers need good programming practices
+ Don’t repeat the same work twice
+ Use sustainable programming languages
+ Model View Controller
12. MESSAGE IMPLEMENTATION
Django
+ It’s easy to build things fast in Python
+ Pragmatic Community
+ Good Templates
+ We’re not trying to replace Django #thinksatchmo
13. MESSAGE IMPLEMENTATION
Influenced by Google App Engine
+ Data is modeled more like documents less like tables
+ Real Python Data
+ Expando Properties
20. REAL WORLD
+ Starting with Message
+ Roadmap
+ More UI Work
+ Refining the Datastore
+ Built In Apps #thinkdjango.contrib
+ Open Source
+ Hosted Version