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

Migrate plone.app.dexterity docs into Plone 6 Documentation #1445

Open
1 of 2 tasks
MrTango opened this issue Feb 15, 2023 · 5 comments
Open
1 of 2 tasks

Migrate plone.app.dexterity docs into Plone 6 Documentation #1445

MrTango opened this issue Feb 15, 2023 · 5 comments
Assignees
Milestone

Comments

@MrTango
Copy link
Contributor

MrTango commented Feb 15, 2023

Plone Documentation versions affected

  • 5.x
  • 6.x

Description

To make it easier it would be nice to have the external docs from https://github.com/plone/plone.app.dexterity also as a myst version. The final docs will be part of the new mains docs, no sub repo.

@stevepiercy
Copy link
Contributor

Refs: plone/plone.app.dexterity#360

@stevepiercy stevepiercy added this to the Plone 6.0 milestone Feb 15, 2023
@rakshith6404 rakshith6404 modified the milestones: Plone 6.0, Plone 6.1 Mar 2, 2023
@stevepiercy stevepiercy changed the title convert docs from plone.app.dexterity to myst version Migrate docs from plone.app.dexterity May 24, 2023
@stevepiercy
Copy link
Contributor

The source files now reside at plone.app.dexterity, and are awaiting a content expert to review them and place them in their home.

@stevepiercy stevepiercy pinned this issue May 24, 2023
@stevepiercy stevepiercy changed the title Migrate docs from plone.app.dexterity Migrate plone.app.dexterity docs into Plone 6 Documentation May 24, 2023
@MrTango
Copy link
Contributor Author

MrTango commented Apr 11, 2024

I'm working on the chapter "Rich text, markup and transformations":

Python docs including RichTextValue details should go into fields.
I'm still oundering if the template part should go into templates or stay with the RichText field?
@petschki @jensens @pbauer opinions on this?

@MrTango
Copy link
Contributor Author

MrTango commented Apr 11, 2024

see #1648

@jensens
Copy link
Sponsor Member

jensens commented Apr 17, 2024

I'm still oundering if the template part should go into templates or stay with the RichText field?

IMO it is better keeps things together in one place here. In "templates" point readers to this place.
I don't like it if information is scattered around the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants