See http://microformats.org/wiki/Main_Page
At least hCalendar, rel-nofollow, hCard, and rel-license make sense. geo would be good too.

It should be possible to easily move a portlet from one portlet manager to another.
Use Case: drag the calendar portlet from portal_column_one to portal_column_two.

Perhaps the planned blocks system already solves this issue.

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.

There should be a consistent application programming interface into Plone so that applications already developed for Plone do not break when certain features are no longer supported in new versions of Plone. It is my impression that many third party applications for developed for earlier versions of Plone have lapsed because of the amount of work involved in adapting them to new versions of Plone. The learning curve is high enough as it is without having to go through the process again with new versions.

Recently, many portable devices support geotag data. It might be good to have geotag for all contents type as a standard metadata. Contents can be organized in terms of location and timing. Could be a good source for animation on the map.

HTML markup should not be hard-coded, for example in Plone 3 it is very hard to have complete design control over error messages, because the markup for these messages is fixed in a certain way and buried deep somewhere in the core code. Should really separate markup from logic completely.

Edge Side Includes (ESI) allows a cache server to cache parts of a page.The Plone UI is now pretty modular and it ought to be possible to assign a URL to each part (e.g. viewlets and portlets in an own ++ namespace), and a caching server like Varnish could cache individual portlets and viewlets that do not change with who is logged in.

If you have a site which is using references between content, you don't have the possibility to name the references. If you for example have a reference between a page describing an organizational unit and a page describing a manager, it should be possible to add the name "Manager" as the name of the reference added on the organizational unit page.

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.

If multiple Plone Instaces run on on Zope server, you should be able to index all of these instances and search from any. It is a great addition if different departments have their own instance on one server.

<http://commontag.org/>

> … open tagging format … Common Tags are references to unique, well-defined concepts, complete with metadata and their own URLs …

<http://groups.diigo.com/Web2/bookmark/tag/%22Common+Tag%22> for a Diigo highlighted view of some related pages.

It would be nice an Integrated Development Environment with the following features:
- API auto-completion
- Common templates
- pre-defined templates (e.g. portlet)
- copy some existing templates in your product
- user-defined templates
- Common elements:
- select with tal:repeat
- label with i18n:translate

It could be an Eclipse plugin that reads the Plone sources in order to get the updated API.

Common elements could be added with a toolbar with buttons like "Plone select", "Plone label", etc. like ColdFusion toolbar for Dreamweaver

People should be able to just browse through login-protected contents, even if they have other than a reader role for those contents. Instead of directly displaying all the content bars and actions for editing upon login, there should be an action/button/link to get to the 'editing mode'.

- 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 )

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.

It should be possible to enable saving of large files (like audio, video, images etc. outside the catalog with default plone setup (from the control panel). One option for images could be to save images larger than (PIL) max size outside the catalog (= all pil sizes are saved in the cartaog, while the 12Mb image the user uploaded is kept outside....)

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.

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.