Matt Hamilton: plone.com
Talking about writing content for plone.com during the PLOG 2012.
More info about PLOG 2012: http://www.abstract.it/abstract-en/initiative/plone-open-garden-2012/
Goal: multilingual gateway to Plone for decision makers, managers, recommenders, press. Feature list. Mostly not software. Super cached for outstanding performance. Experience should be very user-focused.
Messages: Plone is active, pervasive, actively getting better, open source done right. Focus points: quality, security, testing, ease of use by content managers.
See idealware.org report Comparing Open Source CMSs: WordPress, Joomla, Drupal, and Plone: http://www.netsight.co.uk/blog/open-source-content-management-systems-a-tale-of-two-reports
We have ideas for the basic site structure.
What is of interest to a developer may not be interesting for an end user or decision maker. On plone.org as non-technical user you are lost. We should ask feedback from end users.
When a client of Abstract picked Plone, they still missed something like plone.com to explain to some of the decision makers what Plone actually is, compared to in this case Joomla.
For new developers it would help to have a document explaining Plone for Joomla developers or Wordpress developers, using their terms, their vocabulary, comparing technologies.
Gartner would not investigate Plone, because Plone is not a company.