The Vibe Company

This repo publishes content directly from Markdown files in the codebase.

There are two public entry types:

• learnings
• articles

1. Install dependencies:

bun install

2. Copy envs and fill them in:

cp .env.example .env.local

No CMS-specific environment variables are required for content publishing.

3. Start the app:

bun dev

Main URLs:

• Site: http://localhost:3000

The site exposes:

• /sitemap.xml - generated from indexable static routes and Markdown content.
• /llms.txt - generated Markdown index for LLMs and agents.

Content lives in:

• content/articles/*.md
• content/learnings/*.md

Each file uses simple frontmatter:

---
title: Why we simplified the CMS
slug: why-we-simplified-the-cms
summary: A short explanation of why the old setup had too much surface area.
publishedAt: 2026-02-20
---

Markdown body here.

Adding or editing an article is now a normal code change. The site rebuilds from those files on deploy.

Optimize images referenced from Markdown before opening a PR:

bun run images:optimize

The optimizer is lossless and idempotent:

• source images stay in place and remain the canonical content references;
• generated variants are written under public/images/_optimized/;
• regular content and cover PNG/JPEG images get lossless WebP variants;
• ogImage PNG assets get losslessly recompressed PNG variants;
• already-optimized variants are left byte-for-byte unchanged on later runs.

Check image budgets without rewriting files:

bun run images:check

bun run build

Production deploys are handled by GitHub Actions on main.

PR previews are also deployed through GitHub Actions to Vercel preview environments. To make them work, configure these repository secrets:

• VERCEL_TOKEN
• VERCEL_ORG_ID
• VERCEL_PROJECT_ID

Each PR from this repository gets a fresh preview deployment and the workflow updates a comment on the PR with the Vercel URL.

For security, previews are skipped for PRs opened from forks because GitHub does not expose repository secrets to those runs.