Reference Surface

Show the wedge without pretending the ecosystem is huge.

This showcase is the public map for what RustFrame should help people start from: one flagship workflow, one workflow-first starter, a few credible references, and optional frontend-stack starters that still keep the runtime model intact.

Browse entries Read the template guide

How to read this

Not every card is making the same claim.

The flagship app proves the wedge. Starters help teams move faster. Reference apps show layout and workflow patterns. The point is to help people choose a starting point honestly.

Ecosystem rule

Keep the surface tied to real jobs.

Community templates, remote sync patterns, and capability extensions should all stay anchored to credible local-first workflows instead of broad framework marketing.

Next step

Use the catalog and docs together.

Pick a starting point here, then move into the docs for the exact manifest, runtime, packaging, and trust-model constraints behind it.

Showcase

One public map for starters, flagship workflows, and references.

The showcase stays intentionally selective. Entries here should help a builder decide what to clone, adapt, or study next without implying that RustFrame already has a broad plugin ecosystem.

Loading showcase…