[slorber]

Hey, Docusaurus maintainer here.

I'm not sure to understand what you mean by "Docusaurus is static". Docusaurus builds static pages and allows you to plug JS/React code anywhere in your docs, so it's quite interactive and can run anything that can run in a browser, including REPLs.

I read the Fly article but still don't really understand what Livebook is about. They say they use Livebook themselves, but the examples linked to only display a regular non-interactive doc to me.

Do you have any production url showing me an experience that is possible in Livebook, and impossible in Docusaurus?

[Dowwie]

Sure, here's a simple demonstration of what livebook can do that docusaurus cannot, at least without maintainer expertise ;)

Imagine the following.

<here's a code block containing project metadata>

we click a play button to start an elixir runtime based on that metadata code block

<here's a "component" that securely connects to an elixir system running in a kubernetes pod in production, exposing an elixir REPL to interact with it>

with this component, we then issue commands to inspect state, manage elixir "processes" in the runtime, etc

[slorber]

> we click a play button to start an elixir runtime based on that metadata code block

Can you show a concrete example? IE a real production url running this?

What is "metadata"?

In Docusaurus you can have a live playground evaluating on your browser, or you can embed any embeddable playground if it requires a server integration.

> with this component, we then issue commands to inspect state, manage elixir "processes" in the runtime, etc

Another example would be useful.

So this is just an embedded widget to interact with something remote? Why can't this be built as a React component that you can add to any Docusaurus page?

---

It looks to me that you don't need maintainer knowledge to build that, and React knowledge is enough.