Documentation request: architecture overview

It stands to reason that many people who will be using Frankenphp have little to no experience with Go or even Caddy.

While it does appear to be relatively easy to get started with frankenphp without such knowledge, surely people would benefit from having at least a conceptual understanding of what is going on. With that, they might even start dabbling in writing their own Go/Caddy modules.

I have no expectation that Frankenphp should provide detailed documentation on Caddy, Go etc, but would it be possible to add a simple documentation article that provides an overview of Frankenphp's architecture?

Is Caddy embedded in Frankenphp? Or is Frankenphp a Caddy Module? What about Mercure? How would we extend and/or modify them all - with additional caddy modules? Can Go code be written to make use of Frankenphp worker mode, or is frankenphp even needed if we intend to write Go code? Etc...

I'm sure those questions are contradictory and even incoherent, but I hope you get the sense of what I'm trying to describe and learn.

Id imagine it could all be explained in a few paragraphs, along with some links to relevant Caddy documentation and perhaps Go documentation.

Thanks!

Start by identifying the existing documentation structure and the architecture concepts raised in the issue: FrankenPHP's relationship to Caddy, Mercure, Go, and worker mode. The work is done when a concise overview answers those questions and links to relevant Caddy and Go documentation.