The people best positioned to write good Apache framework documentation — the committers and long-term contributors — have no good tooling for turning their deep knowledge into beginner-accessible, example-driven tutorials. Right now, if an Apache Tobago or Apache Turbine contributor wants to write a 'getting started with advanced features' guide, their only option is to write a wiki page or a blog post. Neither is versioned with the framework, neither can embed runnable code, and neither has a feedback loop that tells the author where readers get stuck.

The reason this gap persists is that the people who feel it — contributors — are unpaid volunteers whose tooling priorities go toward the codebase itself. Doc tooling investment competes with feature work and bug fixes. Meanwhile, the downstream pain is felt by end users ('documentation is too hard for beginners,' 'little content available over the internet') who are not in the room when tooling decisions get made. This is the classic open-source contributor-user split: the people who experience the pain don't have write access to fix it, and the people with write access don't feel the pain acutely enough to prioritize it.

What's needed is a lightweight authoring environment that lets a contributor write a tutorial in Markdown, embed code blocks that are tested against a specific framework version in CI, annotate where beginners commonly get confused, and publish it with a versioned URL that Apache can link to from their official docs. The result is persistent, testable, community-maintained tutorials — not one-off blog posts that go stale.

This is a business because Apache isn't the only open-source Java project with this problem — any framework with a small community and a high beginner drop-off rate has it. The wedge is Apache because the pain is documented and the community is reachable, but the product generalizes to the broader JVM ecosystem and beyond.

What to build

Build a GitHub-integrated tutorial authoring tool where open-source framework contributors write versioned, Markdown-based tutorials with embedded code examples that are automatically tested via CI against tagged framework releases, and published to a canonical URL that increments with the framework version.

Where to start

Approach Apache Shiro contributors directly — Shiro has high external adoption, an active GitHub presence, and publicly acknowledged documentation gaps in issues and discussions, making contributors there the most likely early adopters with a clear personal motivation to improve the new-user experience.

The hard part

Getting the first Apache PMC to officially link to tutorials published through an external tool requires navigating Apache's strong preference for hosting their own content — the trust barrier with a new commercial tool may require an extended free period or an open-source core before any PMC points newcomers there.

How it makes money

Free for open-source projects hosted on GitHub or GitLab; paid tier ($49–99/month) for private repositories or enterprise teams writing internal onboarding documentation for their own Apache-based customizations, with a one-time setup fee for CI integration into existing pipelines.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Java Web Frameworks.

More ideas in Java Web Frameworks