deleted 204 characters in body
Source Link

Given this modelling part, relavantrelevant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model.
It works without Link (schema/model). Why? I was suprised ;-)
Other XML name then "internalLink" didn't work.

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with XMLxml name "internalLink" (like inside website above)?

Q4- Can use the Xml Name for both?

Datamodel contains two exact same schema's "ListItemLijst".
One for component link and one is Embeddable.

Given this modelling part, relavant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model.
It works without Link (schema/model). Why? I was suprised ;-)
Other XML name then "internalLink" didn't work.

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with XML name "internalLink" (like inside website above)?

Q4- Can use the Xml Name for both?

Datamodel contains two exact same schema's "ListItemLijst".
One for component link and one is Embeddable.

Given this modelling part, relevant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model.
It works without Link (schema/model). Why? I was suprised ;-)

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with xml name "internalLink" (like inside website above)?

added 39 characters in body
Source Link

Given this modelling part, relavant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model. 
It works, without Link (schema/model). Why? I was suprised. ;-)
Other XML name then "internalLink" didn't work.

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with XML name "internalLink" (like inside website above)?

Q4- Can use the Xml Name for both?

Datamodel contains two exact same schema's "ListItemLijst".
One for component link and one is Embeddable.

Given this modelling part, relavant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model. It works, I was suprised.
Other XML name then "internalLink" didn't work.

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with XML name "internalLink" (like inside website above)?

Q4- Can use the Xml Name for both?

Datamodel contains two exact same schema's "ListItemLijst".
One for component link and one is Embeddable.

Given this modelling part, relavant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model. 
It works without Link (schema/model). Why? I was suprised ;-)
Other XML name then "internalLink" didn't work.

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with XML name "internalLink" (like inside website above)?

Q4- Can use the Xml Name for both?

Datamodel contains two exact same schema's "ListItemLijst".
One for component link and one is Embeddable.

Source Link

How to get component link for internal/external/multimedia working

Given this modelling part, relavant for the linking.

enter image description here

Component linking should be implement for linking to:

1. Inside website

Linking to e.g. article, article-top-tasks.
Created field with XML name "internalLink" for schema and model. It works, I was suprised.
Other XML name then "internalLink" didn't work.

2.Outsite website

Created schema "ExterneLink" (for reuse), it contains 1 field for Url.
To get this to work, schema and model defined, can us it value in class/view.
Advantage: Works. It's also normal for embedded of component linking.
Disadvantage: Extra field.

Example for 1: Inside website 'Tegel' (Tile)

enter image description here

Example for 2 extended for Outside website

enter image description here

Questions:

Q1- Can you custom (extend/change) Link schema e.g. icon or drop altText?

Core example application use "Link" schema.
Sdl.Web.Common.Model.Link has model in Dxa Framework.
I made a Link model myself, when tested the Url is NOT resolved. Why?

Q2- Created schema/model "List item" instead of "Link".

Advantage and disadvantage?

Q3- Multimedia schema "Document" for upload/link "Pdf files".

Will it work with XML name "internalLink" (like inside website above)?

Q4- Can use the Xml Name for both?

Datamodel contains two exact same schema's "ListItemLijst".
One for component link and one is Embeddable.