ManageIQ/manageiq.org

Website for the ManageIQ Management Platform

Owned by Red Hat · part of IBM

View on GitHub ↗Jump to charts ↓

ManageIQ/manageiq.org has 20+ stars and 100+ forks on GitHub, is written in HTML, and was last pushed on Jul 23, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 12 minutes ago
Type:Documentation / SpecificationCategory(s):Documentation ToolsDeveloper Tools
Added to GitGenius on October 12th, 2026
Created on May 13th, 2014
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 103
Total Stargazers: 24 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 37.0 days
90th percentile: 74.1 days
Tracked items: 2

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: 305 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

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

Top labels

  • Mend: dependency security vulnerability (9)
  • Mend: dependency dashboard (1)
  • developer (1)
  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ManageIQ.org is a Jekyll-based static site that serves as the web presence for the ManageIQ Management Platform.

The site aggregates documentation from multiple distributed sources into a unified web experience. It pulls together getting-started guides hosted in the repository itself, user reference documentation maintained in a separate repository that supports both Markdown and legacy Asciidoc formats, API documentation, developer guides included as a Git submodule, and links to external automation resources. The build process preprocesses these sources using Ruby tooling, adding Jekyll front matter where needed and using rsync to organize reference documentation before the final site generation.

Contributors should choose this approach if they need to maintain a cohesive documentation site while allowing different documentation groups to live in separate repositories under independent maintenance. The project suits teams managing complex software platforms where documentation naturally divides into user guides, API references, developer resources, and getting-started materials. The separation of concerns means contributors can work on documentation in the appropriate repository without needing to understand the entire site structure.

Development activity shows consistent engagement with documentation updates and site maintenance. The project accepts contributions through standard pull request workflows and maintains active communication channels for questions and suggestions. The codebase includes test coverage for the Ruby processing logic that handles documentation aggregation and transformation.