Out of the box it should be possible to import and export content in an XML format. This would considerably simplify processes like restoring part of a site, migration or reorganization of content.

- We lack an high contrast css in the core!
- Integrate some improvement found in: http://pypi.python.org/pypi/italianskin.templates and http://pypi.python.org/pypi/italianskin.tool/ (which add an high contrast css )

SVG should be supported as a regular image format, just like PNG or JPEG. For browser compatibility it should probably use the <object/> tag for SVG content.

Plone should also allow the upload of SVG content.

SVG could also be used as image backgrounds (e.g. CSS)

Finally (as a goodie), Plone should be able to index SVG content, but the general SVG support is more important.

Out of the box, Plone should come with known-good production configurations that include ZEO, pound, squid, nginx, varnish, Apache that don't require arcane knowledge to tweak

It's very limiting to think that all events are one-time only. Calendar systems are used for booking rooms and equipment as well as to advertise weekly and monthly meetings. Plone should come equipped with a calendar that has a nice user-interface for repeating events.

MIT's Exhibit system offers extremely useful and powerful visualization based on viewing the same data as timelines, maps, and faceted queries. http://www.simile-widgets.org/exhibit/ Having this capability would be a huge win for Plone which could be used in many different ways

I know this isn't exactly new, but it's really crying for a solution:

We often have a few pages (or other objects) that contextually belongs in more than one place (folder).

To avoid creating redundant objects means using collections or custom views, etc. all of which are too complicated for content managers that aren't plone savvy.

How can we accomplish this?
Often the content

Make it easier to setup multilingual sites with various requirements. Alexander Limi mentioned this on his blog last year. Currently LinguPlone primarily supports creating sites which are to be fully translated into every language and which have an identical site structure in all languages. This is not flexible enough for many applications. We need more options for language fallback, improved translation workflow and better integration with other products. ( There is an interesting high-level discussion about this on the developer forum: http://n2.nabble.com/Next-generation-multilingual-support-tp3142356p3149348.html )

In the case of things like the collection portlet, the output can vary from collection to collection. It would be helpful to allow integrators to specify a selection of different templates for editors to choose from.

"The Big Green Button" is an idea that has been floated around to make it easier to push plone content to a static web server or to a sql database. Plone becomes just the content management tool and not the content delivery server.

http://www.martinaspeli.net/articles/pete-and-andy-try-plone-4

http://blog.kapilt.com/2008/07/02/introducing-content-mirror/

http://blog.delaguardia.com.mx/hosting-options-plone-adoption-and-the-big-green-button

It would be great to be able to have a calendar view of events. Being able to choose either view by day, week, or month.

Out of the box, Plone should support mobile device presentation using mobile templates that are more optimized for devices such a the iPhone/ blackberry, etc.

There is a dashboard in Plone, but users have to go on it and it only contains portlets.
It shoud be possible to have a dashboard page as front page restricted to specific roles. If users have one of these roles they would get the start page instead of the standard start page.
Users should be able to personalize this start page by adding or moving widgets? These widgets may be plone widgets (portlets ?) and external web widgets.

Plone currently creates a class in the body tag called "section-" using getSectionFromURL for all top level folders in main_template.pt. However, there is a known limitation in creating subsite themes within Plone. For more information, go to:
https://weblion.psu.edu/trac/weblion/wiki/SubsiteTheming

A modification could be made to getSectionFromURL to include a class for every section folder. This implementation is currently being used with a WordPress theme called Sandbox (http://www.plaintxt.org/themes/sandbox/). This can greatly help enable the ability to create subsites within Plone using CSS. The Sandbox example can be seen here: http://www.plaintxt.org/themes/sandbox/sandbox_body/

Sometimes, sites have protected content that should not be shown to anonymous (or maybe to a general role like Authenticated or Member), but want to show "teaser" content, either calculated from the actual content (like a crop of the text) or specifically authored for that purpose.

There should be a way to designate alternate content like this. Maybe by role, to keep it generic. It could also be something that involves a redirect.

I haven't really thought the implementation through, but I've come across it on two separate projects and resorted to ugly workarounds on both.

Most modern CMS' allow new content types and their templates to be built and managed through the web, putting the ability to create forms-based types and build organisation-specific "micro applications in the hands of power users. Plone should be no different.

Of course, we still want to ensure there can be a good interface between such power users and developers building more advanced functionality, and a way to get information out of the ZODB to be managed appropriately, when required.

The content type side of this is one of the aims of the Dexterity project.