The Problem

You know the cycle. Late-night inspiration strikes. You spin up a repo, sketch out the vision, maybe even bang out a prototype. The dopamine is flowing. This one's different. This one matters.

Then reality sets in. If you're going to share this—really share it—you'll need a landing page. A README that doesn't suck. Maybe a logo. Probably a blog post explaining the why. And someone will ask "where's the demo?" so you should probably deploy that too. Suddenly the idea that felt so alive five minutes ago feels like homework. So you don't ship. You tell yourself "when it's ready."

But ready never comes.

The old playbook was: build in silence, polish obsessively, then announce with a bang. But in the AI-powered era where you can go from idea to working prototype in hours, that approach is backwards. The energy isn't in the finished product—it's in the becoming. The best projects are built in public, with feedback loops from day zero, with momentum from people who bought into the vision before the code was even written.

When you ship early, feedback compounds. Each piece of interest—a star, a comment, a "what if you tried..."—adds fuel. The project grows momentum instead of bleeding it.

The Vision

The pitch is the first version.

Kindling represents a fundamental shift in how we build. The articulation of intent becomes the act of creation itself. In an era where AI can translate vision to working code faster than ever, the bottleneck is no longer implementation—it's clarity of thought and speed of iteration.

A polished project page forces you to crystallize the problem, the solution, the why. It becomes your north star before a single line of code is written, and your first artifact shipped to the world.

The Personal OS Movement

This is about more than tools—it's about a new practice emerging among self-starters and builders: the Personal OS, the custom workflow, the bespoke system tailored to how you think and work.

We're entering an age where everyone can be a tools builder, where the gap between "I wish this existed" and "here's v0.1" collapses to days. Kindling itself is a manifestation of this philosophy—built in a single session, shipped before it was "done."

Working in Public Compounds

• One project page is a statement
• Ten is a portfolio
• Fifty is a body of work that tells the story of your curiosity and craft

Each page—whether the project ships, pivots, or gets shelved—adds to your surface area for serendipity. Someone discovers your abandoned idea and offers to collaborate. A recruiter sees your taste through the problems you choose. An investor spots the throughline across your experiments.

How It Works

Dead simple by design:

That's it. No build step. No framework decisions. No design paralysis. Just your idea, rendered beautifully, deployed instantly.

# The entire deployment config
services:
  web:
    image: node:20-slim
    volumes:
      - /path/to/kindling-pages:/app:ro
      - ./.project.md:/app/content/.project.md:ro

What happens when someone visits your page? Content is read at runtime—no build step means changes appear instantly:

Rich Content Support

Kindling Pages renders your markdown with full styling support—tables, diagrams, interactive charts, and syntax-highlighted code all work out of the box.

Interactive Charts

Write chart code directly in markdown with ```tsx rechart blocks. Full Recharts API with complete JavaScript/TypeScript power—including formatters, event handlers, and dynamic calculations:

Features

Code Blocks

Syntax highlighting powered by Shiki:

// Your entire deployment in one file
interface ProjectFrontmatter {
  name: string;
  tagline: string;
  description: string;
  subdomain: string;
  status: 'idea' | 'prototype' | 'beta' | 'live';
  github?: string;
  links?: { label: string; url: string }[];
}

What's Next

This is v0.6—iterating in public. Here's the roadmap:

Want This?

I'm building this for myself—50-100 project ideas that deserve to see daylight. But if this resonates with you:

• Star the repo — Signal that this matters
• Ship your own — Fork it, deploy your ideas, tell me about it
• Tell me what's missing — What would make you use this every week?

Built by @thebrubaker as part of a "ship from v0" experiment. Let's see how many ideas we can get out of the graveyard.