91. Initial PLIP Submissions
• 7822: Make standard file content types use ZODB BLOB support • 9286: Allow to show/hide portlets
• 8801: Move action icon support into actions, remove CMFActionIcons • 9288: Improved commenting infrastructure
• 8802: Move our upgrade / migration infrastructure to GenericSetup • 9292: Group management delegation
• 8805: Do not ship with NuPlone anymore • 9295: Improved UI for collections
• 8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 • 9300: Well formed, valid XHTML
• 8809: Make KSS optional • 9302: Improving the event type with recurrence, etc.
• 8814: Replace SecureMailHost with a standard Zope mailhost • 9305: Use real names instead of usernames
• 8901: Deleting a user should revoke roles • 9309: Better search for East Asian (multi-byte) languages.
• 9186: Set Image IDs from Title field • 9310: User registration process more flexible
• 9210: Folderish pages • 9311: Clean up of user related actions UI
• 9214: support logins using e-mail address instead of user id • 9312: New roles : Webmaster/site administrator and novice users
• 9236: Include ""CachableRedirects"" or equivalent functionality • 9313: Mobile View with Mobile Image selection options
• 9249: Add TinyMCE as the default visual editor • 9314: Plone "Developer Pack" option for installers
• 9250: Add jQuery Tools to base install • 9315: New theme for Plone 4
• 9256: Expand variable substitution in mailing action of plone.app.contentrules • 9316: Unify folder implementations
• 9258: Replace Products.ATReferenceBrowserWidget with • 9319: Merging archetypes.fieldtraverser into Products.Archetypes
archetypes.referencebrowserwidget • 9320: Add global status bar for site notifications
• 9259: Group dashboards • 9321: Reimplement the search form with an eye on usability
• 9263: GenericSetup syntax for importing Sharing page roles • 9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
• 9264: Merge backport patches from plone.app.dexterity into Plone binary eggs
• 9270: Stop using fill-slot column_one_slot and two in standard templates • 9323: Ship with Vice for syndication
• 9271: Improving the search results page • 9324: Use Amberjack to offer guided help for first-time users
• 9272: Exposing and editing Dublin Core properties • 9327: unified interface for lists of content
• 9274: Remove actions tab from folder_contents • 9328: content im-/export
• 9279: Making document actions optional • 9329: Manage actions through-the-plone
• 9281: Use dashboard as social networking tool • 9330: Add ability to choose group when adding new site members
• 9282: Improved search results presentation • 9331: Invite to share
• 9283: A more lightweight backend for collections • 9347: Registration Policy
• 9284: Allow views to override skin layer elements easily • 9352: Search Results Improvements
• 9285: Show blocked portlets in management interface • 9376: Include archetypes.schematuning
92. Initial FWT Vote
• 7822: Make standard file content types use ZODB BLOB support • 9286: Allow to show/hide portlets
• 8801: Move action icon support into actions, remove CMFActionIcons • 9288: Improved commenting infrastructure
• 8802: Move our upgrade / migration infrastructure to GenericSetup • 9292: Group management delegation
• 8805: Do not ship with NuPlone anymore • 9295: Improved UI for collections
• 8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 • 9300: Well formed, valid XHTML
• 8809: Make KSS optional • 9302: Improving the event type with recurrence, etc.
• 8814: Replace SecureMailHost with a standard Zope mailhost • 9305: Use real names instead of usernames
• 8901: Deleting a user should revoke roles • 9309: Better search for East Asian (multi-byte) languages.
• 9186: Set Image IDs from Title field • 9310: User registration process more flexible
• 9210: Folderish pages • 9311: Clean up of user related actions UI
• 9214: support logins using e-mail address instead of user id • 9312: New roles : Webmaster/site administrator and novice users
• 9236: Include ""CachableRedirects"" or equivalent functionality • 9313: Mobile View with Mobile Image selection options
• 9249: Add TinyMCE as the default visual editor • 9314: Plone "Developer Pack" option for installers
• 9250: Add jQuery Tools to base install • 9315: New theme for Plone 4
• 9256: Expand variable substitution in mailing action of plone.app.contentrules • 9316: Unify folder implementations
• 9258: Replace Products.ATReferenceBrowserWidget with • 9319: Merging archetypes.fieldtraverser into Products.Archetypes
archetypes.referencebrowserwidget • 9320: Add global status bar for site notifications
• 9259: Group dashboards • 9321: Reimplement the search form with an eye on usability
• 9263: GenericSetup syntax for importing Sharing page roles • 9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
• 9264: Merge backport patches from plone.app.dexterity into Plone binary eggs
• 9270: Stop using fill-slot column_one_slot and two in standard templates • 9323: Ship with Vice for syndication
• 9271: Improving the search results page • 9324: Use Amberjack to offer guided help for first-time users
• 9272: Exposing and editing Dublin Core properties • 9327: unified interface for lists of content
• 9274: Remove actions tab from folder_contents • 9328: content im-/export
• 9279: Making document actions optional • 9329: Manage actions through-the-plone
• 9281: Use dashboard as social networking tool • 9330: Add ability to choose group when adding new site members
• 9282: Improved search results presentation • 9331: Invite to share
• 9283: A more lightweight backend for collections • 9347: Registration Policy
• 9284: Allow views to override skin layer elements easily • 9352: Search Results Improvements
• 9285: Show blocked portlets in management interface • 9376: Include archetypes.schematuning
93. Initial Implementation Reviews
• 7822: Make standard file content types use ZODB BLOB support • 9286: Allow to show/hide portlets
• 8801: Move action icon support into actions, remove CMFActionIcons • 9288: Improved commenting infrastructure
• 8802: Move our upgrade / migration infrastructure to GenericSetup • 9292: Group management delegation
• 8805: Do not ship with NuPlone anymore • 9295: Improved UI for collections
• 8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 • 9300: Well formed, valid XHTML
• 8809: Make KSS optional • 9302: Improving the event type with recurrence, etc.
• 8814: Replace SecureMailHost with a standard Zope mailhost • 9305: Use real names instead of usernames
• 8901: Deleting a user should revoke roles • 9309: Better search for East Asian (multi-byte) languages.
• 9186: Set Image IDs from Title field • 9310: User registration process more flexible
• 9210: Folderish pages • 9311: Clean up of user related actions UI
• 9214: support logins using e-mail address instead of user id • 9312: New roles : Webmaster/site administrator and novice users
• 9236: Include ""CachableRedirects"" or equivalent functionality • 9313: Mobile View with Mobile Image selection options
• 9249: Add TinyMCE as the default visual editor • 9314: Plone "Developer Pack" option for installers
• 9250: Add jQuery Tools to base install • 9315: New theme for Plone 4
• 9256: Expand variable substitution in mailing action of plone.app.contentrules • 9316: Unify folder implementations
• 9258: Replace Products.ATReferenceBrowserWidget with • 9319: Merging archetypes.fieldtraverser into Products.Archetypes
archetypes.referencebrowserwidget • 9320: Add global status bar for site notifications
• 9259: Group dashboards • 9321: Reimplement the search form with an eye on usability
• 9263: GenericSetup syntax for importing Sharing page roles • 9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
• 9264: Merge backport patches from plone.app.dexterity into Plone binary eggs
• 9270: Stop using fill-slot column_one_slot and two in standard templates • 9323: Ship with Vice for syndication
• 9271: Improving the search results page • 9324: Use Amberjack to offer guided help for first-time users
• 9272: Exposing and editing Dublin Core properties • 9327: unified interface for lists of content
• 9274: Remove actions tab from folder_contents • 9328: content im-/export
• 9279: Making document actions optional • 9329: Manage actions through-the-plone
• 9281: Use dashboard as social networking tool • 9330: Add ability to choose group when adding new site members
• 9282: Improved search results presentation • 9331: Invite to share
• 9283: A more lightweight backend for collections • 9347: Registration Policy
• 9284: Allow views to override skin layer elements easily • 9352: Search Results Improvements
• 9285: Show blocked portlets in management interface • 9376: Include archetypes.schematuning
95. Initial Implementation Reviews
• 7822: Make standard file content types use ZODB BLOB support • 9286: Allow to show/hide portlets
• 8801: Move action icon support into actions, remove CMFActionIcons • 9288: Improved commenting infrastructure
• 8802: Move our upgrade / migration infrastructure to GenericSetup • 9292: Group management delegation
• 8805: Do not ship with NuPlone anymore • 9295: Improved UI for collections
• 8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 • 9300: Well formed, valid XHTML
• 8809: Make KSS optional • 9302: Improving the event type with recurrence, etc.
• 8814: Replace SecureMailHost with a standard Zope mailhost • 9305: Use real names instead of usernames
• 8901: Deleting a user should revoke roles • 9309: Better search for East Asian (multi-byte) languages.
• 9186: Set Image IDs from Title field • 9310: User registration process more flexible
• 9210: Folderish pages • 9311: Clean up of user related actions UI
• 9214: support logins using e-mail address instead of user id • 9312: New roles : Webmaster/site administrator and novice users
• 9236: Include ""CachableRedirects"" or equivalent functionality • 9313: Mobile View with Mobile Image selection options
• 9249: Add TinyMCE as the default visual editor • 9314: Plone "Developer Pack" option for installers
• 9250: Add jQuery Tools to base install • 9315: New theme for Plone 4
• 9256: Expand variable substitution in mailing action of plone.app.contentrules • 9316: Unify folder implementations
• 9258: Replace Products.ATReferenceBrowserWidget with • 9319: Merging archetypes.fieldtraverser into Products.Archetypes
archetypes.referencebrowserwidget • 9320: Add global status bar for site notifications
• 9259: Group dashboards • 9321: Reimplement the search form with an eye on usability
• 9263: GenericSetup syntax for importing Sharing page roles • 9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
• 9264: Merge backport patches from plone.app.dexterity into Plone binary eggs
• 9270: Stop using fill-slot column_one_slot and two in standard templates • 9323: Ship with Vice for syndication
• 9271: Improving the search results page • 9324: Use Amberjack to offer guided help for first-time users
• 9272: Exposing and editing Dublin Core properties • 9327: unified interface for lists of content
• 9274: Remove actions tab from folder_contents • 9328: content im-/export
• 9279: Making document actions optional • 9329: Manage actions through-the-plone
• 9281: Use dashboard as social networking tool • 9330: Add ability to choose group when adding new site members
• 9282: Improved search results presentation • 9331: Invite to share
• 9283: A more lightweight backend for collections • 9347: Registration Policy
• 9284: Allow views to override skin layer elements easily • 9352: Search Results Improvements
• 9285: Show blocked portlets in management interface • 9376: Include archetypes.schematuning
96. Final FWT Vote
• 7822: Make standard file content types use ZODB BLOB support • 9286: Allow to show/hide portlets
• 8801: Move action icon support into actions, remove CMFActionIcons • 9288: Improved commenting infrastructure
• 8802: Move our upgrade / migration infrastructure to GenericSetup • 9292: Group management delegation
• 8805: Do not ship with NuPlone anymore • 9295: Improved UI for collections
• 8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 • 9300: Well formed, valid XHTML
• 8809: Make KSS optional • 9302: Improving the event type with recurrence, etc.
• 8814: Replace SecureMailHost with a standard Zope mailhost • 9305: Use real names instead of usernames
• 8901: Deleting a user should revoke roles • 9309: Better search for East Asian (multi-byte) languages.
• 9186: Set Image IDs from Title field • 9310: User registration process more flexible
• 9210: Folderish pages • 9311: Clean up of user related actions UI
• 9214: support logins using e-mail address instead of user id • 9312: New roles : Webmaster/site administrator and novice users
• 9236: Include ""CachableRedirects"" or equivalent functionality • 9313: Mobile View with Mobile Image selection options
• 9249: Add TinyMCE as the default visual editor • 9314: Plone "Developer Pack" option for installers
• 9250: Add jQuery Tools to base install • 9315: New theme for Plone 4
• 9256: Expand variable substitution in mailing action of plone.app.contentrules • 9316: Unify folder implementations
• 9258: Replace Products.ATReferenceBrowserWidget with • 9319: Merging archetypes.fieldtraverser into Products.Archetypes
archetypes.referencebrowserwidget • 9320: Add global status bar for site notifications
• 9259: Group dashboards • 9321: Reimplement the search form with an eye on usability
• 9263: GenericSetup syntax for importing Sharing page roles • 9322: Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via
• 9264: Merge backport patches from plone.app.dexterity into Plone binary eggs
• 9270: Stop using fill-slot column_one_slot and two in standard templates • 9323: Ship with Vice for syndication
• 9271: Improving the search results page • 9324: Use Amberjack to offer guided help for first-time users
• 9272: Exposing and editing Dublin Core properties • 9327: unified interface for lists of content
• 9274: Remove actions tab from folder_contents • 9328: content im-/export
• 9279: Making document actions optional • 9329: Manage actions through-the-plone
• 9281: Use dashboard as social networking tool • 9330: Add ability to choose group when adding new site members
• 9282: Improved search results presentation • 9331: Invite to share
• 9283: A more lightweight backend for collections • 9347: Registration Policy
• 9284: Allow views to override skin layer elements easily • 9352: Search Results Improvements
• 9285: Show blocked portlets in management interface • 9376: Include archetypes.schematuning
97. Final FWT Vote
• 7822: Make standard file content types use ZODB • 9263: GenericSetup syntax for importing Sharing page
BLOB support roles
• 8801: Move action icon support into actions, remove • 9264: Merge backport patches from plone.app.dexterity
CMFActionIcons into Plone
• 8802: Move our upgrade / migration infrastructure to • 9272: Exposing and editing Dublin Core properties
GenericSetup • 9285: Show blocked portlets in management interface
• 8805: Do not ship with NuPlone anymore • 9286: Allow to show/hide portlets
• 8808: Require Python 2.5 or 2.6, Zope 2.12, and CMF • 9305: Use real names instead of usernames
2.2 for Plone 4.0 • 9309: Better search for East Asian (multi-byte) languages.
• 8814: Replace SecureMailHost with a standard Zope
• 9310: User registration process more flexible
mailhost
• 9314: Plone "Developer Pack" option for installers
• 9186: Set Image IDs from Title field
• 9315: New theme for Plone 4
• 9214: support logins using e-mail address instead of user
• 9316: Unify folder implementations
id
• 9321: Reimplement the search form with an eye on
• 9249: Add TinyMCE as the default visual editor
usability
• 9250: Add jQuery Tools to base install
• 9330: Add ability to choose group when adding new site
• 9256: Expand variable substitution in mailing action of members
plone.app.contentrules
• 9258: Replace Products.ATReferenceBrowserWidget
with archetypes.referencebrowserwidget
• 9259: Group dashboards
128. SecureMailHost
• Introduced in Plone 2.1
• TLS encryption support
• Made redundant by Zope 2.11’s Products.MailHost
• Optional mail queuing
• Sent emails are quoted-printable
145. Sponsored By
• Potsdam Institute for Climate Impact Research
• Intergovernmental Panel on Climate Change
• European Network and Information Security Agency
147. Potsdam Institute For Climate
Impact Research
• http://pik-potsdam.de/
• 6,789 files to migrate
• Migration took 51 minutes
• ZODB was packed from 16.5 GB to 3.0 GB
• Memory footprint from 10 GB to 3 GB
160. Flexible User Registration
• join_form is now a view
• Show/Hide possible fields
• Utility lookup for fields
• Easily extendible
161. #9309
East Asian Language Search
Manabu Terada, Mikio Hokari,
Takeshi Yamamoto, Naotaka Hotta,
Jonathan Lewis
162. Full-text Indexing
• Full-text indexing typically splits words on spaces
• CJK (Chinese, Japanese, Korean) languages don’t
• Use bigram-splitting for those languages instead
• Work begun during 2008 GSOC
178. Group Dashboards
• Assign portlets to dashboards on per-group basis
• User sees:
• Personal portlets
179. Group Dashboards
• Assign portlets to dashboards on per-group basis
• User sees:
• Personal portlets
• Portlets of groups they belong to
180. Group Dashboards
• Assign portlets to dashboards on per-group basis
• User sees:
• Personal portlets
• Portlets of groups they belong to
• Win for intranets
181. Group Dashboards
• Assign portlets to dashboards on per-group basis
• User sees:
• Personal portlets
• Portlets of groups they belong to
• Win for intranets
• Bulletin board
225. Set Image ID from Title
• Makes ATImage act more like other types
• Easily give images more memorable IDs
• Picture 1.png
• 3425573738_90e84302e8.jpg
262. vs.event
• Recurring events
• New calendar widget
• Improved all-day events
• Extended support for
attendees and attachments
(UI and iCal level)
263. vs.event
• Recurring events
• New calendar widget
• Improved all-day events
• Extended support for
attendees and attachments
(UI and iCal level)
• Support for master &
supplementary events
which absolutely none of you came to hear, but I’m going to tell you about anyway.
Part the first, in which things are needlessly convoluted.
We had two releases, Plone 3 and Plone 4.
We had two releases, Plone 3 and Plone 4.
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
Plone 3 had all sorts of things
Plone 4 had all sorts of plans
The problem was, we were looking at 3 years between releases and huge migrations for everyone.
And so we said, “well, some of this is actually ready...now”.
So let’s make a new major release!
It’ll be like Plone 3, but with some of the things from Plone 4. People get will get some of the new features much sooner and they’ll have a much simpler migration.
And everybody said yaaay!
And let’s call it Plone 3.5!
And everybody said Nooo!
Because of what I’ve been calling the “Dot Release Contract”
Though, while researching for this presentation, Google informed me that I’m the only one to ever actually use the term. Here’s how we make it canon...
So we said, “here’s what we’ll do...”
We’ll take the release we’ve been calling Plone 4 and call it Plone 5.
“And then we’ll call this new one Plone 4 instead!”
[deadpan/sarcastic] Because that won’t confuse anybody...
And everybody sorta just shrugged.
And so, let me introduce
The intent of the release was to make this primarily a transitional release which means
Part the second, in which I give an overly-detailed description of...
...the PLIP process.
So what’s a PLIP?
== Motivation ==
Why does this proposal exist and what problem does it solve?
== Assumptions ==
What is being covered by and what is intentionally left out of the scope of the proposal.
== Proposal & Implementation ==
What needs to be done, and how should it be done?
== Deliverables ==
What code and documentation needs to be produced?
== Risks ==
What are the risks of implementing this proposal?
What incompatibilities can it cause?
And before we could accept those proposals, we needed a framework team.
And the primary duty of the Framework Team is to evaluate PLIPs for inclusion into the release.
And before we could accept those proposals, we needed a framework team.
And the primary duty of the Framework Team is to evaluate PLIPs for inclusion into the release.
And before we could accept those proposals, we needed a framework team.
And the primary duty of the Framework Team is to evaluate PLIPs for inclusion into the release.
3 series, Plone 5
And we threw in Plone 2.5‘s release manager, Alec Mitchell, for good measure. Eight people sounded like a lot, but really worked out rather well because of what happened next.
And as release manager, it’s my job to remind, push, prod, nag, cajole, and occasionally shame everyone into getting their work done.
And as release manager, it’s my job to remind, push, prod, nag, cajole, and occasionally shame everyone into getting their work done.
And as release manager, it’s my job to remind, push, prod, nag, cajole, and occasionally shame everyone into getting their work done.
And as release manager, it’s my job to remind, push, prod, nag, cajole, and occasionally shame everyone into getting their work done.
And as release manager, it’s my job to remind, push, prod, nag, cajole, and occasionally shame everyone into getting their work done.
And as release manager, it’s my job to remind, push, prod, nag, cajole, and occasionally shame everyone into getting their work done.
So Deadline 1 was PLIP submission. We gave everyone two weeks to get their proposals in.
I figured we’d be lucky to see 10.
We got a record 58.
After an initial evaluation by the Framework Team, we were down to 41.
33 actual implementations were submitted to the Framework Team who dug through the code and made suggestions for improvements.
Then handed those back to the implementers and gave them 3 weeks to revise their work accordingly.
At this point, I need to give a big thanks to
for pitching in for these reviews. We never would’ve made it through otherwise.
So then we handed those critiques back to the implementers and gave them 3 weeks to revise their work accordingly.
And then it was time for the final up or down vote on each. 26 made the cut.
Again, a record for Plone.
Done.
So basically I went through all of that for one reason. There are a lot of people who worked extremely hard to put together this release in a very short amount of time. They all deserve a round of applause. And, if I might make a suggestion, a round or more of free beers.
[reduces the risk of Plone being unable to adopt third party
packages that depend on newer Python features]
RelStorage, which means it’s easier to store data in relational databases and use their clustering and replication features.
And Blob storage, which lets us save file content to the filesystem outside of the Data.fs.
Funkload tests run for us by Ross Patterson.
Using Plone 2.5 as the baseline performance measurement.
Then Plone 3.0
3.3
And 4.0
We can see that Plone 4.0 responds nearly twice as fast at low loads and as we get up into higher loads, it’s performing nearly 5 times better than Plone 2.5.
And responds around twice as fast as Plone 3.3.
And another graph.
This time, we’re looking at performance while adding new content to the site.
Once again, using Plone 2.5 as the baseline.
We can see that Plone 4 runs anywhere from 2.5 to 4.5 times faster than Plone 2.5, again with much better relative response times at higher loads.
And up to 3 times as fast as Plone 3.3
Also of note, Plone 3.3 performs worse than 3.0 in this test. Now that we have this benchmarking set up, we can hopefully catch regressions like these before we release.
Hanno ran some numbers for page load times using apache benchmark and found that
44% increase in speed
35% increase in speed
19% increase in speed
SecureMailHost was added in Plone 2.1 to support Transport Layer Security encryption.
That was made redundant by changes to Zope 2.11’s MailHost.
Quoted-printable instead of base64 which should make them less likely to get flagged by spam filters.
Plone currently ships with two types of folders.
Plone currently ships with two types of folders.
Basically a large plone folder,
but with ordering support
Provides an ordering adapter which allows you to specify exactly which content types will be orderable within a folder.
Basically a large plone folder,
but with ordering support
Provides an ordering adapter which allows you to specify exactly which content types will be orderable within a folder.
Basically a large plone folder,
but with ordering support
Provides an ordering adapter which allows you to specify exactly which content types will be orderable within a folder.
40% increase in speed
30% increase in speed
Simplify the process of adding new roles to Plone’s sharing view by adding some new GenericSetup functionality.
This is a port from collective.sharingroles.
And this is what the GenericSetup XML would look like.
Hanno has pointed out another instance of plone.app.blob in production: Norden.org, built by Jarn, which has a 6 gig data.fs and another 16 gigs of file content in blob-storage. It scales quite nicely.
Take advantage of changes in CMF
Take advantage of changes in CMF
Why’s this so great?
They’ve just opened Plone up to a potential 1.5 billion new users.
Billion
The main intent behind this theme was to be intentionally boring. Something that looked good, but was simple enough that a company could slap their own logo in there and call it a finished site.
It’s built on the Deco grid system which lets you define layout very easily.
The main intent behind this theme was to be intentionally boring. Something that looked good, but was simple enough that a company could slap their own logo in there and call it a finished site.
It’s built on the Deco grid system which lets you define layout very easily.
The main intent behind this theme was to be intentionally boring. Something that looked good, but was simple enough that a company could slap their own logo in there and call it a finished site.
It’s built on the Deco grid system which lets you define layout very easily.
The main intent behind this theme was to be intentionally boring. Something that looked good, but was simple enough that a company could slap their own logo in there and call it a finished site.
It’s built on the Deco grid system which lets you define layout very easily.
The main intent behind this theme was to be intentionally boring. Something that looked good, but was simple enough that a company could slap their own logo in there and call it a finished site.
It’s built on the Deco grid system which lets you define layout very easily.
The main intent behind this theme was to be intentionally boring. Something that looked good, but was simple enough that a company could slap their own logo in there and call it a finished site.
It’s built on the Deco grid system which lets you define layout very easily.
Roel Bruggink
Provides the option to expose Dublin Core metadata for any object in the HTML meta tags.
A PLIP so big it apparently defies my attempts to display it on one line.
Replaces Products.ATReferenceBrowserWidget
Provides large performance improvements over its predecessor
It supports more reference field implementations OOTB and is easier to plug into new ones.
It’s easy to override the popup template
Proper test coverage
Replaces Products.ATReferenceBrowserWidget
Provides large performance improvements over its predecessor
It supports more reference field implementations OOTB and is easier to plug into new ones.
It’s easy to override the popup template
Proper test coverage
Replaces Products.ATReferenceBrowserWidget
Provides large performance improvements over its predecessor
It supports more reference field implementations OOTB and is easier to plug into new ones.
It’s easy to override the popup template
Proper test coverage
Replaces Products.ATReferenceBrowserWidget
Provides large performance improvements over its predecessor
It supports more reference field implementations OOTB and is easier to plug into new ones.
It’s easy to override the popup template
Proper test coverage
Replaces Products.ATReferenceBrowserWidget
Provides large performance improvements over its predecessor
It supports more reference field implementations OOTB and is easier to plug into new ones.
It’s easy to override the popup template
Proper test coverage
This is Products.TinyMCE which has been available for use in Plone 3 for a while now. This PLIP is one of those Plone 5 changes that we’re preparing everyone for since TinyMCE is an integral part of the Deco UI.
We’re integrating this as the default rich text editor for Plone 4, but we’re still including Kupu for backwards compatibility reasons.
The configuration options look very similar to Kupu’s as well.
Like Mac screenshots or downloads from Flickr
This is another highly requested feature.
This is another highly requested feature.
This is another highly requested feature.
This is another highly requested feature.
We’re stealing the Zope startup page from the Unified Installer. This provides a much friendlier view for new Plone users.
Create a new Plone site from here. And you’ll also see any migration warnings here.
The new Plone site form has also been revamped. Once again, trying to provide a much friendlier experience for new users. The general idea is to keep newbies out of the ZMI for as long as possible.
Have the option to skip the example content (front-page, news, events)
You’ll have the ability to chose which (already downloaded) products should be automatically installed in that new site.
The new Plone site form has also been revamped. Once again, trying to provide a much friendlier experience for new users. The general idea is to keep newbies out of the ZMI for as long as possible.
Have the option to skip the example content (front-page, news, events)
You’ll have the ability to chose which (already downloaded) products should be automatically installed in that new site.
The new Plone site form has also been revamped. Once again, trying to provide a much friendlier experience for new users. The general idea is to keep newbies out of the ZMI for as long as possible.
Have the option to skip the example content (front-page, news, events)
You’ll have the ability to chose which (already downloaded) products should be automatically installed in that new site.
And if you’ve been following the growing debate over Setuptools and Distribute, Plone will be throwing its rather sizable weight behind Distribute.
Configurable and extensible comment forms using z3c.form
Configurable and extensible comment forms using z3c.form
Configurable and extensible comment forms using z3c.form
Configurable and extensible comment forms using z3c.form