Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

last paragraphs in intro needs rewrite #301

Open
flipmcf opened this issue Oct 30, 2019 · 0 comments
Open

last paragraphs in intro needs rewrite #301

flipmcf opened this issue Oct 30, 2019 · 0 comments
Assignees

Comments

@flipmcf
Copy link
Contributor

flipmcf commented Oct 30, 2019

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.

@flipmcf flipmcf self-assigned this Oct 31, 2019
jensens added a commit that referenced this issue Nov 5, 2019
Update intro suggesting deprication of Archetypes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant