Plone - Revised Roadmap: Plone 3,4,5 and beyond - Dutch Plone Users Day (+AUDIO)
11 likes1,702 views
The document outlines the revised roadmap for Plone versions 3, 4, and 5, focusing on improvements in speed, user roles, and editing mechanisms. Key features include a new theme, reduced code complexity, and the introduction of 'tiles' for dynamic content management. It also promotes the upcoming Plone conference with various sessions and networking opportunities.
Plone - Revised Roadmap: Plone 3,4,5 and beyond - Dutch Plone Users Day (+AUDIO)
- 1. Plone Revised Roadmap Plone 3, 4, 5 and beyond
- 4. 3
- 5. 4
- 6. 5
- 7. 4
- 10. Disclaimer Contents may shift during transportation
- 12. CMF 2.2
- 13. TinyMCE editor
- 14. BLOBs
- 15. plone.folder
- 16. KSS optional
- 17. Fewer hacks
- 21. Improve Comments
- 23. New theme
- 24. 5
- 27. Simplicity
- 28. Approachability
- 29. Performance
- 30. Approachability
- 31. Dexterity
- 32. Dexterity Through the web schema editing Web-to-filesystem round-trip(!) Pluggable schemas Pluggable behavior Separate packages Faster
- 33. Deliverance xdv Theming done right
- 34. Your theme Plone output Navigation Search Awesome, Inc. Search Navigation Sidebar Sidebar Content Sidebar Content Sidebar Footer Footer
- 36. Content type View Form Tile
- 37. plone.registry
- 38. Performance
- 39. Plone needs to be faster… …out of the box …for logged in users …in high-end scenarios
- 40. Reduce and simplify the code base
- 41. LINES OF CODE 1200000 1144322 1147545 1122261 1100000 1000000 960456 916360 887059 900000 867263 800000 3.1 ) ) ) 3.0 3.2 ) -26 -17 -14 -09 -02 -03 -01 -05 09 09 09 09 20 20 20 20 k( k( k( k( n n n n Tru Tru Tru Tru Lines of Code/Tempates for Plone including the CMF and Zope stacks
- 42. 1,200,000 1147545 867263 800,000 400,000 0 3.0 nk tru
- 44. ZPT is slow
- 45. Chameleon
- 46. 50.0 Anonymous page view 45 37.5 25.0 18 12.5 12 0 Plone 3.3 with ZPT Plone 3.3 with Chameleon Plone trunk
- 47. Logged in view 30.0 24 22.5 15.0 10 7.5 7 0 Plone 3.3 with ZPT Plone 3.3 with Chameleon Plone trunk
- 48. Lacks support for restricted Python Currently works with views Still some way to go for skin templates Works with Plone 3.3 (some caveats)
- 49. Search Less dependence on Catalog Fewer indexes Queryplan Collective.SOLR
- 51. Simplicity
- 52. Deco A new approach to page editing
- 53. Pages Layouts composed of Tiles
- 54. Tiles Persistent Stores configuration and data Form for configuration Live at a unique URL Renders to HTML TILES ARE THE NEW APPS
- 55. Example tiles HTML text Image with caption Lists / stored searches Flash movie/app Form, poll etc. File attachment Fields (AT/Dexterity)
- 56. Deco Full-page editing interface Replaces Kupu DOM manipulation Drag/Drop of Tiles TinyMCE inside text tiles NO GRID MANAGEMENT
- 58. One content type! A page is also a folder is also a collection
- 59. …even an event
- 60. Not the end of content types Custom types still have many uses
- 61. Choice of types Dexterity or Archetypes or NONE
- 62. Plone 3.3 Out Now Plone 4 End 2009 Plone 5 Mid 2010
- 63. Plone Conf 2009
- 64. Budapest! (a beautiful city)
- 65. Plone Conf Amazing value - €200 ➡ 2 days of training before ➡ 2 days of scheduled talks ➡ 1 day ‘unconference’ ➡ 2 days of sprints
- 66. Plone Conf 50 talks over first two days ➡ Including case studies, tutorials, and in depth developer talks
- 67. Plone Conf ‘Unconference’ 3rd day ➡ Self-organised by the attendees ➡ Think ‘lightning talks’ but on a larger scale
- 68. Plone Conf Have Fun! ➡ Meet other Plone users ➡ Chat with Plone developers ➡ Drink beer!
Editor's Notes
- #2: I’m going to take you through the vision for the next couple of major releases for Plone. Netherlands highest number of Plone companies per capita? Fourdigits, Pareto, Zest, Infrae, Goldmund...
- #4: Actually this talk was mainly written by these two guys, Geir Baekholt and Alex Limi This roadmap has been presented at European Plone Symposium & Plone Symposium East
- #5: Goal of 3.x: Stability, predictability, maturity. 3.3 has shipped now Stability comes at the cost of innovation. We cannot do innovate within the scope of Plone 3. That would break the promise of stability. So, happy as we are with Plone 3 — time to get innovating again.
- #6: Plone 4: a cleanup/infrastructure release Bringing in some of the great work from Plone trunk earlier than Plone 5 Will have new features, but stuff that is stable now. Features that are too big for a 3.x release. (i,.e require migration, compatibility changes, might break addons) Not experimental
- #7: Plone 5: Redefine how content management is done (Until recently known as Plone 4 — confusing, we know ;)
- #8: So, let’s talk about Plone 4 first. This is mostly a cleanup release, with some infrastructural changes.
- #9: We decided to make a Plone 4 release, goal is end of 2009 Not as radical as the work on Plone trunk Will have new features — but stuff that has stabilized through community usage. Features that are too big for a 3.x release. (i,.e require migration, compatibility changes, might break addons)
- #10: With release manager Eric Steele, who should take special care to make sure there are more high-resolution images of him available on the web.
- #11: This is a list of what has been PROPOSED at this point, not what will necessarily land. :) As there is a formal proposal and review process, code to be written on a volunteer basis, and a general lot of uncertainty here — let’s see all of this as speculation, guesswork and hopes. PLIPs
- #12: BLOB support is the big deal in 2.11 Python 2.6 if we go for Zope 2.12, which I think we should aim for (better unicode memory management in Python, eggified Zope, etc)
- #13: Bug fixes and updates
- #14: Widely used visual editor. The new editing UI for Plone 5 will also be based on TinyMCE. Plone integration already exists. (Four Digits) You will still be able to use Kupu with Plone 4, of course. We’ll just switch the default. Also, we won’t change your existing setup when you upgrade — unless you want us to.
- #15: Proper support for BLOBs Store binary objects outside the ZODB, on the filesystem Tested. Jarn has this running in a 7000 employee intranet.
- #16: BTree-based folder implementation, supports ordering Faster Scales better Replaces Folder, ATFolder, Large folder, etc
- #18: Fewer hacks like SecureMailHost.The built-in Zope mailhost is now more advanced than this one. Better for us to have less custom stuff to maintain.
- #19: plone.app.upgrade Upgrade machinery. replaces the suboptimal reinstall button in the current add-on quickinstaller. Makes it simple for product authors to define upgrade steps between versions.
- #20: Newbie (limited/restricted user) — possible to make adjustments to UI and otherwise for certain users. Site admin is a not-fully-fledged admin that can do things like manage users, but not things that can affect the site configuration (ie. install add-ons).
- #21: Stuff like Gloworm
- #22: Commenting is one of the original cool features of the CMF and Plone — but it is way overdue for revision. Currently a Google Summer of Code project.
- #23: Martin has made some interesting improvements here, ability to require a revision note, etc. Simple, non-intrusive, low risk.
- #24: Port over the typography from the new plone.org design Make it color-neutral, so simple customization like adding a company logo always looks good
- #25: OK, time to talk about the exciting release, Plone 5 (I refuse to call this Plone trunk ;)
- #26: Release manager Hanno Schlichting
- #27: Three pillars of Plone 5:
- #31: Approachability means that it should be easy for new developers to pick up
- #32: Replacement for Archetypes.
- #34: Theming fast and simple. Write html, poke holes in it for your Plone content. XDV is deliverance reimplemented as compiled XSLT. Currently has less features than Deliverance, but has much better performance. Laurence’s goal is to have it compile down to a single XSLT transform that can be placed in the pipeline. No special software required to host it. Used on current plone.org.
- #35: Nate Aune has been doing some fantastic work in this area with ‘Banjo’ a GUI for doing deliverance theming.
- #36: GROK allows ‘convention over configuration’, similar to Ruby on Rails. Does what you’d expect for 90% of your tasks, but you still have zcml if you want more power. Most developers/integrators do the same things. Common tasks are:
- #37: These are by far the most common tasks a developer will need to perform. plone.grok directives for these common scenarios. No more need for zcml.
- #38: Better, more capable version of portal_properties Split more tools into configuration and functionality Similar to Mozilla’s about:config
- #40: So, how do we make it faster?
- #42: Reduction of lines of code from Plone 3.x to trunk (what will become Plone 5)
- #46: Templating engine — can be used for multiple syntaxes of attribute based languages like ZPT and Genshi Quite a bit faster. Maintained. Used by Repoze.BFG, Pylons, Plone
- #47: Improvements for anonymous page rendering…
- #48: But also substantial for logged-in users.
- #50: Collective.SOLR integrates with SOLR, an open source enterprise level search engine — much more advanced than ZCatalog. Jarn using this in a 7000-employee intranet. It works wonderfully. There is no way ZCatalog could have handled this kind of load/content.
- #51: CacheFu works really well for caching content, but is a bit old, and the way it works is a bit ugly. We have better ways to do this now, 4 years later.
- #52: Simplicity for the end-users.
- #53: “Blocks” is the back-end architecture “Deco” is the front end editing interface
- #58: Not needed anymore. Since deco handles layout properly no more need for “use content as default page”
- #59: This is not a haiku. ;) No need for most content types now that we have tiles + Deco
- #62: Archetypes will still work Dexterity will be there for those that want to switch And if you don’t need types, you’ll not have to relate to either.
- #68: Found something interesting whilst talking to others? Talk sparked some interest? Then do a talk on the subject!