adobe/hyde

A front-end to Jekyll that parses C++ sources to produce and enforce out-of-line documentation

Owned by Adobe

View on GitHub ↗Jump to charts ↓

adobe/hyde has 300+ stars and 40+ forks on GitHub, is written in C++, and was last pushed on Mar 11, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 41 minutes ago
Added to GitGenius on October 12th, 2026
Created on October 17th, 2018
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 45
Total Stargazers: 341 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Hyde is a documentation tool for C++ that parses source code to produce and enforce out-of-line documentation compatible with Jekyll.

The tool addresses the problem that inline documentation comments in source code tend to fall out of sync with the code they describe and clutter files that experienced developers no longer read. Hyde solves this by using Clang's libTooling library to compile and analyze C++ sources, extracting documentation information into structured Markdown files with YAML front-matter. This approach keeps documentation separate from code while maintaining a direct link to the actual source through compilation-based analysis rather than comment parsing.

Developers should choose Hyde if they maintain C++ libraries and want documentation that stays synchronized with code changes. The tool suits projects that already use Jekyll for static site generation or are willing to adopt it. Hyde operates in two modes: an update mode for library developers to refresh documentation against source changes, and a validate mode for build engineers to verify that documentation reflects the current codebase. The tool can also output AST-based information as JSON, enabling additional tooling on top of its analysis. Unlike inline documentation systems, Hyde's structured output and schema enforcement make it possible to detect when documentation has drifted from implementation.

The project maintains active development with regular commits addressing bug fixes and feature improvements. The codebase shows consistent attention to build infrastructure, with updates to CMake configuration and Docker support. Contributors engage substantively with issues, providing detailed responses and implementing requested enhancements. The project demonstrates stability in its core functionality while remaining responsive to user needs and environmental changes in the C++ ecosystem.