feat(blog): add "Build once, at build time" essay

[Adebesin-Cell]

🔗 Linked issue

N/A. New blog post, no tracked issue.

🧭 Context

We started sketching Chakra v4 earlier this year and the work pulled us deep into Panda, learning Rust and pushing on the v2 compiler's speed. I wanted to write about that from the inside, so this kicks off a Panda CSS series on the blog written from actually shipping it, not from the changelog.

📚 Description

Adds a new post, content/blog/build-once-at-build-time.md.

What's in it:

• The origin story: prototyping Chakra v4 with Segun, the move to Panda for extraction/generation, and learning Rust along the way.
• The v2 Rust/Oxc engine and the real benchmark numbers behind it (cold parse ~23x, warm re-parse ~360x), plus one under-the-hood decision I like: keeping an O(n²) linear scan on purpose because real style objects rarely clear 50 keys.
• Why build-time extraction beats runtime CSS-in-JS, with a plain css() example and how atomic dedup keeps the output from growing with your app.
• A short teaser for part two on runtime css() caching.

Notes for review:

• Marked draft: true for now.
• Links point at v2.pandacss.com, which isn't live yet but will be soon. Flagging so the not-yet-resolving links are expected.
• No cover image on this one, matching the recent posts that ship without one.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lope	Ready	Preview	Aug 18, 2026 7:01pm