Introducing Slide-CN

Have you ever created a presentation, and tried to change the font size of the header? You need to change it manually for every slide. If you want to change the font color, you need to select all the text in every slide, and change it manually. Then, after making these changes, you realize it looked better before, but going back to the previous version is a nightmare.

The problem is not with fonts, color, or anything else. I am a developer, and these things are solved problems. I am frustrated with the fact that I am still having to struggle with basic things like version control, and reusability. With code, I have git. I can create one component and re use it everywhere, so why can’t I do the same with slides?

Slides are just UI. It is not rocket science.

So why not create slides with code?

So I built Slide-CN

What this unlocks

Version control for presentations

Because I am now using code to create slides, I can also use things like, git and github. You can review your collaborators changes. Your workflow as a whole gets better.

Reusability without templates

Slide-CN is component based. You can create small custom components that you can reuse anywhere you want. You can set color schemes. You can standardize how presentations from your company is supposed to look like, without having to create complex templates.

Real data, not screenshots

Your slide deck is basically a website now. That means, you can call APIs, and dynamically render content. You can pull data from your dashboard in real time. Your presentations become alive.

Interactive storytelling

Your slides are now made out of web components. Web components that can be interactive. React to clicks, mouse movements, and more. Maximum freedom, zero restriction.

Link, not a file

Host your presentation, and use a url to share it with people. That way, you can update your slides, and everyone sees the new version. This means, you dont have to deal with flies like “demo_version_2_final_final” anymore. You can also track how people progress through you slides, and see where people are the most engaged, where people loose interest and so on. Unlimited freedom to do what you want.

Open-source

There are a ton of open source component libraries that you can drag and drop into a slide-cn project. A few examples of these are

• Reactbits


• Shadcn


• MagicUI

Nothing comes close to the kind of ecosystem code has.

Why not Gamma or Canva?

I will probably write a whole article about this, but the short version is that these tools like Canva and PPT are an abstraction over code. They were built in a time where the thought of coding a website seemed alien to most people.

That is not the case now

Anyone can pickup cursor and prompt away. People are not shying away from code now. The tools available to vibecode are getting better every month. Even LLMs are natively better at “coding” than at “canva.”

Gamma represents the opposite end of this spectrum, where an agent generates your entire presentation. You give up all control. You can not change minor details, you are constrained by their system. Slide-CN gives you complete freedom, along with the speed that comes from vibe-coding.