Blogs
From ReadMe to MakeSliDev v0.1

From ReadMe to MakeSliDev v0.1

August 6, 2025

TL;DR I found out a great web app that edits markdown in live time and wanted to combine it with SliDev for PPT Generation.

Intro

I was bikeshedding and found out this great project:

MPL2 | An Awesome ReadME Generator To Jumpstart Your Projects!

Blame again to the people building in public: https://www.reddit.com/r/github/comments/1itqlh4/i_got_tired_of_writing_readmes_so_i_built_an/

For the ones who mind their time, Shaan is also the dev behind this OSS Pomodoro Timer: https://github.com/ShaanCoding/Pomodoro-Timer

About MPL 2.0 🚀

It’s not just about keeping the initial license; it’s about a specific type of copyleft that applies at the file level.

The main restriction is: If you modify an existing file that is under the MPL 2.0 license, or create a new file that contains MPL 2.0-licensed code, that modified or new file must also be licensed under the MPL 2.0 when you distribute it.

Here’s why that’s a more accurate way to look at it:

  • File-level copyleft: The MPL 2.0’s copyleft “stops” at the file boundary. This is the key difference from a strong copyleft license like the GPL, which would require the entire “larger work” to be under the GPL. With the MPL, you can have a project with some files under the MPL and other, completely new files under a different, even proprietary, license.

  • Distribution trigger: The obligations only kick in when you distribute the code. If you modify the code and only use it internally within your organization, you are not required to share those changes.

  • Other obligations: While the file-level copyleft is the primary restriction, you also have other, less onerous obligations. These include:

    • Keeping the original copyright and license notices.
    • Informing recipients that the code is under the MPL 2.0.
    • Making the source code for the MPL-licensed parts available to anyone you distribute the binary to.

So, your summary is conceptually correct in that the core idea is to maintain the license on the specific part of the code it applies to.

However, the details of how that “keeping” works—at the file level and upon distribution—are what truly define the MPL 2.0’s unique balance.

Isnt it great?

MakeReadMe UI

It can edit markdown and see the result live!

No CMS, nor headless CMS.

Ive been looking for such a thing for long time:

From Readme to SliDev

It’s all about taking makereadme features.

And combining them with SliDev: https://sli.dev/resources/theme-gallery

I mean, letting windsurf do so

Because the ppt templates should not be our focus anymore.

But the content quality!

MakeSlidev

The original features you have them in main

git clone https://github.com/JAlcocerT/makeslidev
make setup
make dev

There you go, the original makeread.me project running locally:

I changed the img to https://cyclingthere.pages.dev/_astro/PXL_20241008_144149173.Cj1pqXWc_1oH9Mo.webp

alt text

See the UI at: http://localhost:3000/

And the swagger api: http://localhost:8080/

But the juice starts at the branch makeslidev:

git branch -a

Conclusions

Similar to AI project docs generation…

I could not resist but to try these IDE’s (Windsurf etc) and their context awareness to generate SliDev PPTs.

And it worked.

So in a way a codex + md editor + slidev should be possible .

Ill come back to SliDev + CMS on a future post.

Expect a v0.2 coming with a simpler way of editing a SliDev PPT!

Alternatives

I got to know along the way about these live markdown editors, that in theory can be plugged into a flask web app.

So as per the learnings of:

This can be done muuuch simpler

HUGO can also be coolInteracting with SSGs and md via Flask