Updating links in Quickstarts to open in new tab

[mchang16-auth]

Changes

• Changed all links in markdown files contained within /articles/quickstart to <a href="link" target="_blank" rel="noreferrer">. This will make it open in a new tab.
• Added the same anchor tag logic to 4 files located in /articles/_includes. These files are commonly used in Quickstarts (api_auth_intro.md, _callback_url.md, etc).

Changes were made using this script, and manually tested in local environment to check that the links were working properly. Images in the markdown format of ![text](image) were not altered.

const fs = require('node:fs');
const path = require('path');
const { opendir } = require('node:fs/promises');

const changeLinks = async () => {
  const dir = await opendir('./articles/quickstart', { recursive: true });
  for await (const dirent of dir) {
    if (dirent.isFile() && path.extname(dirent.path) === ".md") {
      console.log(dirent.path);
      fs.readFile(dirent.path, 'utf8', (err, data) => {
        if (err) {
          console.error("READ:", err);
          return;
        }

        let newContent = data.replaceAll(/(\[.*?\])(\(.*?\))/g, (match, p1, p2) => {
          const text = p1.replace(/[\[\]']+/g, "");
          const url = p2.replace(/[{()}]/g, "");
          return `<a href="${url}" target="_blank">${text}</a>`
        })

        fs.writeFile(dirent.path, newContent, err => {
          if (err)
            console.error("WRITE:", err);
        });
      });
    }
  }
}

changeLinks();

[BcnCarlos]

Looks good to me.

[frederikprijck]

Did we consider adding rel="noreferrer"?

See: https://developer.chrome.com/docs/lighthouse/best-practices/external-anchors-use-rel-noopener

When you link to a page on another site using the target="_blank" attribute, you can expose your site to performance and security issues:

I see we are adding target="_blank" that target another site.

The page I linked also explains the solution:

Adding rel="noopener" or rel="noreferrer" to your target="_blank" links avoids these issues.

It also mentions this is mostly for legacy browsers, as modern browser solve this internally already. So I would still recommend considering it.

[BcnCarlos]

Reviewed and approved

[BcnCarlos]

Updates approved