Skip to content

docs(connectors): add the metaLinks self alternate to nmi and razorpay - #286

Merged
nfarah86 merged 1 commit into
mainfrom
docs/metalinks-nmi-razorpay-20260918
Sep 18, 2026
Merged

nfarah86 merged 1 commit into
mainfrom
docs/metalinks-nmi-razorpay-20260918

Conversation

@nfarah86

Copy link
Copy Markdown
Collaborator

Adds the metaLinks.alternates self entry to the last two connector pages that were missing it.

Why

Every page under integration-space/connectors-integrations/available-connectors/ carries a self-referential metaLinks.alternates entry. It is authored at page creation, not written later by a sync — amazonpay.md was created with one in #282.

Two checks support that reading:

  • All 40 existing entries are self-referential. None points at a different, prior path, which is not how a move-redirect record would look.
  • The field is present in the commit that creates each page.

nmi.md and razorpay.md predate the current connector backfill batch and were the only two pages in the directory without it.

Scope

Front matter only. No page body, navigation, or generated block is touched.

Page Change
nmi.md metaLinks.alternates: [nmi.md]
razorpay.md metaLinks.alternates: [razorpay.md]

The same gap in the open batch PRs is fixed separately: #283 (barclaycard), #284 (bitpay), #285 (blackhawknetwork).

🤖 Generated with Claude Code

Every page under available-connectors carries a self-referential
metaLinks.alternates entry, authored at page creation rather than
written later by a sync: amazonpay.md was created with one in #282. All
40 existing entries are self-referential and none points at a different
prior path.

nmi.md and razorpay.md were the last two pages in the directory without
one. bitpay, barclaycard and blackhawknetwork are fixed in #284, #283
and #285.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@nfarah86
nfarah86 merged commit d7cb8ca into main Sep 18, 2026
6 checks passed
@nfarah86
nfarah86 deleted the docs/metalinks-nmi-razorpay-20260918 branch September 18, 2026 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant