A Plone API

Overview

The plone.api is an elegant and simple API, built for humans wishing to develop with Plone.

It comes with cookbook-like documentation and step-by-step instructions for doing common development tasks in Plone. Recipes try to assume the user does not have extensive knowledge about Plone internals.

The intention of this package is to be transitional. It points out the parts of Plone which are particularly nasty -- we hope they will get fixed so that we can deprecate the plone.api methods that cover them up, but the documentation can still be useful.

Some parts of the documentation already are this way: they don't use plone.api methods directly, but simply provide guidance on achiving a task using Plone's internals. Example: usage of the catalog in content_find_example.

The intention is to cover 20% of the tasks we do 80% of the time. Keeping everything in one place helps keep the API introspectable and discoverable, which are important aspects of being Pythonic.

Note

This package is still under development, but should be fairly stable and is already being used in production. It's currently a release candidate, meaning that we don't intend to change method signatures, but it may still happen.

Indices and tables

Table Of Contents

About Plone

This is documentation for Plone®. Plone is a popular, open source, content management system written in Python programming language.

Edit this document

The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.

  1. Go to A Plone API on GitHub.
  2. Press the Fork button. This will create your own personal copy of the documentation.
  3. Edit files using GitHub's text editor in your web browser
  4. Fill in the Commit message text box at the end of the page telling why you did the changes. Press the Propose file change button next to it when done.
  5. Then head to the Send a pull request page (you won't need to fill in any additional text). Just press Send pull request button.
  6. Your changes are now queued for review under project's Pull requests tab on Github.

For basic information about updating this manual and Sphinx format please see Writing and updating the manual guide.