quarkusio/quarkusio.github.io

Website for Quarkus project

Owned by Red Hat · part of IBM

View on GitHub ↗Jump to charts ↓Open shareable report →

quarkusio/quarkusio.github.io has 150+ stars and 400+ forks on GitHub, is written in HTML, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 37 minutes ago
Type:Documentation / SpecificationCategory(s):Backend FrameworksDocumentation ToolsWeb Development
Added to GitGenius on October 12th, 2026
Created on March 1st, 2019
Open Issues & Pull Requests: 210 (+0)
GitHub issues: Enabled
Number of forks: 411
Total Stargazers: 186 (+0)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 32.0 hours
Mean response time: 136.9 days
90th percentile: 410.2 days
Tracked items: 64

Maintainer activity

5 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 63% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 20% of tracked open issues have had no activity in three months. Only 37% of issues opened in the past year have been closed. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 57
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 328 days
Stale 30+ days: 38
Stale 90+ days: 17

Recent activity

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

Top labels

  • triage/needs-triage (16)
  • enhancement (12)
  • area/infra (2)
  • area/website (2)
  • good first issue (2)
  • area/search (1)
  • dead-link (1)
  • performance (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Quarkus.io Website is the documentation and content site for the Quarkus project, built as a static site generated from HTML and served through GitHub Pages.

The site serves as the central hub for Quarkus documentation, guides, and blog content. It is built using a Maven-based development workflow with Quarkus itself, allowing developers to run the full site locally including all guides, or optionally run a faster version without guides or with only the latest guides. The site generation is handled by a tool called Roq, which processes the content and generates the complete site that gets deployed to GitHub Pages.

Anyone contributing to or maintaining this site needs Java 21 or later and Maven to run locally. The development setup is straightforward: cloning the repository and running a Maven command starts a dev server on port 8042. Initial startup takes a minute or two while dependencies download and the site generates, but subsequent starts are faster. For blog contributions, the project maintains an authors file and requests that human writers retain their voice and perspective rather than relying on generative AI to write entire posts, though AI assistance in writing is acceptable. Deployment happens automatically via GitHub Actions when commits reach the main branch, though local deployment is possible using the act tool if needed.

The project maintains active engagement with contributors through clear documentation of the contribution process. The README includes explicit guidance on blog writing standards and author registration procedures, indicating attention to content quality and contributor experience. Development activity shows responsiveness to maintaining the site infrastructure and documentation pipeline, with automated deployment workflows in place to keep the live site synchronized with repository changes.