🔗 `mdx` linking best practices

[JFWooten4]

Doing this (bad) v. this.

[JFWooten4]

Doing [this] (bad) v. [this](https://good.com).

[this]: https://stellar.org/protocol/sep-10

[JFWooten4]

As a bonus:

⌨️ Update minor SEP-10 syntax
This should probably be refactored to have seperate custial and
non-custodial sections / code examples.

and

Order pages with existing translations:

• https://developers.stellar.org/docs/tokens/quickstart

[JFWooten4]

Safer long-term options (so this doesn’t bite you again)

Prefer absolute doc URLs with the /docs prefix in Markdown:

Operations & Transactions

Relative paths are easy to break after file moves.

Or use Docusaurus’s doc link syntax (resilient to moves/renames if you keep the id/slug stable):

See {@link doc:/learn/fundamentals/transactions/operations-and-transactions}.

(Alternatively, use from @docusaurus/Link.)

Add client redirects to cover old “/learn/…” links that snuck in. In docusaurus.config.js:

plugins: [
  [
    '@docusaurus/plugin-client-redirects',
    {
      createRedirects(existingPath) {
        // If a page lives at /docs/learn/..., also accept /learn/...
        if (existingPath.startsWith('/docs/learn/')) {
          return [existingPath.replace('/docs', '')];
        }
        return [];
      },
    },
  ],
];

This lets old /learn/... links keep working even if someone forgets the /docs prefix.

[JFWooten4]

OpenAPI page edits can migrate in type-specific READMEs and includes the best practice of full hard links at stellar#2386 (comment). Then run yarn api