Skip to content

The Dexterity-reference from the training and the dexterity docs should both move into docs #1298

Description

@stevepiercy

The Dexterity-reference from the training (https://training.plone.org/mastering-plone/dexterity_reference.html) and the dexterity docs should both move into plone/documentation. I would not pull the dexterity docs in (as a submodule) but rather move it there since it is very very "core".

Sources

Advantages

  • Core docs should be in the plone/documentation, instead of scattered across multiple repositories.
  • More likely to get contributions through the plone/documentation repository. No need to explain, "Oh, sorry, you have to go over to plone/plone.app.dexterity to update this one section of the docs."
  • No need to deal with submodules.

Disadvantages

  • Docs would not be kept together with the project.

To Dos

See also

Originally posted by @pbauer in #1290 (comment)

Activity

  1. added this to the Plone 6.0 milestone on Sep 7, 2022
  2. jensens commented on Sep 8, 2022

    @jensens
    SponsorMember

    +100

    Also consider to include the plone.behavior readme https://github.com/plone/plone.behavior/blob/master/README.rst (and reduce it to a link to the docs).

  3. stevepiercy commented on Sep 8, 2022

    @stevepiercy
    MemberAuthor

    Also consider to include the plone.behavior readme https://github.com/plone/plone.behavior/blob/master/README.rst (and reduce it to a link to the docs).

    Agreed. Created new issue: #1309

    Are there other external docs that should be moved into plone/documentation?

  4. moved this from New to Todo in Plone Documentationon Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions