The map structures the content and shows clear borders between different subjects and tasks.

• Visual Customization (Templates, ZPT, main_template, macros, CSS, Javascript)
• Product Management
• Site Setup and Configuration which should probably include:
  

Membership (sources, roles, group management)

Kupu (Configuration)

Workflows

• External Services (email, database, etc)
• Content Types (Component Architecture, Archetypes, ZCML, Python best practices)
• Forms
• Internationalization
• Creating content with Plone (Pages, Folders, Images...) and Using Kupu
• Content creation (including working with MS Office documents)
• Catalogs (portal_catalog, searches, options for searches)
• Server administration
• Developer best practices.

Possible inspirations

• Definitive Guide to Plone
• Plone Architecture — slide 12 of 99 within Plone 3: a swiss army knife for portals and extranets — if we view each one of the the portions within the circle as an area of interest (a viewpoint), and if our own perspectives of plone and related architectures differ from that example, then — with audience-oriented documentation in mind — audience diversity may be greater than we imagine.
  

(Please see: http://plone.org/documentation/how-to/review-documentation/#help-audiences for why I reorganized some of the items above; also review the history/version comments for more info. -Darci 4/15/07)