Skip to main content

Starting a knowledge base in public

· 2 min read
Roshan Ragunath
Roshan Ragunath
Consultant and Developer

I'm starting a public knowledge base.

The plan is simple: when I learn something useful -- a Claude Code pattern, an n8n trick, a Betty Blocks edge case -- I write it down here instead of letting it evaporate.

Why public​

A private second brain is a fine thing, but I want this stuff to be findable. If I figure out how to embed Claude Code and Codex in the same workspace and write it down on this site, future-me can find it via Google. So can anyone else who hits the same wall.

Notion stays for messy drafts and personal capture. This site is for things that are useful enough to share.

What to expect​

  • Cheatsheets in /docs/ -- durable references like the Claude Code cheatsheet. I update these in place.
  • Posts here on the blog -- things I figured out this week, or rough notes I haven't promoted to a cheatsheet yet.

No schedule. I write when there's something worth writing.

Built with​

This site runs on Docusaurus, hosted on Cloudflare Pages, source on GitHub. The whole stack is free and the build-to-live time is about 30 seconds. Hard to beat for a developer content site.

You can find the source at github.com/RoshanRagunath/knowledge -- PRs and corrections welcome.