The Panmind Stack: Building 2020s Architecture in 2010

Sun, 12 Apr 2026 00:00:00 +0000

In 2009, a small team in Rome started building Panmind, a collaborative platform for sharing and organizing knowledge. The company was Mind2Mind S.r.L., founded by Emanuele Caronia.

Panmind itself didn’t survive. But the stack we built for it did something interesting: it anticipated architectural patterns that wouldn’t become mainstream for five to ten years. We were building single-page applications before the term existed, streaming analytics before Segment, and sharing sessions across languages before JWTs.

I presented some of our open-source spin-offs at the Ruby Social Club in Milan in 2010, but that post only scratched the surface — it was a quick rundown of Rails plugins. This is the deeper story: three technologies, three problems solved too early, and how the same ideas showed up in every major framework that followed.

Act 1: jquery-ajax-nav — SPA Before SPAs¶

Panmind needed to feel fast. Clicking a link shouldn’t reload the entire page — it should swap just the content area, instantly. In 2023 you’d reach for React, or Turbo, or HTMX. In 2009, none of those existed. There was no History API. There was no pushState. The URL hash fragment — the bit after # — was the only part of the URL you could change without triggering a page reload. So that’s what we used.

Architecture on Marcello Barnaba

The Panmind Stack: Building 2020s Architecture in 2010

Act 1: jquery-ajax-nav — SPA Before SPAs¶