You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that these two paragraphs need a bit more work now that Plone 5.2 is out.
I'm willing to get my feet wet and do a commit to the documentation. I'm nervous about being correct. I'll do a PR and see if I can get us closer to today's reality.
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.
The text was updated successfully, but these errors were encountered:
I noticed that these two paragraphs need a bit more work now that Plone 5.2 is out.
I'm willing to get my feet wet and do a commit to the documentation. I'm nervous about being correct. I'll do a PR and see if I can get us closer to today's reality.
The text was updated successfully, but these errors were encountered: