OpenAPI, brought up to spec

OpenAPI, brought up to spec The last post told JSONSchema's origin story: it exists because ApptiveGrid needed OpenAPI, and OpenAPI needs a way to describe request and response bodies. OpenAPI is the other half of that story - a Pharo implementation of the OpenAPI 3 specification, three packages deep: `OpenAPI-Core` models a document as an object tree and can validate a whole document against the

Soil v5 released

Soil v5 released I announced this release at ESUG 2026 in Plovdiv, but only now found the time to actually write it up. Soil v5 is out. Quick side note on what that even means: Soil doesn't do releases as git tags or semantic versioning. We never found MAJOR.MINOR.PATCH to be as clear as it pretends to be, so instead there's just a branch per version - v1, v2, v3, and so on - each one a moving poi

JSONSchema, picked back up

JSONSchema, picked back up JSONSchema didn't start as its own thing. It exists because ApptiveGrid needed OpenAPI, and OpenAPI needs a way to describe request and response bodies - which means it needs JSON Schema. Building a JSON Schema engine in Pharo was table stakes for having a documented API at all, so that's what got built: a small, generic core, cleanly separate from ApptiveGrid itself, pl

Foliage released

Foliage released Foliage is a static web site generator pretty much like Octopress/Jekyll. Instead of being a tool you invoke from the commandline foliage is meant to be a library to create a customized web site with a script. The script can then be used to invoke foliage headless on a commandline. The basic idea of foliage is to reify all structures of the web site from filesystem hierarchy down