The Plone Content Management System
Plone is a mature, secure and user-friendly Content Management System (CMS).
Plone - and the Open Source community behind it - aggregates more than 15 years experience in content management. It offers all major features expected by a modern CMS out-of-the-box.
Lots of customizations can be made trough-the-web, such as creating content types, themes, workflows and much more. Pushed one step further Plone can be used as a framework on which to build custom CMS-like solutions.
Plone works as a
- full-featured classical server-side rendered CMS,
- headless CMS offering all features as a REST API.
Plone is available on Microsoft Windows, Linux, OSX and BSD platforms.
Plone runs as container in the cloud with Docker.
Consult the official Plone documentation with information for different audiences.
For trainings comprehensive Plone training material is available.
What is Plone?
Plone is a ready-to-run content management system, offering a complete set of features needed by a wide variety of organizations.
Security is built into Plone’s architecture from the ground up. Plone offers fine grained permission control over content and actions.
Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets.
- Plone is easy to install. Several installation options are available for either your local machine or on servers in the cloud.
- Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content.
- Plone is international. The Plone interface has more than 35 translations, and tools exist for managing multilingual content.
- Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3C’s AAA rating for accessibility.
- Plone is Open Source. Plone is licensed under the GNU General Public License, the same license used by Linux. This gives you the right to use Plone without a license fee, and to improve upon the product.
- Plone is supported. There are over three hundred developers in the Plone Development Team around the world, and a multitude of companies that specialize in Plone development and support.
- Plone is extensible. There is a multitude of add-on products for Plone to add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages.
- Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD.
Plone is a content management platform written in Python. It builds upon Zope, an Open Source web application server and development system and thus on the pluggable Zope Component Architecture (ZCA).
Python is the easy-to-learn, widely-used and supported Open Source programming language. Python can be used to add new features to Plone, and used to understand or make changes to the way that Plone works.
Plone stores its contents in Zope’s built-in transactional hierachical object database, the ZODB. The ZODB can be connected to simple file-storages, scalable ZEO-Servers or Postgres, MySQL and Oracle. There are addon and techniques, however, to share information with other sources, such as relational databases, LDAP, filesystem files, etc.
- plone.com - Official website for decision makers and evaluators.
- plone.org - Official website for developers and community.
- Plone support - Where to find help.
- community.plone.org - Official community forum, the best place to get help.
- docs.plone.org - Official documentation for developers/integrators.
- training.plone.org - Training classes for developers/integrators/users/designers.
- plone.api - Documentation for plone.api.
- plone.restapi - Documentation for plone.restapi.
- official Gitter chat - monitored.
- Release Plone 5.2.4 final [maurits]
- Removed plone.app.dexterity from dependencies. It is already required by Products.CMFPlone. [maurits]
- Release Plone 5.2.3 final [maurits]
- Release Plone 5.2.2 final [maurits]
- Release Plone 5.2.1 final [esteele]
- Release Plone 5.2 final [esteele]
- Release Plone 5.2rc5 [esteele]
- Release Plone 5.2rc4 [esteele]
- Release Plone 5.2rc3 [esteele]
- Release Plone 5.2rc2 [esteele]
- Release Plone 5.2rc1 [esteele]
- Add plone.restapi as a dependency. [timo]
- Release Plone 5.2a2 [esteele]
- Release Plone 5.2a1 [esteele]
- Release Plone 5.1.4 [esteele]
- Release Plone 5.1.3 [esteele]
- Release Plone 5.1.2 [esteele]
- Release Plone 5.1.1 [esteele]
- Release Plone 5.1 [esteele]
- Release Plone 5.1rc2 [esteele]
- Release Plone 5.1rc1
- Release Plone 5.1b4 [esteele]
- Add link to Plone.com and tweak intro [tkimnguyen]
- Release Plone 5.1b3 [esteele]
- Release Plone 5.1b2 [esteele]
- Remove plone.app.openid from core, still available as addon package. [jensens]
- Release Plone 5.1b1 [esteele]
- Be sure to require archetypes.multilingual even if it’s not required as a dependency of plone.app.multilingual. [davisagli]
- Release Plone 5.1a2 [esteele]
- Release Plone 5.1a1 [esteele]
- Release Plone 5.0.2 [esteele]
- Release Plone 5.0.1 [esteele]
- Release Plone 5.0 [esteele]
- Release Plone 5.0rc3 [esteele]
- Release Plone 5.0rc2 [esteele]
- Release Plone 5.0rc1 [esteele]
- Release Plone 5.0b4 [esteele]
- Release Plone 5.0b3 [esteele]
- Release Plone 5.0b2 [esteele]
- Release Plone 5.0b1 [esteele]
- Release Plone 5.0a3 [esteele]
- Move plone.app.theming dependency into Products.CMFPlone. [esteele]
- Release Plone 4.3.4 [esteele]
- Release Plone 4.3.3 [esteele]
- Release Plone 4.3.2 [esteele]
- Release Plone 4.3.1 [esteele]
- Release Plone 4.3 [esteele]
- Release Plone 4.3b2 [esteele]
- Release Plone 4.3b1 [esteele]
- Release Plone 4.3a2 [esteele]
- Release Plone 4.3a1 [esteele]
- Release Plone 4.2.1 [esteele]
- Release Plone 4.2 [esteele]
- Release Plone 4.2rc2 [esteele]
- Add explicit dependencies on some zope.app libraries, to ensure they stay included during the 4.2 series. [hannosch]
- Release Plone 4.2rc1 [esteele]
- Release Plone 4.2b2 [esteele]
- Release Plone 4.2b1 [esteele]
4.2a2 - 2011-08-25
- Release Plone 4.2a2 [esteele]
4.2a1 - 2011-08-08
- Release Plone 4.2a1 [esteele]
4.1 - 2011-07-12
- Release Plone 4.1 final [esteele]
4.1rc3 - 2011-06-02
- Release Plone 4.1rc3 [esteele]
4.1rc2 - 2011-05-21
- Release Plone 4.1rc2 [esteele]
4.1rc1 - 2011-05-20
- Release Plone 4.1rc1 [esteele]
4.1b2 - 2011-04-06
- Release Plone 4.1b2 [esteele]
- Depend on wicked now that Products.CMFPlone doesn’t. [davisagli]
4.1b1 - 2011-03-04
- Release Plone 4.1b1 [esteele]
4.1a3 - 2011-02-14
- Release Plone 4.1a3 [esteele]
4.1a2 - 2011-02-10
- Include plone.app.caching as an optional, shipped add-on. [esteele]
4.1a1 - 2011-01-18
- Separate Products.CMFPlone from the Plone egg. [elro]
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size Plone-5.2.4-py2.py3-none-any.whl (4.6 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View|
|Filename, size Plone-5.2.4.tar.gz (19.4 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for Plone-5.2.4-py2.py3-none-any.whl