Difference between "Document" and "Slice" field.

[rqelibari]

Hi,

what exactly is the difference between a "Slice" and a "Document" field. "Slice-Content" seems to be just another "Content Type", with the restriction, that it may no be queried directly, but instead has to be referenced in a "Slice" field of a standard "Content Type".

Am I right, when I think of a "Document" field named myField to correspond to the following GraphQL schema:

[...]
union MyFieldDocument = SomeType1 | SomeType2

type MyContentType {
    myField: MyFieldDocument!
}
[...]

If that is right, what exactly does "Slize" correspond to?

[birkir]

Document is a field that you can reference another documents with many-to-many relationships.

Slice is a field that allows slices (like documents) within your document that has one-to-many relationship.

I am re-using ContentType to store the schema of the two, but fundamentally, they are different. The UI is a little bit confusing, and I tend to fix that soon.

Document(Author)[] <> Document(Blog)[]
Document(Blog) > Slice(Foo | Bar | Baz)[]
Document(Author) > Slice(Baz | Foo)[]

Nobody owns documents content
Document owns Slices content

[intellix]

Was also wondering the same thing actually. Used the Deploy to Heroku feature and am playing around with Prime.

I can add a Document and pick both Slices and Documents, which lead me to confusion but I think it shouldn't be allowed? After having a Document field with both documents and slices I get errors after visiting the Documents page:

[birkir]

Yes, that should not happen. I am hoping to be able to update the UI to not show Slices in the Schema tabs (Content Types/Templates/Slices) but rather inside Content Types themselfs.

However I want them to be shared between content types too, so I will figure something out there