-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prep README and Changelog for v0.1.0 #27
Comments
also, for "example usage" - it would be nice to at least link to this: ("manim-window shortcuts" - an essential part for many use-cases) |
thoughts, where we can also announce it: discord, reddit but only when the major issues are solved |
So we would announce on:
Any other outlets you would consider? @Splines @VladimirFokow what are your twitter handles? |
I don't have a Twitter account, but I might post a video on my YouTube channel. However, I'd like such a video to be more than a sales-pitch and to go a bit more in-depth, so this won't happen in the timeframe you have envisioned and I'm not sure if I even have time for that video ;) I can however create a YouTube post on my channel with a square image advertising the new extension. And on LinkedIn as well. It'd be really nice if you could create such an asset for us to use, e.g. with the VSCode icon in a corner, your cool extension logo in the center and a short title (in the image). As a further idea: let's file in a PR to 3b1b's |
I think we should also include some images in the Readme. Since to be honest: when installing a new extension, I rarely take a too close look on the Readme. I just scroll through it and if images stand out I will see them first. Users should at least remark the |
I've just seen that on the VSCode Discussions, there exists an |
Also make clear which minimal ManimGL version we support. |
The README should include
The Changelog should view v0.1.0 as the "initial release" and list all features that are supported. In a sense, it is the first release under a formal github workflow and the first that is publicly announced.
The text was updated successfully, but these errors were encountered: