Relations reordering: Dev docs updates - alternative

[pwizla]

Reworks #1324 with a streamlined, hopefully simpler approach:

• simpler structure (lighter in the TOC)
• tables
• tabs for various examples with the full context

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
documentation	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 17, 2023 at 1:39PM (UTC)
documentation-docu-mvp	❌ Failed (Inspect)			Jan 17, 2023 at 1:39PM (UTC)

[Boegie19]

Should the relations part of this documentation not also exist under:

• Entity Service API
• GraphQL API
• Query Engine API

With some small modifications to the examples?

Also it mind be worth to add to the docs what happens if connect a already existing relationship in an update.
Since you can do that to change the position of a relationship
if you do connect instance without adding a position it should do noting if it already exists.

[Marc-Roig]

sublime :) Can't see anything more to add.

[pwizla]

Note: This PR will be merged for the beta release, and we'll have another shorter PR to remove beta mentions to get ready for GA.

[pwizla]

Should the relations part of this documentation not also exist under:

* Entity Service API

* GraphQL API

* Query Engine API

With some small modifications to the examples?

Thanks for your question, @Boegie19! The syntax explained for the REST API will be exactly the same for the Query Engine and Entity Service APIs so we've only added this callout to redirect to the related REST API page.