A new WO-like web framework, written from scratch: familiar to a WebObjects programmer but without Foundation, EOF or the session lock. Where everything else here is heading.

A slimmed-down fork of Project Wonder with just what a modern WO application needs to run on a current JDK. Seventy-one frameworks became four; Java 1.8 became JDK 25.

The template parser for WebObjects: WOOgnl's inline syntax on ng-objects' parser, with line-and-column errors shown in the page, exception context and a render heat map in development.

A Jetty-based WOAdaptor for classic WO applications: virtual threads, streaming request bodies and WebSockets, on the same HTTP stack ng-objects uses.

WOLips cut down to a single plugin focused on template editing for WO and ng-objects, with refactorings WOLips never had, an element reference, and a dev server that tools and agents can drive.

The successor to WO's .api files: typed, directional, documented element bindings, so an editor can check a template against a real contract instead of guessing.

A Claude Code skill that teaches an agent the edit, refresh, validate loop through the Parslips dev server and the running application's own endpoints.

A Maven plugin that builds self-contained .woa bundles from scratch rather than wrapping the old Ant tasks. No NEXT_ROOT, no system-wide WO install, and the JVM is switchable at launch.

A Jetty reverse proxy that takes the place of mod_WebObjects — and, optionally, a complete front-end server that replaces Apache and certbot too: TLS with native ACME, HTTP/2, WebSockets and hot reload, from one TOML file.

wotaskd and JavaMonitor, forked from Wonder and cleaned up: Foundation-free, with the wire protocols finally documented and a deploy endpoint that swaps bundles and bounces instances for you.