We've been fairly quiet the last few months, mostly because we were heads-down building and not great at talking about it at the same time.

That's actually why this site exists now.

The problem with app-only communication

Crimpd has always lived inside the app. Feature updates went into release notes that maybe 5% of users read. Our philosophy has traditionally been to deliver features for users and let them discover them organically. Sometimes we shared updates on social media, but with the way Instagram suppresses reach (unless you pay to boost), many users just didn't see them.

That was fine when Crimpd was smaller, but it meant many of the features and content updates we shipped weren't adopted as quickly as we hoped. We realised we had no good way to explain what we were building, why we were building it, or how to actually use it once it shipped.

So before we could ship any of those things, we had to build this.

What's here now

Despite being a ground-up rebuild, the site mostly has the same spartan feel as before. But there are two new things that matter:

1. A proper documentation section
   We've ported and updated some of our existing guides for getting started with Crimpd, building a training plan with Crimpd+, and managing your subscription. Each one walks you through the app step by step, and we'll keep adding to these as new features land.

2. This blog
   You're reading the first real post on it and there are two more — Release 7.0 and the New Paradigm Climbing Playlist — but going forward this is where we'll announce features, explain the thinking behind changes, and occasionally write about training concepts and research that don't fit into the app itself.

The nerdy bits

For the fellow nerds out there (since I know I'll be asked), here's the tech stack we chose for the rebuild:

• React 19 with React Router 7 (Framework mode w/ pre-rendering)
• Vite 7 — bundler and dev server
• TypeScript 5.9
• Chakra UI v3 — component library and design system

We've migrated from an old Gatsby site hosted on AWS CloudFront to Cloudflare Workers. There was nothing wrong with CloudFront, but we've been using Cloudflare Workers at Lattice and have been very impressed with the platform. This choice meant we stayed away from Next.js since they don't play too nicely together. We also didn't use Astro since we wanted to add quite a bit more interactivity than Astro is designed for.

What's coming

We have a lot planned for 2026. I'm not going to list features here because timelines shift and I'd rather show you things when they're ready than promise them before they are. But the reason we invested in building this site first is that several of the upcoming changes are significant enough that a two-line release note wouldn't cut it. They need proper explanations, guides, and context — and now we have a place to put all of that.

If you want to stay in the loop, check back here. We'll be posting more frequently than we have in the past, because now we actually can.

-pk