Skip to main content

Home/ Plone distributed documentation/ Group items tagged unread

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

The Zope Book (2.6 Edition): Acquisition - 0 views

www.zope.org/...Acquisition.stx

2009 Zope acquisition Plone (software) unread

shared by Graham Perrin on 26 Feb 10 - Cached
  • Acquisition
  • allows dynamic behavior to be shared between Zope objects
  • containment
  • ...4 more annotations...
  • understanding of acquisition is important
  • Acquisition vs. Inheritance
  • Objects are situated inside other objects. These objects act as their "containers".
  • may acquire behavior from their containers
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

PloneEdu - 0 views

weblion.psu.edu/ploneedu

2010 2010-05 2010-05-21 Plone (software) unread

shared by Graham Perrin on 21 May 10 - No Cached
  • PloneEdu
  • Promoting open source web publishing for all levels and types of education
  • collaboration, knowledge sharing, and support of Plone
Graham Perrin

Review of Veda Williams' Plone 3 Theming - ACLARK.NET, LLC - 0 views

aclark.net/...-veda-williams-plone-3-theming

2009 2009-11 2009-11-10 unread Plone (software)

shared by Graham Perrin on 10 Nov 09 - Cached
  • Veda Williams'
  • Review
  • Plone 3 Theming
  • ...14 more annotations...
  • If you are interested in Plone and how Plone theming works
  • chapter by chapter review
  • I would have liked to have seen the PyPI features of plone.org mentioned
  • still hard to create Plone themes
  • tool for releasing themes (and any package) to both plone.org/products and pypi.python.org at the same time
  • http://pypi.python.org/pypi/jarn.mkrelease
  • Chapter 15 This chapter (by Alexander Limi) introduces people to "new style" theming
  • a while before it is fully digested
  • http://pypi.python.org/pypi/collective.xdv
  • great stuff but potentially confusing
  • XSLT transform "on the fly" (in memory)
  • but the recommended deployment strategy is to use NGINX or Apache with Laurence's patches
  • plone.org uses it
  • non-trivial to say the least
1 - 6 of 6
Showing 20▼ items per page