docs: reposition product positioning statement to after benchmark chart - #85
Merged
EricNGOntos merged 2 commits intoMay 15, 2026
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
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.
Closes #84
What Changed
Moves the bold positioning statement 'We're not developing the next MinerU — we're building document memory infrastructure that agents can effectively consume.' from the very top of the 'What We Are' section to immediately after the benchmark performance chart, as a blockquote before 'Key Advantages'.
Rationale
At the top of the page, the statement reads as a defensive opener before the reader has any context or evidence. After the benchmark chart — where the reader has just seen concrete performance data against raw parsing baselines — the same statement becomes a natural, confident interpretation of what those numbers mean: Knowhere is not competing on raw parsing fidelity, it is providing a higher-level memory infrastructure layer that agents can navigate and cite.
The flow now reads:
Changes
>blockquote between the benchmark chart and 'Key Advantages'