Use Ravion-branded OG banners for every docs page - #26
Merged
Conversation
Co-Authored-By: brandon <brandon@flightcontrol.dev>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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:
|
Co-Authored-By: brandon <brandon@flightcontrol.dev>
Co-Authored-By: brandon <brandon@flightcontrol.dev>
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.
Summary
Docs links currently unfurl with Mintlify's auto-generated preview. Every page now points its social-share tags at the Ravion OG renderer instead, so docs share the same banner as the marketing site and the blog (orange grid, frame brackets,
PP Fragmenttitle):Only the page path goes into the frontmatter — the renderer (flightcontrolhq/flightcontrol#6795) reads the title from the page's own Mintlify Markdown export, so titles never get duplicated or drift.
scripts/sync-og-images.mjswrites those two tags for every.mdxoutsidesnippets/(the 107 committed pages here are its output). Generated pages don't carry the tags, so the module-catalog workflow now runspnpm sync:og-imagesafter generation — as do the two sync workflows in the monorepo — and--checkmode runs on pull requests to catch a page that was added or regenerated without them.Verified with
mint validate(build validation passed) and by rendering/og/docs/index.pngand/og/docs/config-as-code/ci-integration.pngagainst a local web server.Link to Devin session: https://app.devin.ai/sessions/5a2da15aec4240a8b446ef95f66e3fbd
Requested by: @flybayer