Links on TNC Properties

When you are linking to an internal page or asset (a page or asset on AEM from AEM), you should always use the relative URL - also known as the file path or page path (for a web page). The relative URL points to the location of the page in AEM - and not the full external page address.

Dynamic URLs

When you are linking to a page using a relative URL, if the address or location of the target page changes, the link will still work. In contrast, if you use the full URL you are using a static URL and the link will not work if that URL changes.

Tied to Notifications - Avoid the 404!

Also, if you are linking to an expiring page or asset using the relative URL you will be notified that the link is expiring. If you link with a full URL, an expiration will not trigger a notification and you will end up with a broken link.

In components and page properties, always use the relative URL (or file path) to pages and assets. These URLs always start with /content/.

Relative URL Examples:

• Photo: /content/dam/tnc/nature/en/photos/tnc_55342987_1640x1230.jpg  (don't forget to include the file extension!)
• Page: /content/tnc/nature/us/en-us/about-us/where-we-work/canada  (make sure you don't include .htm or .html on the end of a page path!)

Use the full, published URL when linking from outside AEM - such as in an email or on social. Full, published URL examples:

• Page: https://www.nature.org/en-us/about-us/where-we-work/canada/
• Document: https://www.nature.org/content/dam/tnc/nature/en/documents/Caribbean-Impact-Report-Climate-Action-2017.pdf

And remember to NEVER link to author.tnc.org. 

The general rule to follow is that all internal links (links on TNC properties) should open in the same tab that the user is currently viewing. All external links (links to non-TNC properties) should open in a new tab. 

The following screenshot and list illustrate how to follow this guideline.