Under Community Review
  • What are example use cases where direct Page Links are better than Component Links?
  • If we provide Page Linking functionality, where would you put the Page Links?  In Page metadata? Or also in Component content/metadata?  Components are often defined higher up in the BluePrint than Pages, so it may not be possible to link from Components to Pages (?)
  • Should it be possible to constrain the type of Pages you can link to (by Page Template or Page Schema)?
  • Should it be possible to embed Page Links in a Rich Text field?
  • Should it be possible to unpublish a Page if another published Page links to it?

Page Linking

Tridion should allow linking to Pages directly rather than through Component Links.

In order to simulate Page Linking functionality, we have created a "shadow navigation" structure using Navigation Shadow Components (which reflect Pages), so we can use Component Links to link to Pages. This solution is customization heavy and hard to maintain.
 

Chris Chrcek
Parents

  • Sorry for the delay in getting back to you Rick. I didn't get a notification of your comment for some reason and have only just come back here after reading your blog post about Page Linking.

    Both the Pages and the Components were in the same Publication(s) for the solution that we built (I know - It was a legacy application that we picked up and was already like this!), so fortunately, we didn't have to worry about this.

    I guess that there are a few ways to handle this though, including:

    1. A user can select only one page to link to in one of the child publications (not ideal - unless this Page was inherited by the majority of the sites)

    2. A user can select multiple pages to link to, depending on the website publication

    I don't envy you guys the UX and UI design on that one! :)

Comment

  • Sorry for the delay in getting back to you Rick. I didn't get a notification of your comment for some reason and have only just come back here after reading your blog post about Page Linking.

    Both the Pages and the Components were in the same Publication(s) for the solution that we built (I know - It was a legacy application that we picked up and was already like this!), so fortunately, we didn't have to worry about this.

    I guess that there are a few ways to handle this though, including:

    1. A user can select only one page to link to in one of the child publications (not ideal - unless this Page was inherited by the majority of the sites)

    2. A user can select multiple pages to link to, depending on the website publication

    I don't envy you guys the UX and UI design on that one! :)

Children
No Data