Update intro suggesting deprication of Archetypes #302
Conversation
First stab at new intro paragraph. I'm not in love with it.
|
@flipmcf you need to sign the Plone Contributor Agreement in order to merge this pull request. Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html |
|
@flipmcf thanks for creating this Pull Request and help improve Plone! To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass. Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating: With this simple comment all the jobs will be started automatically. Happy hacking! |
|
Agreement signed. |
|
Fixes #301 Improves:
Changes proposed in this pull request:
|
|
@flipmcf thanks for creating this Pull Request and help improve Plone! To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass. Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating: With this simple comment all the jobs will be started automatically. Happy hacking! |
docs/intro.rst
Outdated
| 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. |
There was a problem hiding this comment.
Content is fine, but please follow the doc style for all new edits; here: One sentence per line.
https://docs.plone.org/develop/styleguide/documentation.html
There was a problem hiding this comment.
https://docs.plone.org/about/contributing/documentation_styleguide.html is correct link to documentation styleguide.
There was a problem hiding this comment.
Sorry, I totally missed that you edited the CHANGES.rst. For various reasons we switched to using towncrier now for almost all Plone repositories. Please add a file to the /news/ folder named 302.bugfix and add the changelog line there.
|
Force push reverted CHANGES.rst back. |
First stab at new intro paragraph. I'm not in love with it.
Maybe we should remove the suggestions that "Dexterity is an alternative to Archetypes" and update our history to suggest that Plone embraced Dexerity as of version 5 and deprecated it at 5.2