redis/docs

Documentation for Redis, Redis Cloud, Redis Enterprise, Redis Iris, Redis Insight, RDI, Redis Feature Form, and Redis Radar

Owned by Redis

View on GitHub ↗Jump to charts ↓

redis/docs has 80+ stars and 350+ forks on GitHub, is written in Java, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Documentation / SpecificationCategory(s):NoSQL, Key-Value & CachesDocumentation ToolsDatabases & Storage
Added to GitGenius on October 12th, 2026
Created on November 17th, 2023
Open Issues & Pull Requests: 58 (+1)
GitHub issues: Enabled
Number of forks: 371
Total Stargazers: 86 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.6 hours
Mean response time: 22.6 hours
90th percentile: 2.6 days
Tracked items: 261

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 94% of issues opened in the past year have since been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 136 days
Stale 30+ days: 7
Stale 90+ days: 4

Recent activity

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

Top labels

  • bug (35)
  • invalid (33)
  • dev (31)
  • rs (26)
  • question (25)
  • cmds (12)
  • enhancement (6)
  • k8s (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Redis Docs is a documentation site generator that publishes reference material for Redis and its related products.

The project solves the problem of maintaining accurate, up-to-date documentation across multiple Redis offerings including Redis Cloud, Redis Enterprise, Redis Iris, Redis Insight, RDI, Redis Feature Form, and Redis Radar. It uses Hugo as its static site generator, organizing content into markdown files with structured front matter, and employs Tailwind CSS for styling. The build pipeline automatically publishes changes from the main branch to the live documentation site without manual intervention, with per-branch staging URLs available for preview before merging.

The tool suits teams maintaining comprehensive product documentation that needs to scale across multiple related products and versions. It requires Python, Node.js, Hugo, Make, and Git to build locally. The automatic publishing workflow means contributors can merge changes and see them live after the build and CDN cache refresh, eliminating separate deployment steps. The project includes archetypes for consistent front matter, reusable HTML partials for common components like tables of contents and breadcrumbs, and shortcodes for embedding tabbed code examples and notification blocks within markdown.

The project maintains active development with regular updates to its build configuration and tooling. Pull requests receive automated staging link comments from the documentation team's bot, enabling reviewers to validate changes before merge. The codebase includes a dedicated guide for AI agents accessing the documentation, indicating intentional support for automated tooling integration. Build requirements are explicitly versioned, with Hugo pinned to a specific extended edition release to ensure consistent output across contributors.