-
Notifications
You must be signed in to change notification settings - Fork 3
Document instance audiences feature #1471
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
Merged
Merged
Conversation
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
Add comprehensive documentation for the new instance audiences feature that allows filtering versions and products by audience to control what gets generated in each docs instance. - Created new page at fern/products/docs/pages/navigation/instance-audiences.mdx - Added page to Configuration section in docs.yml navigation - Includes examples for configuring audiences on instances, versions, and products - Explains filtering logic and how to publish to specific instances - Shows how instance audiences work alongside API reference audiences Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
Contributor
Author
🤖 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:
|
Contributor
- Replace audience(s) with audiences for clarity - Change 'does not' to 'doesn't' per Microsoft.Contractions - Capitalize 'API Reference' per FernStyles.Reject - Replace 'Latest/latest' version names with v3/v2 to avoid time-relative terms Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
Contributor
Contributor
Contributor
Contributor
devalog
approved these changes
Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Document instance audiences feature
Summary
Added comprehensive documentation for the new instance audiences feature that allows filtering versions and products by audience to control what gets generated in each docs instance. This enables users to create separate documentation sites for different audiences (e.g., public customers, internal developers, beta testers).
Changes:
fern/products/docs/pages/navigation/instance-audiences.mdxdocs.ymlnavigation (placed after Products)Review & Testing Checklist for Human
Recommended Test Plan
docs.ymlwith two instances (one public, one internal) with different audiencesfern docs devand verify the correct content appears based on the filtering logic--instanceflagNotes
fern docs dev(no syntax errors)Session info: