docs: remove beta banner and legacy SDK tab#78
Open
docs: remove beta banner and legacy SDK tab#78
Conversation
Clean up global docs navigation by removing the temporary beta status messaging and taking the SDK (Legacy) tab out of the top-level tabs for now. - removed `banner` block from `docs.json` to eliminate the “Beta Docs” notice - removed the entire `SDK (Legacy)` tab from `navigation.tabs` - kept underlying SDK files in the repository untouched (only navigation changed) - validated `docs.json` structure remains valid
This was referenced Mar 3, 2026
Open
Open
This was referenced Mar 3, 2026
Open
aimensahnoun
changed the title
banner block from `docs.js
This was referenced Mar 3, 2026
aimensahnoun
changed the title
aimensahnoun
changed the title
Member
Author
Greptile SummaryThis PR removes the beta warning banner and the "SDK (Legacy)" navigation tab from Key changes:
Issues found:
Confidence Score: 3/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
subgraph Before["Before (navigation tabs)"]
T1[Use Cases]
T2[API]
T3[Resources]
T4["SDK (Legacy)"]
T4 --> P1["sdk-legacy/overview"]
end
subgraph After["After (navigation tabs)"]
T5[Use Cases]
T6[API]
T7[Resources]
end
subgraph Orphaned["Still in repo / still linked"]
F1["sdk-legacy/overview.mdx"]
L1["glossary.mdx (3 links)"]
L2["use-cases/welcome.mdx (1 link)"]
L3["resources/lifecycle-of-a-request.mdx (1 link)"]
L1 -->|"/sdk-legacy/overview"| F1
L2 -->|"/sdk-legacy/overview"| F1
L3 -->|"/sdk-legacy/overview"| F1
end
style T4 fill:#ff6b6b,color:#fff
style F1 fill:#ffa94d,color:#fff
style Orphaned fill:#fff3bf,color:#000
Last reviewed commit: 6d58668 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| @@ -166,17 +162,6 @@ | |||
| ] | |||
There was a problem hiding this comment.
Orphaned page with live internal links
The sdk-legacy/overview.mdx file is still present in the repository, and three other documentation files contain internal links pointing to /sdk-legacy/overview:
glossary.mdx(3 links) – references to "SDK (Legacy)" for payment reference, swap-to-pay, and swap-to-conversion definitionsuse-cases/welcome.mdx– a cardhrefpointing to/sdk-legacy/overviewresources/lifecycle-of-a-request.mdx– a prose link to "SDK (Legacy)"
In Mintlify, pages that are not referenced in the docs.json navigation are typically not built or served. This means removing the tab without also removing these inbound links is likely to produce broken links (404s) for readers who click them.
To fix this, either:
- Remove or update the five inbound links in
glossary.mdx,use-cases/welcome.mdx, andresources/lifecycle-of-a-request.mdxto point elsewhere (e.g., the legacy docs sitehttps://docs.request.network), and deletesdk-legacy/overview.mdx. - Or, if the page should remain accessible, keep it in the navigation (perhaps under the Resources tab) rather than removing the tab entry entirely.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Removed the beta warning banner and legacy SDK documentation section from the docs configuration.
What changed?
How to test?
Why make this change?
The documentation has likely moved out of beta status, making the warning banner obsolete. The legacy SDK documentation removal suggests a transition to newer SDK versions, streamlining the documentation structure by removing outdated content.