From 6c95d23c3b756d130a1634420f7374d0661be35e Mon Sep 17 00:00:00 2001 From: Flip McFadden Date: Wed, 30 Oct 2019 12:19:08 -0400 Subject: [PATCH 1/3] Update intro suggesting deprication of Archetypes First stab at new intro paragraph. I'm not in love with it. --- docs/intro.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/intro.rst b/docs/intro.rst index ef458cca..26b3ca2e 100644 --- a/docs/intro.rst +++ b/docs/intro.rst @@ -54,6 +54,4 @@ 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. - -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. +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. It can still be added to Plone to support Archetypes-based add-ons, but it will not function when running Plone using Python 3. If you are considering upgrading to Plone 5 and Python 3, you are reading the right documentation. From 955396cd7ee2a62e9091e5c49efd3955428aa5b7 Mon Sep 17 00:00:00 2001 From: flipmcf Date: Mon, 4 Nov 2019 12:57:04 -0500 Subject: [PATCH 2/3] update news --- news/302.bugfix | 1 + 1 file changed, 1 insertion(+) create mode 100644 news/302.bugfix diff --git a/news/302.bugfix b/news/302.bugfix new file mode 100644 index 00000000..a1d5bca7 --- /dev/null +++ b/news/302.bugfix @@ -0,0 +1 @@ +Update documentation introduction w/r/t archetypes (#301) From 21798f08951f3ae98eb3821438d4fd6f310f7916 Mon Sep 17 00:00:00 2001 From: flipmcf Date: Mon, 4 Nov 2019 13:02:13 -0500 Subject: [PATCH 3/3] Apply styleguide --- docs/intro.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/intro.rst b/docs/intro.rst index 26b3ca2e..a5fb1414 100644 --- a/docs/intro.rst +++ b/docs/intro.rst @@ -54,4 +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. -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. It can still be added to Plone to support Archetypes-based add-ons, but it will not function when running Plone using Python 3. If you are considering upgrading to Plone 5 and Python 3, you are reading the right documentation. +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. +