Mintlify import#1727
Merged
Merged
Conversation
…d to ko/models/core/registry/model_registry/model-lineage.mdx
…models/core/automations/automation-events.mdx
… to ko/models/core/automations/create-automations/slack.mdx
…md to models/automations/create-automations/webhook.mdx
…/reports/reports-gallery.mdx
…ko/models/reports/clone-and-export-reports.mdx
…eports/edit-a-report.mdx
…eports/embed-reports.mdx
…/models/reports/collaborate-on-reports.mdx
…models/reports/cross-project-reports.mdx
…/reports/create-a-report.mdx
…raining/serverless-rl.mdx
…o training/serverless-rl/available-models.mdx
… to training/serverless-rl/use-trained-models.mdx
…aining/serverless-rl/usage-limits.mdx
…ls/tables/visualize-tables.mdx
…s/tables/tables-download.mdx
…dels/tables/tables-walkthrough.mdx
…log/log-tables.mdx
…/tables/tables-gallery.mdx
…ack/project-page.mdx
…els/track/environment-variables.mdx
…odels/track/create-an-experiment.mdx
…s/track/public-api-guide.mdx
## Summary This PR adds the necessary redirects configuration for Mintlify to the docs.json file. ## Changes - Added `redirects` array to docs.json with comprehensive redirect rules - Includes redirects for: - Models documentation paths - Guides and tutorials - Platform and app paths - Japanese and Korean localized content - Launch documentation - Weave documentation paths ## Purpose These redirects ensure that users accessing old URLs are properly redirected to the new Mintlify documentation structure, maintaining link integrity and improving user experience during the migration.
## Description Fixes casing in docs.json to correspond to filenames. <!-- Uncomment and add a description of the change --> <!-- Optionally, uncomment the heading and add details about how you tested the change and how reviewers should test it. For example: ## Testing - [ ] Local build succeeds without errors or broken internal links (`hugo server`) - [ ] PR tests succeed - [ ] The Lychee Github action run against the PR branch reports no broken links Replace the `[ ]` with `[x]` to check off the item instead of leaving it unchecked. Otherwise, delete this entire section from opening to closing comment. --> <!-- Optionally, uncomment the heading and add one or more lines like these. Otherwise, delete this entire section from opening to closing comment. ## Related issues - Fixes DOCS-12345 - Fixes #12345 -->
…ble via direct URLs (#1740) ## Summary This PR moves the W&B Launch documentation section to a separate hidden tab, making it accessible only via direct URLs while removing it from the main site navigation. ## Changes 1. **Removed W&B Launch from Platform tab** - The entire Launch section has been removed from the Platform tab navigation 2. **Created separate W&B Launch tab** - All Launch documentation and navigation structure has been moved to its own tab 3. **Added `hidden: true` flag** - Attempting to hide the tab from the main navigation bar ## Intent The goal is to make the W&B Launch section: - ✅ Accessible via direct URLs (e.g., `/platform/launch`, `/platform/launch/walkthrough`) - ✅ Maintain full navigation structure when accessed - ✅ Hidden from the main documentation navigation ## Note The `hidden: true` flag on tabs may not be fully supported by Mintlify. This PR proposes the configuration for testing and discussion. Alternative approaches may be needed such as: - Custom CSS to hide the tab - Keeping the section in the Platform tab but using other visibility controls - Moving to a separate documentation instance ## Testing - Access any Launch URL directly to verify the pages are still accessible - Check if the Launch tab appears in the main navigation (it should be hidden if Mintlify supports it) - Verify all internal Launch navigation works when on Launch pages
## Description Removes "https://weave-docs.wandb.ai" from Models and Inference docs. With the exception of Models -> evaluate-models.mdx because I couldn't find the corresponding page in the new Weave docs. ## Note * There are about 12 weave pages (`docs/weave/*`) that need to be updated. * 1 Release notes page needs updating <!-- Uncomment and add a description of the change --> <!-- Optionally, uncomment the heading and add details about how you tested the change and how reviewers should test it. For example: ## Testing - [ ] Local build succeeds without errors or broken internal links (`hugo server`) - [ ] PR tests succeed - [ ] The Lychee Github action run against the PR branch reports no broken links Replace the `[ ]` with `[x]` to check off the item instead of leaving it unchecked. Otherwise, delete this entire section from opening to closing comment. --> <!-- Optionally, uncomment the heading and add one or more lines like these. Otherwise, delete this entire section from opening to closing comment. ## Related issues - Fixes DOCS-12345 - Fixes #12345 --> --------- Co-authored-by: Matt Linville <matt.linville@wandb.com>
## Description Some of the integration docs were missing and/or repeated within multiple locations in docs.json <!-- Uncomment and add a description of the change --> <!-- Optionally, uncomment the heading and add details about how you tested the change and how reviewers should test it. For example: ## Testing - [ ] Local build succeeds without errors or broken internal links (`hugo server`) - [ ] PR tests succeed - [ ] The Lychee Github action run against the PR branch reports no broken links Replace the `[ ]` with `[x]` to check off the item instead of leaving it unchecked. Otherwise, delete this entire section from opening to closing comment. --> <!-- Optionally, uncomment the heading and add one or more lines like these. Otherwise, delete this entire section from opening to closing comment. ## Related issues - Fixes DOCS-12345 - Fixes #12345 -->
## Description - Fixed some important links to point to correct anchors - Fixed awkward list formatting in privacy page - Update the MS Entra setup instructions - Fixed awkward list formatting - Fixed excessive # of images - Validated instructions against current official Entra docs
## Description This PR replaces hard-coded Weave links and replaces them with internal references. This also fixes WEave reference links across the docs that were using an old schema.
## Summary This PR adds analytics integration for Mintlify documentation with proper consent management. ## Changes - **Added OneTrust cookie consent management**: Integrates with OneTrust for GDPR-compliant cookie consent - **Segment Analytics integration**: Uses self-hosted Segment build at `wandb.ai/sa-docs.min.js` - **Microsoft Clarity analytics**: Added for user behavior insights - **Consent-based loading**: Analytics scripts only load when users grant marketing or statistics consent - **User engagement tracking**: Added user engagement tracking script ## Key Features 1. **Privacy-first approach**: Analytics only loads after user consent 2. **Consent synchronization**: Implements `wpConsentSync` to manage different consent categories: - Statistics - Marketing - Functional - Preferences 3. **Performance**: Scripts load asynchronously to minimize impact on page load ## Implementation Details The implementation follows these steps: 1. Load the user engagement and OneTrust scripts 2. Wait for user consent via OneTrust 3. Only load analytics (Segment & Clarity) if marketing or statistics consent is granted 4. Fire analytics.page() when Segment is ready ## Testing - Verify OneTrust banner appears correctly - Confirm analytics only loads with proper consent - Check that Segment and Clarity are tracking correctly when consent is given
This was referenced Jun 5, 2026
johndmulhausen
added a commit
that referenced
this pull request
Jun 5, 2026
The intro said "Select the button below to try a PyTorch Quickstart example project on MNIST data" but no button ever followed it (dangling since the original Mintlify import in #1727). Supply the missing button using the existing <ColabLink> snippet component (the same one used in Weave quickstarts and integration guides), pointing at the W&B Tables Quickstart Colab in wandb/examples — the PyTorch-on-MNIST notebook the text describes. Verified it resolves. 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
4 participants
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.
Description
Migrate docs to Mintlify
wandb/docsto Mintlifywandb/weavedocs to Mintlify and import them intowandb/docswandb/weavereference docsCut from here down during squash and merge
Potential cut-over scenario
To go live on Mintlify, we would:
mainno longer triggers a Cloudflare deploy.wandb/docsat themintlify-importbranch. Also adjust the site title at the same time. The Mintlify PR checks start running.main.main. (do not squash and merge). The cut-over is complete.mintlifytestrepo in Github.Testing