The Problem

I want to write blog posts that incorporate custom React components that readers can interact with to better showcase what I'm talking about.

For example, I want to include a button I made in Framer Motion in a post as "this is what we are going to build" and then show how I went about building it.

The Solution

MDX: Sounds like I want to write in MDX. Great. I'll do that.

Remix: I've also been wanting to really give Remix a share shake after reading Kent Dodds': Why I Won't Use Next.js. So let's try that. Specifically, the section "The Web Platform". (Which is kinda funny as I also want to explore building universal apps right now.)

So I venture over to Remix docs on using MDX and I see this:

Rather than compiling your content at build-time like this document demonstrates, it's typically better UX and DX if you do this at runtime via something like mdx-bundler. It's also much more customizable and powerful. However, if you prefer to do this compilation at build-time, continue reading.

Uhhh yea, I can see that with the LONG build times I have for this current site that is completely static and takes 12min to build. But, I dont want to switch to build at runtime if it costs my users ANY increase in load time.

So, can I have both?

Here's some philosophy from Remix about their approach to performance - it's telling that the first section is titled "The Edge."

With distributed servers and databases running at the edge, it's now possible to serve dynamic content at speeds comparable to static files.

Cloudflare Workers or Cloudflare Pages?

https://github.com/remix-run/remix/discussions/1248

Sketch

what about remix + instandb + some fancy something to store all the html pages into sqlite on D1 like remix does?