Skip to content

[DO NOT MERGE] - DocEngine Knowledgebase demo#2200

Draft
dfinster wants to merge 2 commits intomainfrom
doceng/wandb-docs-22499702630
Draft

[DO NOT MERGE] - DocEngine Knowledgebase demo#2200
dfinster wants to merge 2 commits intomainfrom
doceng/wandb-docs-22499702630

Conversation

@dfinster
Copy link
Member

This PR implements the MDX page updates caused by DocEngine (manual run).

Workflow run: Run number 35 — View build
Branch: df/wandb-kbView branch

Warning

This is built from a DRAFT DocEngine branch with DRAFT information that must not be published! DO NOT MERGE THIS PR!

This PR contains auto-generated updates from DocEngine.

Source: coreweave/docengine @ df/wandb-kb
Trigger: workflow_dispatch | Site: wandb-docs

Important

Please review before merging. Do not assume it is safe!

Generated by DocEngine CI (merge to main).
@github-actions
Copy link
Contributor

github-actions bot commented Feb 27, 2026

📚 Mintlify Preview Links

🔗 View Full Preview

✨ Added (246 total)

📄 Pages (246)

File Preview
support/index.mdx Support
support/inference/articles/api-error-code-401-authentication-failed.mdx Api Error Code 401 Authentication Failed
support/inference/articles/api-error-code-402-you-exceeded-your-cur.mdx Api Error Code 402 You Exceeded Your Cur
support/inference/articles/api-error-code-403-country-region-or-ter.mdx Api Error Code 403 Country Region Or Ter
support/inference/articles/api-error-code-403-the-inference-gateway.mdx Api Error Code 403 The Inference Gateway
support/inference/articles/api-error-code-429-concurrency-limit-rea.mdx Api Error Code 429 Concurrency Limit Rea
support/inference/articles/api-error-code-500-the-server-had-an-err.mdx Api Error Code 500 The Server Had An Err
support/inference/articles/api-error-code-503-the-engine-is-current.mdx Api Error Code 503 The Engine Is Current
support/inference/index.mdx Inference
support/inference/tags/administrator.mdx Administrator
... and 236 more files

📝 Changed (1 total)

⚙️ Other (1)
File
docs.json

🤖 Generated automatically when Mintlify deployment succeeds
📍 Deployment: 6d1ae6a at 2026-02-27 19:21:54 UTC

@github-actions
Copy link
Contributor

github-actions bot commented Feb 27, 2026

🔗 Link Checker Results

All links are valid!

No broken links were detected.

Checked against: https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app

@mdlinville
Copy link
Contributor

https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app/support:

  • I wish the Support landing page navigation were more interesting.
  • Ideally the landing page would have featured articles from each top-level support category?

https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app/support/inference and siblings:

  • I wish the cards had more content, I'm not sure what. Maybe some article titles?

https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app/support/inference/tags/api-errors and other tag pages: LGTM! Maybe we could allow the cards to have a bit longer preview text.

One thing that bugs me: The diagonal arrows on the cards make me think they will open in new tabs, but they don't. Do you think they need that arrow?

📚 Mintlify Preview Links

🔗 View Full Preview

✨ Added (246 total)

📄 Pages (246)

File Preview
support/index.mdx Support
support/inference/articles/api-error-code-401-authentication-failed.mdx Api Error Code 401 Authentication Failed
support/inference/articles/api-error-code-402-you-exceeded-your-cur.mdx Api Error Code 402 You Exceeded Your Cur
support/inference/articles/api-error-code-403-country-region-or-ter.mdx Api Error Code 403 Country Region Or Ter
support/inference/articles/api-error-code-403-the-inference-gateway.mdx Api Error Code 403 The Inference Gateway
support/inference/articles/api-error-code-429-concurrency-limit-rea.mdx Api Error Code 429 Concurrency Limit Rea
support/inference/articles/api-error-code-500-the-server-had-an-err.mdx Api Error Code 500 The Server Had An Err
support/inference/articles/api-error-code-503-the-engine-is-current.mdx Api Error Code 503 The Engine Is Current
support/inference/index.mdx Inference
support/inference/tags/administrator.mdx Administrator
... and 236 more files

📝 Changed (1 total)

⚙️ Other (1)
File
docs.json
🤖 Generated automatically when Mintlify deployment succeeds 📍 Deployment: 6d1ae6a at 2026-02-27 19:21:54 UTC

@dfinster dfinster changed the title docs: Update from DocEngine [TEST BRANCH-DRAFT-DO NOT MERGE] [DO NOT MERGE] - DocEngine Knowledgebase demo Feb 27, 2026
@dfinster
Copy link
Member Author

@mdlinville

https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app/support:

I wish the Support landing page navigation were more interesting.
Ideally the landing page would have featured articles from each top-level support category?

It does have the featured articles from each product category. There's only a few featured articles, specifically the ones from the existing page here: https://docs.wandb.ai/models/support

Which ones would you nominate to be featured? The template has sub-headings per product like we discussed.

https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app/support/inference and siblings:

I wish the cards had more content, I'm not sure what. Maybe some article titles?

Article titles sounds messy to me:

  • How many titles should we show? All of them?
  • Should they be links?

I think that UX would be worse somehow.

https://wb-21fd5541-doceng-wandb-docs-22499702630.mintlify.app/support/inference/tags/api-errors and other tag pages: LGTM! Maybe we could allow the cards to have a bit longer preview text.

I've tried it with longer text, and things get messy in most cases after 60 characters because then you get into Markdown formatting, bullet-points, etc. I played with it for about 20 minutes to find a happy compromise. I can show you the variable to tweak if you want to see some examples.

The purpose of the body text preview was just to entice them to click, not to have them see the answer.

One thing that bugs me: The diagonal arrows on the cards make me think they will open in new tabs, but they don't. Do you think they need that arrow?

The arrow indicates that the card itself is clickable, not just a display element. I got that feedback from Lauralee on the CoreWeave home page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-generated DO-NOT-MERGE For PRs that should not be merged yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants