The other day my boss hit me with one of those questions that leaves you speechless: "Why are we messing around with TypeScript and MDX if we could have this same thing on Substack in five minutes?".
At first, I struggled to react. Substack is convenient, it has a network, and it works beautifully. However, I soon realized we were comparing apples to oranges. While Substack works like a digital printing press, GitBlog is born as a creative lab.
Here's why MDX isn't just "Markdown on steroids," but the key to creating content that closed platforms will never be able to touch.
The Static Trap
Most blogs today are text cemeteries. You go in, you read (if you're lucky), and you leave. Substack has made this very easy to monetize, but the experience remains the same as reading a newspaper in 1990, just with scrolling.
The real value of GitBlog isn't publishing text — it's designing premium experiences.
The MDX Pillars that "Kill" Static Content
Here are real examples of what we can build here that is simply impossible on a closed platform:
1. Data Playgrounds (Playing with the Data)
In a conventional blog, you're limited to looking at a screenshot of a chart. In GitBlog, the user takes control.
Try moving the controls below:
See the difference? This isn't reading about compound interest — it's seeing it happen before your eyes.
2. Bespoke Widgets: The Difference Between Reading and Understanding
Imagine you want to teach someone how to tune the animations of their app. How would you do it?
📄 Explanation in text
"Stiffness determines the return velocity. Damping controls the energy dissipated per cycle. A high mass adds inertia to the system..."
Correct. Forgotten in 30 seconds.
⚡ Interactive explanation
Crank Stiffness up to 400 and drop Damping to 3 — you'll see an exaggerated bounce. That's what would happen to your app's menu.
Now tweak it until it feels right.
Retention with text
10%
after 48 hours
Interactive retention
75%
after 48 hours
Time to understand
8 sec
vs ~3 min reading
3. Scrollytelling and 3D Models
Thanks to our <ModelViewer /> component, the narrative becomes physical. Look at this model: you can rotate it, zoom in, and explore it at your leisure.
Forget Substack's static GIFs: here the object is real and you have it directly in your hands.
4. Real-Time Connection
An MDX post can query external APIs, so it's never a text frozen in time. For example, here are the current stats of a GitHub repository pulled directly from its API:
Conclusion: The Blog as a Product
After this debate, the answer to my boss was clear: We're not building a blog — we're developing a living digital product.
Substack serves its purpose if all you're looking for is to send emails. But if you want your content to be a pedagogical tool that feels alive and "premium," code is the way.
What about you? Do you think interactivity is the future of writing, or are we just code romantics?