-
Notifications
You must be signed in to change notification settings - Fork 1
docs: route support questions to the Intercom chat instead of email #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| /** | ||
| * "Chat with us" launcher for the Eden AI docs (Mintlify). | ||
| * | ||
| * How it works: | ||
| * Mintlify boots the Intercom messenger itself from `integrations.intercom` | ||
| * in docs.json, which means it owns `window.intercomSettings` — so Intercom's | ||
| * usual `custom_launcher_selector` option is not available to us. Instead we | ||
| * delegate clicks: any link ending in #chat opens the messenger through the | ||
| * global `Intercom()` API. Same pattern as the #manage-cookies link handled in | ||
| * cookie-consent.js. | ||
| * | ||
| * Used by the "Chat with us" navbar link (docs.json) and the Live Chat section | ||
| * of v3/general/support.mdx. | ||
| * | ||
| * Intercom is not consent-gated (see cookie-consent.js), so the messenger is | ||
| * available on first load. It can still be missing when a privacy extension | ||
| * blocks the widget or the snippet is mid-boot, so we poll briefly and then | ||
| * give up quietly rather than leaving a dead click that throws. | ||
| */ | ||
| (function () { | ||
| var SELECTOR = 'a[href$="#chat"]'; | ||
| var BOOT_TIMEOUT_MS = 5000; | ||
| var POLL_INTERVAL_MS = 150; | ||
|
|
||
| // Mintlify is a SPA; guard against re-registering the listener on | ||
| // client-side navigation. | ||
| if (window.__edenaiChatLauncherLoaded) return; | ||
| window.__edenaiChatLauncherLoaded = true; | ||
|
|
||
| function show() { | ||
| if (typeof window.Intercom !== "function") return false; | ||
| window.Intercom("show"); | ||
| return true; | ||
| } | ||
|
|
||
| // The click can land before Mintlify's Intercom snippet has finished booting, | ||
| // so retry until it does or the deadline passes. | ||
| function showWhenReady(deadline) { | ||
| if (show()) return; | ||
| if (Date.now() > deadline) return; | ||
| setTimeout(function () { | ||
| showWhenReady(deadline); | ||
| }, POLL_INTERVAL_MS); | ||
| } | ||
|
|
||
| // Capture phase so this wins over Mintlify's own anchor handling, which would | ||
| // otherwise treat #chat as an on-page heading link. | ||
| document.addEventListener( | ||
| "click", | ||
| function (e) { | ||
| var trigger = e.target.closest && e.target.closest(SELECTOR); | ||
| if (!trigger) return; | ||
| e.preventDefault(); | ||
| e.stopPropagation(); | ||
| showWhenReady(Date.now() + BOOT_TIMEOUT_MS); | ||
| }, | ||
| true | ||
| ); | ||
| })(); | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: edenai/docs
Length of output: 149
🏁 Script executed:
Repository: edenai/docs
Length of output: 4461
Register
intercom-chat.jsin the Mintlify script config.The
#chatlinks indocs.jsonandv3/general/support.mdxdepend on this file running, but there is no tracked Mintlify reference tointercom-chat.js. Add it as a loaded script; otherwise those links can silently prevent navigation without opening Intercom.🤖 Prompt for AI Agents