Skip to main content

Home/ Plone distributed documentation/ Group items tagged help

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

Why do none of the bookmarks refer to Plone support forums? - 6 views

The combination of Nabble embedded content + forced redirection to plone.org - in particular, the way in which all topics and all messages within a forum are represented as myriad anchors to a si...

started by Graham Perrin on 12 Nov 08 no follow-up yet
Graham Perrin

Relating content automatically in Plone - Vox - 0 views

hvelarde.vox.com/...nt-automatically-in-plone.html

2010 2010-01 2010-01-10 Plone (software)

shared by Graham Perrin on 12 Jan 10 - Cached
  • list of related content automatically
  • Relating content automatically in Plone
  • automatically
  • ...24 more annotations...
  • 02-ene-08
  • Term Extraction
  • Benjamin Saller
  • haystack_tool included a couple of methods
  • summarize text
  • list of "topics" extracted from the content
  • portlets to demonstrate its functionality
  • low quality of the "topics"
  • didn't understood the meaning of words
  • linguistic mapping and automated conceptual mapping, providing high-quality relationships with little or no human effort
  • a proof-of-concept product called Haystack
  • python implementation
  • Implementing this in Plone
  • or use Content Rules
  • trigger a script in a workflow transition
  • fill the Subject field
  • additional field to store
  • better  quality
  • list of pending stuff to test (with a little help of Matt Bowen, of course)
  • Great idea
  • python text summariser which doesn't require Yahoo's web service
  • http://pypi.python.org/pypi/topia.termextract
  • several ways to relate content, both based on keywords and based on explicit relationships, in stock Plone
  • This article is about automatic text summaries based on linguistic analysis
Graham Perrin

Plone and its competition: choosing a CMS - Martin Aspeli - 0 views

www.martinaspeli.net/...plone-and-its-competition

2010 2010-01 2010-01-08 Plone (software) unread

shared by Graham Perrin on 08 Jan 10 - Cached
  • Plone and its competition: choosing a CMS
  • Martin Aspeli
  • Jul 06, 2009
  • ...79 more annotations...
  • evaluate a whole slew
  • eye-opening
  • quite Plone-oriented
  • vendors' marketing materials decidedly do not help
  • if you're paying someone by the day to come up with a recommendation
  • Vendor Subway Map
  • features they have in their product arsenal
  • Plone sits on the intersection of the "Web content management", "Social software & collaboration" and "Enterprise portal" lines
  • cost (both licensing and likely implementation costs), fit with your existing IT architecture, and usability/end-user experience become a lot more important
  • focus on getting a list of requirements for your end solution
  • Vendor demos have a tendency to gloss over the warts
  • The word "CMS" - Content Management System - is quite overloaded
  • Plone is really a Web CMS
  • vendors sometimes focus mainly on content production
  • Other vendors include a dedicated presentation server
  • Some systems, like Plone, accommodate both in a single server
  • away from tight integration
  • towards federation of services on heterogeneous platforms
  • The "federated" view of IT is more realistic as an option these days
  • better support for standards
  • more use of higher level "glue"
  • Deliverance
  • plone.org, for example, "deliverates" Plone and Trac
  • federated architecture that presents a unified user experience
  • In the Java world, there are more formal standards (notably JSR168 and it's successor JSR186)
  • in theory
  • built once and deployed onto different portal containers
  • An intranet or public website should largely present
  • a stable, well-thought-out information architecture
  • a richer, more bespoke, less application-like user experience
  • a shift away from this one-platform-to-rule-them-all mentality
  • some of the "platform" arguments are red herrings
  • External Editor
  • training your in-house staff
  • pick a solution that is supportable
  • specialist vendor
  • Most modern systems are so complex that you can't just expect your IT staff to be able to support them without at last some investment in training
  • Bake vs. fry
  • Assets vs. content
  • In Plone, there is a structured hierarchy
  • content tree
  • mirrors how files are managed on the desktop
  • Folders and taxonomy
  • Plone is comparatively weak
  • Pages and fragments
  • Managing code and content
  • Zope and Plone communities have done a lot of work to move development out onto the filesystem
  • The contenders Below is a list of systems I think are worth looking at and learning from.
  • Usability is king
  • Even Open Text/RedDot, which says in every "datasheet" that Gartner calls its usability "legendary", is confusing to use at times, and many of the other systems - especially the older ones - are downright shocking
  • just to install the system and click
  • most enlightening evaluation
  • If I can't figure it out easily, it's not good enough
  • What Plone can learn All in all, this evaluation exercise has confirmed my belief that Plone can hold its head high in the web content management world.
  • support for the "bake" model
  • file representation of all content
  • upload content easily
  • browse the site via WebDav
  • IT support staff need to be able to feed and water the servers your CMS runs on
  • Morello has an interesting take
  • integration with Microsoft Office and the desktop
  • dragged from the desktop and dropped into the CMS
  • Open Text/RedDot has a nice model
  • RESTful web services
  • integration with other systems much easier
  • group workspaces
  • already decent add-on products
  • dashboard
  • first thing users see
  • content notification
  • "star" content they care about
  • content re-use
  • support for taxonomy
  • multi-site support
  • through-the-web content types and templates
  • page composition
  • Deco system
  • Conclusion
  • Plone UserVoice forum
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
Graham Perrin

Amberjack Lightning Talk - 0 views

www.slideshare.net/...amberjack-lightning-talk

Plone HTML JavaScript Amberjack guide tour help start basic i18n presentation

shared by Graham Perrin on 25 Jul 09 - Cached
  • Graham Perrin on 25 Jul 09
1 - 5 of 5
Showing 20▼ items per page