DF-823: Mintlify plan and entitlement findings - #205
Conversation
Answers the M1 spike on public evidence; one dashboard check is left for a human. Mintlify's `languages` config is not documented as tier-gated, and `ko` is a supported locale. But Mintlify separately sells native AI translations on Pro/Enterprise that bulk-translate the docs and open a PR per change with a human merge gate — which is M2's bulk run plus all of M3. Every observable signal says Mixpanel is on Enterprise, decisively the README putting the Mintlify web editor behind Okta. That reframes M2 and M3: before building a translation pipeline, someone should open the dashboard and check whether we already own one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Confidence Score: 4/5The PR appears safe to merge after fixing or removing the broken references to uncommitted supporting artifacts. The analysis is otherwise self-contained and explicitly preserves the remaining human entitlement check, but readers currently cannot access several documents and tools it cites as existing. Files Needing Attention: i18n/01-plan-and-entitlements.md
|
| Filename | Overview |
|---|---|
| i18n/01-plan-and-entitlements.md | Adds the entitlement investigation, but several references point to supporting files not present at the PR head. |
Reviews (1): Last reviewed commit: "DF-823: Mintlify plan and entitlement fi..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - *"Do not use the same page path in more than one language. Duplicating paths across languages results in | ||
| undefined behavior."* — this is why DF-825's "seed `ko/` with English fallback" step should be dropped; | ||
| see [`02-scope-and-preservation-spec.md`](02-scope-and-preservation-spec.md#on-df-825-do-not-seed-english-fallbacks). |
There was a problem hiding this comment.
This document links to 02-scope-and-preservation-spec.md, 03-tooling-evaluation.md, and scripts/validate-mdx-parity.mjs, but none is present at the PR head. Readers therefore cannot access the specifications, comparison, or validator cited to support these decisions.
1 participant
Documents in
i18n/cross-reference each other, so relative links to files added later in the stackresolve once the stack has landed. The final state is link-checked; every relative link resolves.
Operational sequencing — none of this happens on merge
Merging this stack changes nothing a reader sees.
docs.jsonis untouched, no workflow is installed, andno
ko/tree exists at the repo root. Turning Korean on is a separate, deliberate sequence:docs.jsonlanguagesarray;cp i18n/nav/ko.json ./ko.jsondocs/+guides/intoko/gt.config.jsonto root,translate.ymlto.github/workflows/, setGT_API_KEY+GT_PROJECT_ID/koSteps 3 and 6 are the only ones that change live behaviour. Both are reversible by reverting one file.
Answers the M1 spike on public evidence. One dashboard check is left for a human.
Adds one file:
i18n/01-plan-and-entitlements.mdWhat it found
Mintlify's
languagesconfig is not documented as tier-gated, andkois a supported locale — so areja/ja-JP,id,es,de,fr,pt-BR,zh-Hans/zh-Hant, covering the whole M4 shortlist.But Mintlify separately sells native AI translations on Pro/Enterprise that bulk-translate the docs and open a PR per change with a human merge gate — which is M2's bulk run plus all of M3.
Every observable signal says Mixpanel is on Enterprise: custom domain,
style.css, custom JS injection, self-hosted Garnett fonts, 881 redirects — and decisively,README.mdputs the Mintlify web editor behind Okta, which is SSO, which is Enterprise tier.The one check I could not do
Open the Mintlify dashboard → Settings → Translations. If the page exists and lets you add a locale, this closes.
While there, please capture whether the feature exposes any glossary or do-not-translate control. That single answer decides how much pipeline we build — and it is the input to the engine decision in the DF-827 PR later in this stack.