Skip to main content

Home/ Groups/ Plone distributed documentation
Graham Perrin

Fixing Kupu in deliverance configuration - Finn Arild Music - 0 views

  • Fixing Kupu in deliverance configuration
  • Deliverance is a brilliantly smart concept
  • separating design from logic
  • ...7 more annotations...
  • combining several types of backend web applications into a frontend
  • Deliverance configuration
  • problems in making it play nicely
  • this page which shed some light
  • Varnish config
  • Kupu depended on a pristine /emptypage
  • a match instead of a proxy
Graham Perrin

who wants to be release manager for Deliverance? - 0 views

  • Deliverance Discussion
  • who wants to be release manager for Deliverance?
  • Nov 29, 2009
  • ...33 more annotations...
  • The situation right now is dismal
  • private fork of the code if they want to make any modifications
  • getting a stable, maintained release of this 0.3 incarnation out the door
  • right now the bottleneck is on the maintenance side
  • it would be really nice to see deliverance moving to some dcvs
  • Deliverance tries to solve a problem that very few people have: styling an existing site without having to touch it
  • Plone where you would need hundreds of hours of work of skilled people to do a full styling
  • if you use Deliverance you still need to theme your Plone site
  • a lot of interest in Deliverance
  • XDV, since that is easier to deploy in non-Python environments
  • Deliverance + a proxy is obviously possible
  • legacy systems
  • "shrink-wrapped" solutions that they can't style
  • All my Plone projects these days use Deliverance or XDV
  • turn off most Plone stylesheets
  • custom stylesheet to augment the designer's styles
  • include the Plone authoring stylesheets more or less intact
  • new to Plone
  • teaching theming
  • new to Plone theming
  • comprehension and productivity
  • With Deliverance/XDV, I can get people who understand HTML + CSS to be productive with Plone
  • a *huge* win
  • hard to set it all up
  • soluble
  • stable 0.3 release out is of utmost importance
  • revisit the option of moving it to a different repository later
  • it only takes a very little bit of stop energy to get someone to go away
  • I hereby bestow upon Ethan the title of Maintainer
  • release now, and figure out code location etc later
  • DVCS's genuinely useful for including people in a development process
  • get git working with the major IDEs
  • I'd be looking at fewer man pages with hg than with git
Graham Perrin

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

  • 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

New über-buildout with Repoze and Deliverance - Martin Aspeli - 0 views

  • Martin Aspeli
  • Aug 09, 2009
  • all-in-one
  • ...7 more annotations...
  • devleopment-and-production
  • using Repoze, WSGI and Deliverance
  • don't want to be dependent on a live internet connection for production deployment
  • based on the good-py
  • don't extend any remote services in the uber-buildouts
  • the goodness of: ZEO server4 ZEO clients running PasterSoftware load balancing using haproxyA Varnish cachenginx serving static content
  • über-buildout with Repoze and Deliverance
Graham Perrin

Simplify Plone's Editing Experience · Alexander Limi - 0 views

  • April 14th, 2008
  • Simplify Plone’s Editing Experience
  • Simplifying Plone’s content authoring experience for end-users
  • ...5 more annotations...
  • Part 1
  • bringing sexy back
  • Movie showing the new approach
    • Graham Perrin
       
      A very pleasant reminder of the simplicity that was envisaged around twenty months ago.
  • wrong the first time around
  • we should attack the root
Graham Perrin

Using Hudson CI for Plone projects - Martin Aspeli - 0 views

  • Nov 07, 2009
  • Martin Aspeli
  • Hudson Continuous Integration
  • ...4 more annotations...
  • provides a test runner that can output the types of XML test reports that Hudson expects
  • collective.xmltestreport
  • pretty easy to set it all up
  • Using Hudson CI for Plone projects
Graham Perrin

Table: Plone themes | CSS, viewlets, templates - 0 views

Graham Perrin

Is Plone too hard? - Martin Aspeli - 0 views

  • 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

No, really, you can (just) use Buildout to install Plone. « Alex Clark's Plon... - 0 views

  • Buildout to install Plone
  • Alex Clark
  • a follow up to my Getting Excited about Plone as Eggs post
  • ...13 more annotations...
  • “mostly trivial” to write a buildout.cfg to install Plone
  • a working Plone, but not necessarily a repeatable buildout
  • If you are completely new to buildout
  • install buildout first
  • Distribute
  • curl -O http://python-distribute.org/distribute_setup.py
  • python distribute_setup.py
  • easy_install zc.buildout
  • mkdir plone
  • cd plone
  • buildout init
  • bin/instance console
  • January 7, 2010
Graham Perrin

Plone 4 architecture - 38 views

  •  
    PDF
  •  
    One of the PNGs at http://www.wuala.com/Zope%20&%20Plone/Plone/2010/01/08/a is based on Martin Aspeli's PDF.
Graham Perrin

Request For Comments: My Plone/Apache Stack « jjmojojjmojo: In Effect - 2 views

Graham Perrin

Python Package Index : collective.pdfpeek - 0 views

  • collective.pdfpeek
  • generates image thumbnail previews
  • preview and thumbnail images of each page of uploaded PDF
  • ...2 more annotations...
  • annotated onto the content object containing the pdf
  • generation currently takes place on object modified events
  •  
    plone.org page for this product: http://plone.org/products/collective.pdfpeek/
Graham Perrin

Plone architecture diagram - 1 views

  •  
    N2C 498×692 pixels
Graham Perrin

Of babies and bathwater (or: Why I love the Zope Component Architecture) - Martin Aspeli - 0 views

  • Of babies and bathwater (or: Why I love the Zope Component Architecture)
  • Martin Aspeli
  • Dec 01, 2009
  • ...17 more annotations...
  • In defence of one of the great Python frameworks of the past decade
  • ZCA rocks. It's an incredibly advanced and powerful way to build software
  • ZCA adds complexity. It demands that you swallow its core concepts up front (interfaces, adapters, utilities, events) and get to know them pretty well
  • people can do crazy things, usually doing as much harm as good
  • elegant frameworks like BFG or Pylons
  • That doesn't mean the ZCA is right for all situations
  • learning to use the ZCA effectively is a bit like learning a new programming language on top of Python. You need to "get" those concepts
  • For the ZCA itself, there is clearly an opportunity right now to evolve
  • My personal wish-list
  • advice for projects, such as Plone, that use the ZCA for extensibility and inversion-of-control
  • Don't let the ZCA be the first API that people see
  • don't assume everyone has yet reached ZCA mastery
  • ZCA as a building block
  • BFG does this very well
    • Graham Perrin
  • We're trying to do something similar with Dexterity and the ecosystem of tools around it
  • The same will hopefully be true for other technologies as we move towards Plone 5
  • improved integrator learning curve
Graham Perrin

Unloading Plone - 0 views

Graham Perrin

Python Package Index : collective.xdv 1.0rc4 - 0 views

  • collective.xdv
  • Integrates the xdv Deliverance implementation with Plone
  • post-publication hook
  • ...5 more annotations...
  • XDV is an implementation of Deliverance
  • the original Deliverance XML-based syntax
  • compiling the theme (an HTML file) and rules (an XML file) into a single XSLT file
  • on render
  • applied to Plone's HTML
Graham Perrin

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

  • 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
‹ Previous 21 - 40 of 117 Next › Last »
Showing 20 items per page