feat(docs): rename Production tab to Deployment; promote Use Cases under Community#28
feat(docs): rename Production tab to Deployment; promote Use Cases under Community#28isaacbmiller wants to merge 1 commit intomainfrom
Conversation
Greptile SummaryThis PR makes two focused docs IA changes: it renames Confidence Score: 5/5Safe to merge — only a P2 dead-CSS finding; all redirects are in place and nav logic is correct. No P0 or P1 findings. The single new finding is a ~30-line block of unused CSS (dspy-quote-row) that is cosmetically harmless. Previously flagged issues (Guardrails card removal, Moody's absent from table) are known to the team. docs/docs/stylesheets/extra.css — dead dspy-quote-row CSS block should be removed before further style additions accumulate. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
subgraph Before["Before (nav)"]
B_L["Left tabs: Learn · Tutorials · API Reference"]
B_R["Right tabs: DSPy in Production · Community · FAQ"]
B_R_P["DSPy in Production\n/production/index.md\n(Use Cases card + 4 tool cards)"]
B_R_C["Community\n→ community-resources.md\n→ use-cases.md\n→ community-ports.md"]
B_R --> B_R_P
B_R --> B_R_C
end
subgraph After["After (nav)"]
A_L["Left tabs: Learn · Tutorials · Deployment · API Reference"]
A_R["Right tabs: Community · FAQ"]
A_L_D["Deployment\n/production/index.md\n(4 tool cards + Use Cases callout)"]
A_R_C["Community\n→ use-cases.md\n→ built-with-dspy.md\n→ community-resources.md"]
A_L --> A_L_D
A_R --> A_R_C
end
subgraph Redirects["Redirects added"]
R1["production/companies.md → community/use-cases.md"]
R2["community/community-ports.md → community/built-with-dspy.md"]
end
Reviews (22): Last reviewed commit: "feat(docs): move Deployment to technical..." | Re-trigger Greptile |
b616c7b to
41b8399
Compare
2710679 to
b6bd336
Compare
e65088d to
1bf5bfb
Compare
1c38c11 to
db77245
Compare
…r Community
Two focused IA changes so each top-level tab matches what's actually inside it.
1. Move "Deployment" to the technical tabs on the left.
- Rename the tab `DSPy in Production` -> `Deployment`.
- Move it from the right side of the toolbar (next to Community / FAQ) to
the left, between Tutorials and API Reference.
- Replace the page content with a 4-card overview of the tooling DSPy ships
for production: Monitoring & Observability, Reproducibility, Deployment
with MLflow, Scalability.
2. Promote "Use Cases" under Community.
- Add `Community -> Use Cases`: logo-led hero (Shopify, Databricks, Dropbox,
JetBlue, Replit, AWS) followed by 3 featured case-study spotlights and the
full companies roster.
- Consolidate `community/community-ports.md` into `community/built-with-dspy.md`
(papers, OSS, ports, providers, integrations).
- Logos sourced from public assets (Simple Icons, Wikimedia Commons);
monochrome variants invert correctly in dark mode.
- Add redirects from old paths (`production/companies.md`,
`community/community-ports.md`) to the new locations.
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
db77245 to
c184e17
Compare
This PR makes two focused changes to the docs IA so each top-level tab matches what's actually inside it.
1. Move "Deployment" to the technical tabs on the left
The previous
DSPy in Productiontab sat on the right side of the toolbar next toCommunityandFAQ, which framed it as social-proof / non-technical content. But the page itself was entirely technical: MLflow tracing, reproducibility, model serving, scalability. The location and title both undersold it.DSPy in Production→Deployment.TutorialsandAPI Reference, where the rest of the technical content lives.2. Promote "Use Cases" under Community
The social-proof content (companies running DSPy in production) lived under the old
DSPy in Productiontab, which conflated marketing with technical reference. It belongs underCommunity.Community → Use Cases: a logo-led hero (Shopify, Databricks, Dropbox, JetBlue, Replit, AWS) followed by featured case-study spotlights (Shopify, Dropbox) and the full companies roster.Communitytab at Use Cases instead of the third-party blog list.community/community-ports.mdintocommunity/built-with-dspy.md(papers, OSS projects, language ports, providers, integrations).production/companies.md,community/community-ports.md) redirect to the new locations.