nextra VS webcontainer-core

co-author here

we put in a lot of effort into our docs and we'd greatly appreciate any criticism or feedback! Langfuse is powerful but the docs should help beginners to quickly get started and then incrementally use more features.

docs are OSS, repo: https://github.com/langfuse/langfuse-docs

built using: https://github.com/shuding/nextra

However, this may just be due to the lack of proper documentation from the Nextra side of things (shoutout to Nextra though, regardless).

Nextra - Nextra is another option for creating documentation sites. While it might not be as well-known as Docusaurus, Nextra offers a modern and minimalist approach to building documentation. It is designed to be lightweight and user-friendly, making it a good choice for those who prefer a simple and clean documentation style. You can explore more about Nextra on their official website.

I have looked at https://nextra.site/ but that doesn't work with the app router yet. So I'm wondering if there's another alternative.

You could also have a look at Nextra. You can use mdx components to build your blog (including support for server-side fetching). I'm currently using their documentation template, but it seems they also have a blog template.

We write everything in Markdown, as it's the closest you'll get to a 'universal' format. Then, we use a static site generator to turn the docs into a website. Current projects are using Nextra for this. If you ever need to change site generators, you still have all the markdown docs and image files, so it's pretty easy to change.

https://nextra.site/ is nice

Today I found this tool for Next.js called Nextra. You can effortlessly create a blog post website or a documentation website. All you need is markdown. Simply export your markdown from Notion and utilize it with Nextra to enjoy all the cool features, including full-text search, syntax highlighting, dark/light mode, and even image support. Everything is generated at build time, making it a static website which is Blazingly fast. https://nextra.site/

How does it work? There is no backend whatsoever. The API Security Academy leverages WebContainers, a new technology that allows running full-blown node instances directly in the browser. Each WebContainer contains a live GraphQL application, so you'll not only understand why a vulnerability is risky, but also how to exploit it and, most importantly, how to fix it.

StackBlitz made the claim "... run Node.js, entirely inside your browser" #658, then had to revise it's claim to "We currently do not expose a way to use WebContainer outside of StackBlitz.com,".

> Wasm though seems like the likely general heir, and will have many different offerings for how to do that (Deno being one!).

I was recently blown away by some ideas that StackBlitz [0] apply based on WebContainers. The idea of a "server in the browser", they allow you to run Node-based environment like that via Wasm.

[0] https://stackblitz.com/

[1] https://webcontainers.io/

See https://webcontainers.io.

This very simple fact is well known flaw, which was already often criticized and asked for solutions by users. It doesn't only affect this kind of very exotic bootstrap applications but also significantly limits rusts usefulness in many other areas. Pure browser based scientific code documentation and example notebooks (e.g. jupyterLite) and sandboxed CI and IDE solutions (e.g. web containers) as available for many other languages are simply not available for rust because of this very fundamental issue.

Looks like they plan to open it. From the FAQ section of README (https://github.com/stackblitz/webcontainer-core#faqs):

> Is there a developer API?

I'm skeptical about stackblitz claims. The last time I checked that is closed source code https://github.com/stackblitz/webcontainer-core/issues/658.

StackBlitz claimed https://blog.stackblitz.com/posts/introducing-webcontainers/ to have implemented Node.js in the browser, though I have not observed any evidence of that being true and correct https://github.com/stackblitz/webcontainer-core/issues/658.

The other honorable mention is StackBlitz, a web-based web editor for making containers that run Javascript applications. Interestingly, StackBlitz is championing WebContainers, a technology that allows developers to start NodeJS servers within the browser. The downside is, this technology only works with Javascript-based projects (NodeJS, NextJS, etc). I include it here because WebContainers could easily be extended to support other languages via WASM, like Ruby. I’ll also add in Buildah, a tool for building OCI images. I won’t say much about this tool because it’s designed for building images; you still need another service, like Podman, to actually create the containers.