Document the technical evaluation process - #6817
Open
devin-ai-integration[bot] wants to merge 5 commits into
Open
Document the technical evaluation process#6817devin-ai-integration[bot] wants to merge 5 commits into
devin-ai-integration[bot] wants to merge 5 commits into
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.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
|
🌿 Preview your docs: https://fern-preview-devin-1788367703-technical-evaluation.docs.buildwithfern.com/learn Here are the markdown pages you've updated: |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| Fern and your team build a shared requirements document, with each requirement prioritized as a must-have, should-have, or could-have. | ||
|
|
||
| Alongside the requirements, agree on two or three success criteria tied to an outcome you care about, like reader activation, support ticket deflection, or engineering time saved on docs maintenance. That gives the evaluation a clear bar to clear rather than just a feature list. |
Contributor
There was a problem hiding this comment.
📝 [vale] <FernStyles.Hedges> reported by reviewdog 🐶
Avoid hedge words and filler like 'just'. Prefer direct statements.
devalog
approved these changes
Sep 2, 2026
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.
Summary
Adds a hidden
Technical evaluationpage under Docs > Getting started, describing how a prospect works with the Fern team during a 1-3 week tech eval: demo site, hands-on access for the whole team, the prioritized requirements sheet and review call, per-team stakeholder sessions (engineering, marketing, support, tech writing), and the legal/security/procurement approvals.Content comes from the sales process description in Slack rather than from Mintlify's POC onboarding page — the framing is "how to work with the Fern team", not a self-serve checklist. The stakeholder-session table links each topic to the relevant existing docs (spec syncing, API Explorer, SDK snippets, API key injection, SEO/GEO, Ask Fern, Fern Agent, user feedback, analytics), and the hands-on section links out to Fern Editor and the Docs quickstart.
Hidden like
Self-service setup, so it's shareable by URL but absent from the sidebar. No changelog entry: this is a process page, not a Docs product feature.Link to Devin session: https://app.devin.ai/sessions/6077699499e34d8080084c393a08cbe3
Open in Devin Desktop: https://app.devin.ai/desktop/session/6077699499e34d8080084c393a08cbe3?variant=devin