Onboarding courseware for Apache Java frameworks, sold to engineering teams

The moment a team inherits a Sling-based CMS, a Felix OSGi application, or a Struts codebase and realizes their mid-level developers can't meaningfully contribute without weeks of self-directed flailing through Apache wiki pages written for maintainers, not learners. That's when someone starts searching for training and finds almost nothing purpose-built.

The gap persists because the Apache Software Foundation is a volunteer-run open source body with no commercial training arm and no incentive to build one. Documentation is written by the people who built the framework, for people already close to it. Third-party training vendors focus on high-volume frameworks with mass-market demand — Spring, Hibernate, React — because that's where seat volume is. Apache frameworks are used heavily in enterprise and government contexts but are treated as niche, so nobody builds the courseware.

What teams currently do instead is send developers to read mailing list archives and Javadoc, hire expensive consultants for initial setup, or require developers to already know OSGi before they get the job. One complaint specifically flags that 'lack of Wicket experts in the market was a big issue' — that's not a pipeline problem, it's a training supply problem. Another says Struts 'demands loads of learning experience' with no clear path to acquire it. Existing generic Java learning platforms cover language fundamentals but stop well short of framework-specific mental models like OSGi service lifecycles, Jena's RDF graph API, or Wicket's stateful component model.

This is a business and not a feature because the need recurs every time a team hires a new developer, acquires a codebase, or upgrades a major framework version. A company running a Felix-based product doesn't buy training once — they buy it every time headcount grows or the framework shifts. Engineering managers pay for this because the alternative is weeks of lost productivity per developer, or a consultant engagement at $200+/hour to explain concepts that could be taught in a structured five-hour course.

What to build

Build a structured, self-paced video course library covering OSGi fundamentals through Apache Felix and Aries, Wicket component model, Struts action lifecycle, and Jena's RDF API — each framework as a standalone module, sold to engineering teams via a per-seat annual license with a manager dashboard showing completion.

Where to start

Start specifically with Apache Sling and AEM developers — there's an unusually large commercial ecosystem around Adobe Experience Manager built on Sling, which means thousands of developers who need Sling-specific knowledge and a clear corporate buyer willing to spend on training.

The hard part

Getting the first five paying teams requires credibility you haven't earned yet — Apache framework users are skeptical of training from unknown sources, and the real experts who could validate the content are either unpaid Apache contributors or expensive consultants with no interest in commoditizing their knowledge.

How it makes money

Annual per-seat license to engineering teams, priced per developer per framework module — starts around $199/seat/year per module, with volume discounts above 10 seats. Optional one-time setup for custom private cohort delivery.