add chapter on relations from mastering plone (slighty updated)

[pbauer]

No description provided.

[netlify]

✅ Deploy Preview for 6-dev-docs-plone-org ready!

Name	Link
🔨 Latest commit	63b521e
🔍 Latest deploy log	https://app.netlify.com/sites/6-dev-docs-plone-org/deploys/63231f189a3b080007103712
😎 Deploy Preview	https://deploy-preview-1290--6-dev-docs-plone-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[ksuess]

From time to time I think it would be good to stop defining target sets of a relation field in its widget. Cause this is a constraint of its data structure (Plone: schema) and not a matter of the display (Plone: widget).

[stevepiercy]

I will review this in the next day or two. I'm working on other docs at the moment. Please do not merge yet. Thank you!

[stevepiercy]

General comment, with details coming in a full review later.

Documentation should be the authoritative source, not Training. We should pull content from the Training, and insert and adapt it in Documentation.

If that is too much work for now, then I would be OK with leaving the seealso directives on the previously empty pages (for example, docs/backend/behaviors.md) because it is an improvement, giving the reader something to use as a reference. We should also add a todo directive for each of these pages, and create a new issue in the Documentation issue tracker for each one.

I also think that this would give some newbies an opportunity to contribute by repurposing Training material into Documentation. Or so I hope.

@pbauer what do you think?

[stevepiercy]

This is my first round of review.

I did not start on the mammoth backend/relations.md, but I will start nibbling on that pachyderm one bite at a time over the next day or so.

[pbauer]

Documentation should be the authoritative source, not Training. We should pull content from the Training, and insert and adapt it in Documentation.

Yes. The chapters on relations, and the dexterity-reference can be moved to the docs without mayor changes. I'll remove them from the training and link to the docs once these are merged.

If that is too much work for now, then I would be OK with leaving the seealso directives on the previously empty pages (for example, docs/backend/behaviors.md) because it is an improvement, giving the reader something to use as a reference. We should also add a todo directive for each of these pages, and create a new issue in the Documentation issue tracker for each one.

Yes

I also think that this would give some newbies an opportunity to contribute by repurposing Training material into Documentation. Or so I hope.

You can always hope but I doubt it.

[stevepiercy]

Issues created:

• Backend > Behaviors needs content #1302
• Backend > Content Types needs content #1303
• Backend > Control Panels needs content #1304
• Backend > Fields needs content #1305
• Backend > Vocabularies needs content #1306
• Backend > Widgets needs content #1307
• Backend > Workflows needs content #1308

[stevepiercy]

Added meta data and TODOs in 443a010.

[stevepiercy]

I'm going to continue editing and pushing commits to this tomorrow. The commits I pushed so far are just meta and technical stuff that we should include in docs.

[stevepiercy]

This is excellent work. To save review cycles, I made lots of nit-picky commits to clean up English and MyST syntax and grammar.

I have a few additional questions. Please see the comments and suggestions.

Thank you!