One app.
Every way
to deliver it.
Write one app. Choose SPA or MPA navigation, then ship it as static files or serve its prebuilt documents from a server.
Choose the output.
Keep the app.
Delivery should be a build decision, not a rewrite. Fuzor compiles the same pages, layouts, components, Markdown, and island boundaries for every profile.
Pages as files
Folders become routes. HTML and Markdown become the document your visitor actually receives.
Explore routing ↗Compile the known
Layouts and static components are resolved ahead of time. The server selects a complete document.
Understand rendering ↗Islands where needed
Keep the page plain HTML; mount vanilla, React, Solid, or Vue inside independent boundaries.
Discover islands ↗Build ahead.
Move less at runtime.
The compiler already knows the route structure and shared layout. Let it do that work once so the browser or server can focus on delivery and interaction.
Read the documentation →Content remains useful before JavaScript runs.
This site's documentation lives in Markdown-only route folders.
Typed errors, services, and controlled concurrency keep builds explicit.