-
Notifications
You must be signed in to change notification settings - Fork 4
Fix broken anchor links in documentation #2936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
| | `fern generate` | Build & publish SDK updates | | ||
| | `fern write-definition` | Convert OpenAPI specifications to [Fern Definition](/learn/api-definition/fern/overview) | | ||
| | `fern write-overrides` | Create OpenAPI customizations | | ||
| | `fern generator upgrade` | Update SDK generators to latest versions | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[FernStyles.Current] Avoid time-relative terms like 'latest' that become outdated
| <Step title="Customize your docs"> | ||
| Now that you have a basic docs site, you can customize it by adding tutorials, generating an API Reference, or finetuning the branding. (Or skip ahead to [preview](#preview-your-docs) and [publish](#publish-to-production).) | ||
| Now that you have a basic docs site, you can customize it by adding tutorials, generating an API Reference, or finetuning the branding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[FernStyles.Current] Avoid time-relative terms like 'Now' that become outdated
| <Note> | ||
| Section-level changelogs **cannot** be nested within an `api` entry. See [API-level changelogs](#api-level-changelog) to add an API-level entry. | ||
| Section-level changelogs **cannot** be nested within an `api` entry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'can't' instead of 'cannot'.
Summary
Fixes broken anchor links across 7 documentation files. These links pointed to headings that don't exist, typically because they referenced Step component titles (which don't generate anchor IDs) or used incorrect numbered suffixes for duplicate headings.
Changes by file:
#oauth-authentication→#auth-scheme-reference#add-namespaces-optional#preview-your-docsand#publish-to-production#api-level-changelog#metadata-2→#metadata-1,#reviewers-4→#reviewers-1,#reviewers-1→#reviewers)#developer-packslinks with external Microsoft download links; removed broken#legacy-projectsreferencesUpdates since last revision
Restored the valid anchor links in commands.mdx that were incorrectly removed. After DOM inspection, I confirmed that Accordion components in this docs platform DO generate anchor IDs from their titles (e.g.,
<Accordion title="fern init">generatesid="fern-init"). The original removal was based on a false assumption.Review & Testing Checklist for Human
fern init,fern generate --docs) and confirm they scroll to the corresponding Accordion section#metadata-1,#reviewers-1) depend on heading orderRecommended test plan: Open the preview deployment and navigate to the commands page first to verify the table links work. Then check generators-yml-reference.mdx for the metadata/reviewers links. Finally, spot-check pages where links were removed to ensure readability.
Notes