Dosu LogoDosu Logo
Ask
Join our Discord
Organization avatar
HelmorPublic
Caspian's Workspace
DocumentsHelmor
_template
_template
Type
External
Status
Published
Created
Jul 14, 2026
Updated
Jul 14, 2026
Source
frontend/marketing/data/case-studies/_template.mdx

Company Background#

Provide a brief overview of the company:

  • What they do
  • Size/scale (users, stars, community, etc.)
  • Their main product or service
  • Link to their website/repository

The Challenge#

Describe the specific problems they were facing:

  • What pain points were they experiencing?
  • How was this affecting their team/community?
  • What solutions had they tried before?
  • What were the consequences of not solving this?

The Solution: Dosu Integration#

Explain how Dosu was implemented:

  • What specific Dosu features were used?
  • How was it integrated into their workflow?
  • Any customizations or specific configurations?
  • Timeline for implementation

Results and Impact#

Quantify the improvements with specific metrics:

  • Metric 1: Before vs. After (e.g., "Response time decreased from 2 days to 5 minutes")
  • Metric 2: Percentage improvements (e.g., "66% of issues handled automatically")
  • Metric 3: Team productivity gains
  • Qualitative benefits: Team satisfaction, community happiness, etc.

Key Features That Made the Difference#

Highlight the specific Dosu capabilities that were most valuable:

  1. Feature Name: Brief explanation of how it helped
  2. Feature Name: Brief explanation of how it helped
  3. Feature Name: Brief explanation of how it helped

Looking Forward#

Discuss future plans and expansion:

  • Additional Dosu features they're exploring
  • Plans to expand usage
  • Long-term vision for AI-assisted maintenance

Get Started#

Optional call-to-action section linking to relevant resources:

  • Link to Dosu's open-source program (if applicable)
  • Link to pricing page
  • Link to documentation

Template Instructions#

When creating a new case study:

  1. Replace all placeholders in square brackets with actual content
  2. Update the date to the publication date
  3. Set draft to false when ready to publish
  4. Add the hero image to /public/blog/ and update the images field
  5. Create the author in /data/authors/ if needed
  6. Generate a unique slug that's SEO-friendly
  7. Add relevant tags beyond the default ones if needed
  8. Include specific metrics wherever possible
  9. Add quotes from the company team if available
  10. Ensure the company field matches exactly how you want it displayed

Image Guidelines:#

  • Hero image should be 1200x630px (16:9 aspect ratio)
  • Include company logo and Dosu branding
  • Use consistent styling with other case studies
  • Save as PNG or JPG in /public/blog/

Content Guidelines:#

  • Focus on specific, measurable outcomes
  • Include quotes from team members when possible
  • Keep technical details accessible to non-technical readers
  • Emphasize the human impact, not just the metrics
  • Tell a story arc: problem → solution → transformation
Documents
01 - Get Started
01 - Introduction
02 - Install Helmor
03 - Add a Repository
04 - Create a Workspace
05 - Send Your First Agent Task
02 - Core Concepts
01 - Repository
02 - Workspace
03 - Session
04 - Agent
05 - Changes and Review
06 - GitHub Integration
03 - User Workflows
01 - Start a New Task
02 - Review Agent Changes
03 - Continue an Existing Session
04 - Commit and Ship Work
05 - Use Multiple Agents Safely
04 - Developer Setup
01 - Local Development Setup
02 - Architecture Overview
03 - Frontend Overview
04 - Backend Overview
05 - Sidecar Overview
06 - Testing Guide
07 - Debugging Guide
05 - Troubleshooting
01 - Agent Not Responding
02 - GitHub Authentication Issues
03 - Workspace Errors
04 - Sidecar and CLI Issues
05 - Logs and Diagnostics
7-data-driven-checks-to-ensure-your-documentation-roi-is-high
AGENTS
AGENTS
AGENTS
CHANGELOG
CLAUDE
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
README
SKILL
SKILL
SKILL
STRIPE_README
[tag]
_template
advanced-full-text-search
advanced-jsonb-indexing
ai-contributions-open-source
ai-is-better-at-maintaing-docs-than-humans
april-2025-newsletter-dosu-does-docs
august-2025-dosu-drop
automating-github-issue-triage
better-agent-testing-with-distributed-dependency-injection
blog_template
building-the-future-of-knowledge-management-june-dosu-drop
celery-preserializers-a-low-friction-path-to-pydantic-support
channel-creation-github-repository
channel-creation-slack-channel
ci-jobs
cncf-dosu-case-study
combating-open-source-maintainer-burnout-with-automation
concepts-channel
concepts-data-sources
concepts-interactions
configuration
confluence_edited_markdown
confluence_original_markdown
conn-idle-timeout
conn-limits
conn-pooling
conn-prepared-statements
data-batch-inserts
data-n-plus-one
data-pagination
data-upsert
december-2025-dosu-drop
default
devin
docling-open-source-growth-with-dosu
dosus-new-fact-based-reasoning-agent-is-generally-available
features-auto-labeling
features-generate-docs
features-issue-triage-qa
features-maintain-docs
february-2025-newsletter-introducing-spaces
from-maintenance-to-innovation-freeing-developers-with-ai-automation
george-xu
github-configuration
github-features-dosu-in-first-awesome-continuous-ai-list
github-installation
how-dosu-used-langsmith-to-achieve-a-30-accuracy-improvement-with-no-prompt-engineering
how-lancedb-supercharged-our-knowledge-graph
how-preset-keeps-apache-superset-healthy
how-triliumnext-revitalized-an-abandoned-open-source-project-with-dosus-help
index
index
internal-vs-external-documentation-audience-first
iterating-towards-llm-reliability-with-evaluation-driven-development
january-2026-dosu-drop
july-dosu-drop-public-spaces-enter-the-chat
knowledge-management-in-the-ai-era-why-documentation-is-more-critical-than-ever
li-zheng
lock-advisory
lock-deadlock-prevention
lock-short-transactions
lock-skip-locked
march-2025-newsletter-dosu-knows
marcos
markdown
mastering-auto-labeling-taming-the-backlog-with-intelligent-labels
may-2025-dosu-drop-new-agent-self-serve-pricing-fresh-look
member-invitation
michael-ludden
michael-mangus
migrate-celery-to-dbos-dosu
monitor-explain-analyze
monitor-pg-stat-statements
monitor-vacuum-analyze
notion_edited_markdown
notion_original_markdown
november-2025-dosu-drop
october-2025-dosu-drop
onboarding-introduction
onboarding-key-concepts
onboarding-quickstart
open-source-labeling-best-practices
page
page
pages
photos
pull_request_template
query-composite-indexes
query-covering-indexes
query-index-types
query-missing-indexes
query-partial-indexes
reliable-data-orchestration-for-ai-applications
response-previews
scaling-support-and-documentation-at-Dify-one-of-the-fastest-growing-oss-projects
schema-data-types
schema-foreign-key-indexes
schema-lowercase-identifiers
schema-partitioning
schema-primary-keys
security-privileges
security-rls-basics
security-rls-performance
september-2025-dosu-drop
settings
slack-configuration
slack-installation
sparrowhawk
taylor-dolezal
the-code-understanding-paradox-when-ai-makes-writing-code-fast-but-understanding-it-slow
top-5-zombie-problems-resurrected-by-ai-tools
using-ai-to-generate-and-maintain-documentation
what-lodashs-issue-backlog-reveals-about-oss-burnout
what-the-mythical-man-month-got-right-about-documentation
word2vec-to-transformers-ai-evolution