Keynote: The myth of goldilocks and the three frameworks, Pyramid, Django and Plone
summary
Plone claims enterprise-grade CMS features: 300+ contributors, 400+ plugins and "1000+ commits/month", multi-site out of the box and strong security (used by the FBI), backed by Zope traversal/component architecture and the Diazo theme editor that cuts theming time. Pyramid emphasizes mixing traversal and routing, lightweight start-and-scale design, and easy integration with ZODB or SQLAlchemy. Warning: projects hit a customization cliff—too much CMS hacking means a framework (Django/Pyramid) would have been cheaper. Examples: PrettyGov deployments, pool registration and timetabling sites; hybrid proxy middleware works in production.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:00Reasons for this talk
- 4:52Python family tree(web)
- 8:08ZODB: The piss easy DB
- 8:27ZODB: features
- 10:09Zope Tool Kit
- 15:50Overriding in Plone
- 18:26Separation of concerns
- 19:25Developers blog
- 19:58An app/startup
- 20:48Simple Blog
- 21:11Large content site
- 22:20Web consultancy
- 23:35The customisation cliff
- 25:00Framework vs CMS
- 27:08Pyramid: worst name ever
- 30:14Pyramid: a "micro & more" Framework
- 32:23Micro vs. Fw
- 37:03Other methods
- 37:45Summary
related talks
28mUsing Plone to Develop a Portal
23mStanding on the Shoulders of Giants: The Kotti Web Application Framework
57mArchetypes: this thing is good!™
47mPerformance Tuning of Plone Clusters
01h 10mKeynote 2: Robust Python and Why It Matters
24mA Brief History of Python Web Frameworks
38mPlone 5 and how to use machine learning with it.
01h 01mKeynote 2: The State of Python in 2024