docs: add missing Colab button in tables walkthrough#2738
Open
johndmulhausen wants to merge 1 commit into
Open
docs: add missing Colab button in tables walkthrough#2738johndmulhausen wants to merge 1 commit into
johndmulhausen wants to merge 1 commit into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
📚 Mintlify Preview Links📝 Changed (1 total)📄 Pages (1)
🤖 Generated automatically when Mintlify deployment succeeds |
Contributor
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-fix-tables-walkthrough-colab-card.mintlify.app |
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>
johndmulhausen
force-pushed
the
fix/tables-walkthrough-colab-card
branch
from
e15e3f9 to
665e9dc
Compare
johndmulhausen
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a dangling reference in the Tables walkthrough by replacing text that referred to a non-existent “button” with an actual UI element: a <Card> linking to the W&B Tables Quickstart Colab notebook.
Changes:
- Replaces the broken “Select the button below…” instruction with a runnable Colab entry point.
- Adds a
<Card>linking directly to the W&B Tables Quickstart notebook inwandb/examples.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
models/tables/tables-walkthrough.mdxtold readers to "Select the button below to try a PyTorch Quickstart example project on MNIST data" — but no button ever followed it. The sentence has pointed at nothing since the original Mintlify import (#1727).This supplies the missing button using the existing
<ColabLink>snippet component (/snippets/_includes/colab-link.mdx) — the same one used in the Weave quickstarts and integration guides — rather than inventing a new component. It points at the W&B Tables Quickstart Colab inwandb/examples, which is the PyTorch-on-MNIST notebook the text describes (its own title: "View & analyze model predictions during training … using PyTorch on MNIST data"). Verified the notebook resolves; the same notebook is already linked frommodels/tables/visualize-tables.mdx.Change
Scoped to this one file.
Note for reviewers
#2725 (the
models/tablesstyle pass) also touches this same line (it trims a trailing space), so expect a trivial merge conflict between the two — resolve in favor of this change. Merge order does not matter.🤖 Generated with Claude Code