docs: README screenshot that shows vector sparklines#57
Merged
gordonmurray merged 1 commit intoJun 10, 2026
Merged
Conversation
The old screenshot showed a table of plain integer and text columns, which undersells the main feature. The new one is the v0.3.0 image browsing a dataset with a 512-dim embedding column: CLIP badges and sparklines on every row, and the vector field highlighted in the schema panel.
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
The README screenshot showed a table of plain integer and text columns, which undersells the distinctive feature. Replaced it with a screenshot of the released v0.3.0 image browsing a dataset with a 512-dim embedding column: CLIP badges and per-row sparklines in the table, and the vector field highlighted in the schema panel. The header in the shot shows v0.3.0 with LanceDB 0.33.0.
Same filename, so no README text change; rendered at 2x for sharpness (411 KB vs 284 KB before).
Test plan