DataDog/documentation

The source for Datadog's documentation site.

Owned by Datadog

View on GitHub ↗Jump to charts ↓

DataDog/documentation has 600+ stars and 1k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 50 minutes ago
Type:Documentation / SpecificationCategory(s):Documentation ToolsDeveloper Tools
Added to GitGenius on October 12th, 2026
Created on December 12th, 2011
Open Issues & Pull Requests: 459 (+0)
GitHub issues: Enabled
Number of forks: 1,332
Total Stargazers: 623 (+0)
Total Subscribers: 630 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.1 days
Mean response time: 57.6 days
90th percentile: 170.4 days
Tracked items: 58

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 31
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 192 days
Stale 30+ days: 29
Stale 90+ days: 23

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 2

Top labels

  • documentation (6)
  • logs (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Datadog documentation is a static site generator project that publishes markdown content to the Datadog documentation site using Hugo.

The repository stores the source markdown files that power the Datadog documentation site. Hugo processes these markdown files to generate the static HTML documentation site. Contributors can edit documentation directly through GitHub's web interface via Edit buttons on published pages, or by forking the repository and submitting pull requests. The Documentation team reviews all contributions marked as ready for review.

The project welcomes external contributions and is suitable for anyone wanting to improve Datadog's documentation. Contributors should focus pull requests on addressing one or two specific problems rather than bundling many unrelated changes. The repository provides contribution guidelines and expects PR descriptions to be written by humans, explaining the problem being solved and the context for the change rather than listing individual modifications. The team emphasizes that while AI tools can assist in generating content, human review ensures quality standards are maintained before publication, and contributors should validate AI-generated content independently and plan timelines accordingly for review.

The project maintains active engagement with contributors through automated PR review assignment to the Documentation team. Pull requests receive human review and feedback, with the team requesting clarification on large changes and providing guidance on how to structure contributions. The team explicitly addresses content quality standards in their guidelines, distinguishing between acceptable contributions that solve specific problems and those that require additional validation before merging.