b-org: Creating content types the Plone 2.5 way

Plone 2.5 brings us closer to the promised land of Zope 3. Zope 3 brings us a new way of working. This tutorial will show how to marry the old and the new, to make Plone products that are more extensible, better tested and easier to maintain.

1. Introduction What is b-org, and what will you learn here?
2. A whirlwind tour of Zope 3 Zope 3 is still fairly new. After reading this tutorial, it should hopefully start to feel a bit more familiar. In this section, we will give a brief overview of what is different in Zope 3 and how it fits into Plone.
3. Overview of b-org The big picture
4. To Archetype or not to Archetype Archetypes is still the most complete framework for building content types quickly. With the advent of Zope 3, there is an alternative in Zope 3 schemas. Here's why b-org doesn't use them.
5. The extension story One of the main drivers behind the componentisation of b-org is that it should be easy to extend and customise for third party developers. We'll take a look at how such customisations may look, before considering how we made it possible.
6. Filesystem organisation b-org attempts to adhere to modern ideal about how code should be laid out on the filesystem.
7. Interfaces In Zope 3, everything is connected to an interface in some way. Sure enough, b-org has a slew of them. Getting the interface design right is often more than half the battle, so pay attention to this part.
8. Test-driven development Testing should come first, not last, when doing development.
9. Setup using GenericSetup b-org uses GenericSetup to impose itself on your Plone instance. Here's how it works.
10. Using membrane to provide membership behaviour How b-org uses membrane to let employees be users and departments be groups
11. Writing a custom PAS plug-in Projects require that members are given particular local roles within a project space. This is achieved using a custom PAS plug-in.
12. Placeful workflow b-org uses CMFPlacefulWorkflow, which ships with Plone 2.5, to manage the workflow of content objects inside a project.
13. Sending and handling events Events is undoubtedly one of the most useful things that Zope 3 brings to the Zope 2 world. Here's how b-org uses them.
14. Annotations Annotations are an elegant solution to the "where do I store this?" problem, and are used in many Zope 3 applications.
15. Zope 3 Views One of the nicest things that Zope 3 brough us is a way to manage view logic.

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