Add business-framed Use Cases docs section#356
Merged
Conversation
Adds a new "Use Cases" section that lays out the common things teams build with Schematic, framed by business outcome (PLG / SLG / Customer Management / Ops) rather than by primitive. Each page follows a need -> common approaches -> how Schematic fits in -> learn more skeleton and links into the existing technical docs and playbooks. - New index plus 11 use-case pages under fern/docs/pages/use-cases/ - Nav: insert Use Cases after "Using Schematic"; move Playbooks up to follow it Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Each use-case page now develops the common do-it-yourself approach and where it breaks down, rather than a single compressed paragraph. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Rounds out the two lean buckets: - SLG: Run sales-assisted trials and POCs; Expand accounts with upsells and add-ons - Customer Management: Spot churn and expansion with usage signals; Stay ahead of renewals and expirations Wires the four pages into the nav and the Use Cases index. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
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.
What
Adds a new Use Cases docs section: a business-outcome-framed layer that lays out the common things teams build with Schematic and links into the existing technical docs and playbooks. Layout inspired by Nango's use-case pages.
Structure
Index (
use-cases/overview.mdx) + 11 pages grouped into four categories:Each page uses a consistent skeleton: the need (unheadered intro) → Common approaches → How Schematic fits in → Learn more. Pages are deliberately light and link out; deeper technical guides are a later pass.
Nav
fern/docs.yml: new Use Cases section inserted after "Using Schematic", and Playbooks moved up to follow it. Playbooks content is unchanged; Use Cases link into it.Validation
fern check: 0 errors. The pre-existing 50 warnings don't reference the new pages.Notes for review
🤖 Generated with Claude Code