Welcome to our Q&A feature on Roq, an innovative static site generator built on top of Quarkus. In this series, we explore the project’s origins, technical decisions, and future direction, drawing on insights from Andy Damevin, a developer who spent nearly a decade contributing to Quarkus. Roq started as a personal experiment to see if Java and Quarkus could match the performance of Go-based static site tools. Below, we answer key questions about what makes Roq unique and how it can transform your site building workflow.

What is Roq and How Did It Start?

Roq is a static site generator built using the Quarkus framework. It began as a side project by Andy Damevin, a longtime Quarkus contributor. His goal was simple: test whether Quarkus could power a static site generator that rivals the speed and simplicity of popular tools written in Go. By leveraging Quarkus’s fast startup and low memory footprint, Roq compiles content into static HTML with minimal overhead. The project proves that Java-based tools can compete in performance while offering the robustness of the Java ecosystem. Roq is open source and community-driven, aiming to give developers a familiar yet high-performance alternative for building blogs, documentation sites, and more.

Why Choose Java and Quarkus for a Static Site Generator?

Andy Damevin explains that Java’s mature ecosystem and Quarkus’s container-first design make a compelling combination. Quarkus provides near-instant startup and low resource usage, often compared to Go binaries. This makes it ideal for static site generation, where build speed and low overhead are critical. Additionally, Java developers can reuse existing libraries for templating, Markdown parsing, and asset processing. Roq also benefits from Quarkus’s dev mode, enabling hot reload during development. By choosing Quarkus, Roq avoids the complexity of Python or Ruby dependencies while delivering performance close to native Go tools. The decision reflects a belief that Java can be both productive and performant for modern web projects.

How Does Roq Achieve Speeds Comparable to Go?

Roq achieves its speed through several Quarkus optimizations. First, Quarkus compiles ahead-of-time (AOT) to native binaries using GraalVM, reducing startup to milliseconds. During builds, Roq processes pages in parallel, leveraging Quarkus’s reactive engine for non-blocking I/O. Content caching and incremental builds further accelerate regeneration. Andy notes that for medium-sized sites (hundreds of pages), Roq’s build times are similar to Hugo or Zola. The key is that Roq does not sacrifice Java’s type safety or tooling; it simply uses modern compilation techniques to eliminate overhead. This allows developers to enjoy Java’s strengths without the traditional performance penalty.

What is the Migration Process to Roq?

Migrating to Roq involves converting your existing content and templates into Roq’s structure. Roq supports standard Markdown files with front matter, and its templating engine is based on Qute, a Quarkus-native template language. For Jekyll or Hugo users, you can often copy content folders, then rewrite layouts using Qute syntax. Andy recommends starting with a simple site to test the workflow. Roq provides CLI commands to scaffold a new project and build static output. There is also a migration guide in the official docs covering asset handling, permalink configuration, and dataset compatibility. The process is straightforward for teams already using Java, as they can integrate Roq into existing build pipelines with Maven or Gradle.

What Are the Key Features of Roq?

Roq offers several features tailored for modern static sites:

• Markdown and AsciiDoc support – Easily author content with standard markup.
• Live reload in development – Instant feedback thanks to Quarkus dev mode.
• Flexible templating with Qute – Type-safe templates with auto-completion in IDEs.
• Asset pipeline – Minify CSS/JS, optimize images, and generate sitemaps.
• SEO and RSS out of the box – Built-in feed generation and meta tag support.
• Plugin system – Extend Roq with custom hooks for preprocessing or postprocessing.

These features make Roq suitable for both personal blogs and large documentation hubs, all while keeping the build fast and the output lightweight.

What Does the Future Hold for Roq?

Andy Damevin sees a bright future for Roq, with planned improvements including deeper GraalVM integration for even smaller binaries, better incremental builds, and a richer plugin ecosystem. The project aims to reach feature parity with established generators like Hugo while maintaining a Java-first developer experience. Community contributions are welcome, especially for themes and starter kits. Andy also hints at possible integration with headless CMS platforms and serverless deployment options. The ultimate goal is to prove that Java can be a first-class citizen in the static site generation space, offering both performance and maintainability.