Skip to content

Commit

Permalink
Merge pull request #302 from flipmcf/#301
Browse files Browse the repository at this point in the history
Update intro suggesting deprication of Archetypes
  • Loading branch information
jensens authored Nov 5, 2019
2 parents 1bb0f89 + 21798f0 commit b08b01f
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
5 changes: 3 additions & 2 deletions docs/intro.rst
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ Some of the main differences include:
* It is possible to extend the schemata of existing Archetypes types with the archetypes.schemaextender product, although this adds some performance overhead and relies on a somewhat awkward programming technique. Dexterity types were built to be extensible from the beginning, and it is possible to declaratively turn on or off aspects of a type (such as Dublin Core metadata, locking support, ratings, tagging, etc) with re-usable "behaviors".
* Dexterity is built from the ground up to support through-the-web type creation. There are products that achieve the same thing with Archetypes types, but they have to work around a number of limitations in the design of Archetypes that make them somewhat brittle or slow. Dexterity also allows types to be developed jointly through-the-web and on the filesystem. For example, a schema can be written in Python and then extended through the web.

All that said, Archetypes is still an older and more mature framework. Dexterity is a viable alternative to Archetypes in many projects, but if you are happy with Archetypes, you should not immediately rush to rewrite your types to use Dexterity.
As of version 5 of Plone, Dexterity is the preferred way of creating content types.
Additionally, Archetypes was removed from Plone core in 5.2.
Archetypes can still be added to Plone 5 to support Archetypes-based add-ons, but it will not function when running Plone using Python 3.

There are also some things that Dexterity does not yet support, or, more commonly, services that Plone ships with that currently assume all content objects are built using Archetypes. The current list of "gaps" can be found in the Dexterity issue tracker. You should take a look at this before deciding whether Dexterity will work for you. If in doubt, don't hesitate to write to the Dexterity mailing list and ask for advice.
1 change: 1 addition & 0 deletions news/302.bugfix
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Update documentation introduction w/r/t archetypes (#301)

0 comments on commit b08b01f

Please sign in to comment.