Draft improvements from assistant conversations: explain notification tabs#282
Open
mintlify[bot] wants to merge 2 commits into
Open
Draft improvements from assistant conversations: explain notification tabs#282mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Document what each Notifications Panel tab (
forYou,people,documents,all) actually shows, so readers no longer have to ask what thetabConfigfields mean.Changes
async-collaboration/notifications/customize-behavior.mdx: added a per-tab content table to thesetTabConfigsection, and corrected the "three tabs" default note to enumerate the tabs that are enabled by default.async-collaboration/notifications/overview.mdx: added a new "Tabs" section describing each of the four tabs and linking tosetTabConfig.Context
The recurring assistant question across several buckets was "what do
forYou,people, anddocumentsmean intabConfig?" The existing docs described the API surface and the default fetch counts, but never stated what content differentiated each tab. Field definitions were verified againstNotificationTabConfiginapi-reference/sdk/models/data-models.mdxand the primitives / wireframe variables pages.