Skip to main content

Home/ Plone distributed documentation/ Group items tagged ZMI

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

Is Plone too hard? - Martin Aspeli - 0 views

martinaspeli.net/...is-plone-too-hard

2010 2010-01 2010-01-06 Plone (software)

shared by Graham Perrin on 06 Jan 10 - Cached
  • Is Plone too hard?
  • Feb 03, 2008
  • Themes are not themes, they are customisation
  • ...8 more annotations...
  • ZMI is not alway ideal
  • but it's powerful and quick as hell
  • The usual answer here is to use grep
  • can't find anything
  • Plone's performance is fine if you know how to set it up. We should make that easier by giving CacheFu an overhaul
  • Restarts suck. Slow restarts suck more
  • Each of these areas (and other ones) will need a "champion"
  • imagine we had an all-powerful introspection tool
Graham Perrin

On Plone documentation - Martin Aspeli - 1 views

martinaspeli.net/...on-plone-documentation

2008 2008-11 2008-11-23 Plone (software)

shared by Graham Perrin on 01 Apr 10 - Cached
  • I think it's a mistake to try and solve all the problems with "Plone documentation" in the same way
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      +1
  • rely more on technology
  • What is current good practice?
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      My initial reaction to this: get started | essential actions | refinements and current best practice …
  • ...20 more annotations...
  • a corpus small enough that it can be effectively reviewed
  • highlighted and easy to find
  • this is where they should be stumbling
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      Can we elaborate on this point?
  • Barriers to entry should be low
  • version the document pertains to
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      +1
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      Re http://dev.plone.org/plone/ticket/7831 some simple triggers might draw attention to documentation that becomes outdated (or at least deserves review) at product update time.
  • concerned about how easy it is to add an article
  • highlight the "good" bits of documentation
  • reviewed at least each time we make a new Plone release
  • What's the right way to configure caching?
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      Advice may be diverse.
  • If someone wants to contribute documentation, by all means let them!
  • allow comments
  • ratings of the type "was this helpful to you"
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      I do often rate things (positively more often than negatively). However: I rarely observe other people's ratings.
  • Open the flood-gates
  • group documentation by audience, rather than by type
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      I'm never wholly convinced about audience-based documentation.
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      Can we group documentation by layer - through the Plone (TTP), Zope management interface (ZMI), file system et cetera?
  • Accept that how-to documentation won't be perfect
  • Add ratings
  • improve commenting
  • this is out of date
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      Maybe "This is valid for version n.n of product x" plus "For more recent advice please visit …".
  • We should allow people to make requests for new documentation, and expose the wish list in a way that lets people vote for their favourite requests
    • Graham Perrin
      Graham Perrin on 01 Apr 10
       
      First improvements to a document might be: (1) a link to Trac, so that any documentation-related issue can be tracked; and (2) an in-document summary of relative tickets.
  • We have a Trac
1 - 3 of 3
Showing 20▼ items per page