Group items tagged

expect to see the total amount of lines of code to decrease further

more features with less lines

may be a node name

PATH SPECIFICATION

If no file path is provided then access goes only to the registered local nodes on the system

Useful pdb commands

s = step into, go into the function in the cursor n = step over, execute the function under the cursor without stepping into it c = continue, resume program bt = print stack trace up = go to the scope of the caller function

Useful pdb snippets

evaluate a whole slew

eye-opening

quite Plone-oriented

if you're paying someone by the day to come up with a recommendation

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

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

away from tight integration

The "federated" view of IT is more realistic as an option these days

better support for standards

more use of higher level "glue"

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

External Editor

training your in-house staff

specialist vendor

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.

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

Simply add one more line to your buildout.cfg within [buildout] section:

how simple it is to break a buildout

Links in a package’s description should not be parsed

Dead links should not be parsed by setuptools when running a buildout

setuptools have to ignore duplicated URLs in a package’s index

The local directory service node is referenced with /Local/Default