I would start with actually modding it instead of coming up with a name first. Most people who first say they’re going to make a mod don’t. The best thing to do is actually start working on the mod before you say anything, because then you actually have something to show (and it would be easier to come up with a name).
As for actual learning how to mod snap, the best advice is to just read the code and the large comments at the tops of files. There’s no tutorial, so you’re going to have to learn everything yourself. Also, talk about javascript on the forum is generally frowned upon by the snap devs, so there’s not much help you’re going to get here (especially since most users don’t know how the snap source code works).
I absolutely agree with that! There’s so much you can do in snap already, and the actual snap code is much more fun and interesting than making a change to the ui that you’re not even going to use. You also shouldn’t make a snap mod if you barely know anything about javascript and aren’t willing to spend the time to read the source code, because you’d either be relying too much on other people, or you’re just not going to get anywhere. I absolutely encourage people to make cool snap projects, because that’s what snap is for.
What will your Snap! mod add that Snap! can’t already do? If this is purely visual, you should use something called a userscript so that you can use the Snap! server and keep compatibility with future updates.
And if this Snap! mod adds stuff like more blocks, then you can simply make those blocks as custom blocks in vanilla snap! You can even run JS code in snap, if there’s something that can’t be done in vanilla snap