feat: finalize Mintlify migration — redirects, analytics, SEO, meta descriptions#1129
Merged
Conversation
…escriptions Bring the Mintlify docs to parity with GitBook ahead of production cutover. docs.json: - Add 414 redirects (42 -> 456) so every legacy GitBook URL resolves with no 404s. Covers API resource index pages, guide relocations, and brand-guide path moves. All destinations validated against real mdx/OpenAPI routes. - Add analytics integrations (GA4 + PostHog, US-cloud host) from the `docs` Doppler project. - Add site-wide seo block: canonical metatags matched to the marketing site (og:site_name Seam, twitter:site @helloseam, summary_large_image), absolute og:image, and indexing: navigable. Content: - Add unique meta descriptions to 119 pages (74 hand-written guides + 45 API object/static reference pages); fix 2 factually-wrong descriptions. - Add docs-specific Open Graph image (images/seam-og-default.jpg, 1200x630). Tracked in Linear: DOC-193..DOC-197 (Mintlify Docs Migration). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Ten agent-written descriptions used single-quoted YAML containing a literal apostrophe (e.g. 'Seam's SDK'), which is invalid YAML and broke Mintlify's MDX frontmatter parser. Switched those to double-quoted strings. Verified: npm run validate:mintlify passes (exit 0); all 119 changed mdx frontmatter parse cleanly with a YAML parser. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Brings the Mintlify docs to parity with GitBook ahead of the production cutover. Part of the Mintlify Docs Migration Linear project (DOC-193 → DOC-197).
What's in here
docs.jsonconfigx-mint.hrefroutes, and existing redirects (no dup sources, no shadowing of real pages).integrationsblock for GA4 + PostHog (US-cloudapiHost), values pulled from thedocsDoppler project (PUBLIC_GA4_ID,PUBLIC_POSTHOG_KEY).seoblock — canonical metatags matched to the marketing site (og:site_name: Seam,twitter:site: @helloseam,summary_large_image), absoluteog:image,indexing: navigable.Content
images/seam-og-default.jpg, 1200×630).Verification done
docs.jsonis valid JSON; redirect set independently re-validated (all destinations resolve).Not covered here (pre-promotion gates)
docs.seam.co, dropping/latest) — operational, outside this repo.🤖 Generated with Claude Code