Foundation

Why This Project

The motivation behind Instant Wiki.

Most wikis today are over-engineered. They require databases, build pipelines, client-side frameworks, and megabytes of JavaScript just to render a few paragraphs of text.

Instant Wiki takes a different path. It asks a simple question: what if a wiki could be as lightweight as a static HTML file?

The Problem

  • Slow loads: Wiki pages ship 100KB+ of JS before content appears
  • Complex stacks: Databases, auth systems, CMS layers just for text storage
  • Maintenance burden: Updates require deployment pipelines and monitoring

The Philosophy

Instant Wiki embraces these constraints:

  • Text-first: Markdown as the only source of truth
  • Minimal payload: Each route stays under 14KB (gzip)
  • No client JS: Server-rendered HTML, CSS only when needed
  • Simple hosting: Just needs a static file server anywhere

When It Makes Sense

Choose Instant Wiki when:

  • Your content is mostly text and documentation
  • You prioritize speed over features
  • You want something you can understand in an afternoon
  • You prefer editing files over using a CMS

What You’re Giving Up

  • Real-time collaboration
  • Rich media management
  • User authentication
  • Dynamic content filtering

If you need those features, this isn’t the right tool. But if you just want a fast, simple wiki that loads instantly and costs nothing to host, you’re in the right place.

Continue with Getting Started.

Type at least 2 characters.