Repository navigation
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
- Use the canonical www.lancedb.com Organization @id and url so the docs publisher entity matches the marketing site's JSON-LD. - Make the FAQ generator fail instead of silently dropping content: reject text under non-question headings (including subheadings inside answers), headings with a non-terminal "?", tables, blockquotes, and reference links; ignore trailing heading whitespace; name the page and question in errors; process only the pages listed in FAQ_PAGES. - Share one strip_markdown helper between the FAQ and dataset generators. - Emit Dataset JSON-LD on all dataset pages, not only DocVQA. - Test Dataset schema output and install pyyaml in CI for it. - Restore the Ollama page title to match sibling integration pages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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.
Ahrefs flags the docs homepage for missing Organization profile links and all three FAQ pages for missing FAQPage markup. This adds LanceDB's official GitHub, LinkedIn, and X profiles through Mintlify's native
seo.organizationconfiguration, and adds server-rendered FAQPage JSON-LD covering all 24 visible question/answer pairs.The FAQ landing page now presents its existing navigation and support information as visible questions and answers. A generator reads the FAQ prose, and CI checks that the generated markup stays in sync. The markup uses literal script content so Mintlify includes it in the initial HTML without client-side expression evaluation.
The Product report lists
/datasets/docvqaand/integrations/embedding/ollama. These are a dataset card and an integration guide, so Product offers/prices would misrepresent their content. DocVQA now has Dataset metadata (also emitted by the dataset sync generator), and Ollama's title, description, and introduction identify it as an integration guide. These two Product classifications may still need exclusion in Ahrefs after recrawling; this PR does not claim to clear those false positives.Validation:
noindex, nofollow, so Mintlify intentionally omits page-level Article/Organization markup there; the homepage Organization output still needs confirmation after production deployment.mint validatereports the same eight missing snippet exports on the unmodified freeze branch and this branch: sixPyVectorIndex*exports inindexing/vector-index.mdx,TsAddProgressintables/create.mdx, andRsUpdateMakeUsersReaderintables/update.mdx. No generated code snippets were changed.Based on
deploy-freezeat5d5aaad. Live Ahrefs results require deployment and a new crawl.Audit reports: Organization, FAQPage, Product.