Migrating from Mintlify in a day
Export your existing Mintlify pages, import them into Quill, review the drift report, cut over without breaking inbound links. End-to-end. From "click export" to "redirect old domain."
Long-form, project-shaped guides. Pick a goal — migrating, setting up SSO, embedding the docs site in your product — and follow it end-to-end. Each guide is a complete journey, not a fragment.
Export your existing Mintlify pages, import them into Quill, review the drift report, cut over without breaking inbound links. End-to-end. From "click export" to "redirect old domain."
The Okta side. The Quill side. The first-login UX. The just-in-time provisioning posture. The "what to do when someone gets locked out" runbook. All in one place, with screenshots.
When you want help-center articles to live under app.your-product.com/help rather than a separate domain. Reverse proxy, subpath routing, the SEO posture, the auth carry-over.
The opinionated path for your first seven days. Day 1 import, day 2 review, day 3 brand pass, day 4 connect CI, day 5 cut over. We've watched this play out enough times to know what breaks.
Logo, palette, typography, OG cards, favicons. What's configurable in the portal, what needs a CSS override, what we'll do for you under enterprise. The whole surface, in one walkthrough.
GitHub Actions example. GitLab CI example. Drone, Buildkite, Jenkins. The auth posture for CI tokens. The "we deploy docs on green tests" pattern. Real .yml files you can copy.
Reference docs answer "what does this do?" Guides answer "how do I get from where I am to where I want to be?" Both matter. They're different shapes.