docs(weave): add Haystack integration page (WBDOCS-1061)#2484
docs(weave): add Haystack integration page (WBDOCS-1061)#2484anastasiaguspan wants to merge 4 commits intomainfrom
Conversation
Made-with: Cursor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Skill metadata{
"skill": "author-docs",
"version": "1.0.0",
"depends_on": { "style-guide": "1.0.0" },
"skills_invoked": [],
"model": "unknown",
"note": "style-guide skill multi-pass not invoked with sub-agents; manual AGENTS.md alignment only"
} |
Resume prompt (later session)Continue from PR #2484 (branch |
📚 Mintlify Preview Links✨ Added (1 total)📄 Pages (1)
📝 Changed (2 total)📄 Pages (1)
⚙️ Other (1)
🤖 Generated automatically when Mintlify deployment succeeds |
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-haystack-docs-1061-b.mintlify.app |
|
what's up with this? shouldn't runing the style-guide be required? "note": "style-guide skill multi-pass not invoked with Yes. Per author-docs, running style-guide is required, not optional. From the skill (Step 8, self-review): • Invoke the style-guide skill on the draft. This is required, not optional. So that PR comment was wrong in two ways:
Why it showed up: The style-guide skill is written to use multiple sub-agent passes (Checkpoint 1 and 2). In this session that full Bottom line: You’re right to question it — running style-guide is required by author-docs; the metadata note was inconsistent with If you want this cleaned up on PR #2484, the next steps are: run style-guide on weave/guides/integrations/haystack.mdx (and any |
Made-with: Cursor
Style-guide follow-upRan the full style-guide workflow (all 8 passes applied in-session to Updated skill metadata: {
"skill": "author-docs",
"version": "1.0.0",
"depends_on": { "style-guide": "1.0.0" },
"skills_invoked": ["style-guide"],
"model": "unknown"
} |
ngrayluna
left a comment
There was a problem hiding this comment.
Ahh sorry, I missed this. I'm not sure if want to add this in the public docs. We sifted through integration docs so that only those supported by Growth get added. Suggest moving this to Fully Connected Blog.
@johndmulhausen Does this sound bout right?
|
the plugin seems to have gotten the pip install library name hallucinated! that's bad: weights_biases-haystack not weave-haystack NEVERMIND, i stand corrected: the pip library name in the haystack docs FAILS and the one the plugin wrote does install: |
Summary
Adds a Frameworks integration page for Haystack using Deepset's
WeaveConnector, per WBDOCS-1061.Changes
weave/guides/integrations/haystack.mdx: prerequisites (WANDB_API_KEY,HAYSTACK_CONTENT_TRACING_ENABLED),pip install weave-haystack, minimal pipeline example, links to Deepset open source and Cloud docs.docs.json(Frameworks) andweave/guides/integrations.mdx.Sources
weave-haystack(not the outdatedweights_biases-haystackstring on some Haystack pages).Needs SME verification
pipeline_namemaps to the Weave project name as described for every deployment (W&B SaaS, dedicated).Skill metadata
Author-docs workflow; style-guide multi-pass not run as sub-agent. English only (no
ja//ko/entries per localization process).Made with Cursor