Personal tools
You are here: Home → Documentation → Tutorials → Best Practices for Plone development
Support

Get Help

Join our chat rooms or support forums if you have more specific questions.

Plone Training
Learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.
Find Plone training…
 
Document Actions

Best Practices for Plone development

This Tutorial applies to: Any version.
This Tutorial is intended for: Developers

Based on the talk given by Joel Burton at the Plone Conference in Vienna, this Tutorial discusses some of the best practices for Plone development. If you are doing site development with Plone and want to keep your sanity, this is a must-read. Requires some familiarity with Zope and Plone.

pupq

All content on one page (useful for printing, presentation mode etc.)

  1. The Basics Things everyone should know.
  2. Working off the file system The benefits of working on the file system as opposed to in the ZMI.
  3. Source Code Management A brief overview of Source Code Management and some bests-practices for revision control systems - setup and day-to-day use.
  4. Configuration management Managing different configurations across Plone sites is important. Too many people stick configuration in the ZMI, and have no setup scripts.
  5. Project Documentation A quick overview of some of the tools that can help you document your project for other developers.
  6. Debugging Plone Life without debuggers is hard. Here's what you need to know to get a better life.
  7. Developing, Staging, Syncing Working in one location and syncing that work to another location is critical if you want to be an efficient Plone developer. Here are some tips.
  8. Unit Testing One of the best investments you can make is to learn how unit testing works. Working without unit tests is at best risky, and in bigger projects - outright irresponsible.
  9. Credits People who helped and inspired this tutorial.
 
by Joel Burton — last modified February 12, 2006 - 15:18 All content is copyright Plone Foundation and the individual contributors.

links to useful debug info

Posted by gerrykirk at January 3, 2005 - 19:12

add some links to other useful docs, like http://www.zope.org/Members/klm/ZopeDebugging/ConversingWithZope

Gotcha w/ zopectl debug

Posted by Chad Whitacre at January 3, 2005 - 21:29

Afaict Zope has to be stopped in order to debug.

Use the ZEO, Luke!

Posted by Alexander Limi at January 8, 2005 - 23:05

With several instances, you always have an instance ready for debug work.

Short example

Posted by constantin at January 27, 2005 - 13:17

Hi,

These sound lik egood ideas. I know I am always running around trying to find the changes I made over several months to site 1 to be able to copy them to site 2. But how does one start with this? How to make a site product?

For the first suggestion: I guess I really have to learn to build a product now.

Small example

Posted by constantin at February 7, 2005 - 21:13

Hi, I like this kind of info, but maybe some small examples could help? I think that using an efficient approach will help people to understand Plone and develop better products, which will benefit Plone as a whole. However, some of these tips are (for me at least) too theoretical. Some help to get started will be very helpfull.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by