Clicking on the channel links on https://www.manim.community/awesome/ links to https://youtube.com/channel/undefined which is wrong.
cc @OwenSamuel @prism0x

With 1Password/for-open-source#451 merged, Manim is now in the Open Source program of 1Password. Their logo should be added to our website.

Resources: https://1password.com/press/#press-kit

The website with the documentation is not correct:
https://www.manim.community/plugin/manim-slides/

This is how it appears:

You need to scroll right to see the images.

None of these links work, if you click nothing happens.

Tested on Mac OS Sonoma 14.1.1 with Safari, Chrome.

Currently there is no preview Deployment available for PR and this can be fixed by adding either vercel or Netlify which provides the support for it.

IMO, we want users to see the examples before the links to install. The installation links could also just be condensed into an "install manim" button.

In safari the favicon appears to be blue coloured.

This is a non issue on the documentation's website.

The 404 page font has very low contrast when in dark mode making it difficult to read.

I think the 404 page should also still have the menu and footer for one click navigation rather than having to click home before going to the intended page.

Add instructions on how to build the site and what frameworks it's built on to README.

I think it would be great to know how many people viewed the website. Using google analytics may be an option, but I would like to respect the browser do not track feature in which case google analytics isn't loaded. This is much similar to how it's done in RTD(https://assets.readthedocs.org/static/javascript/readthedocs-analytics.js).

I think a Twitter section displaying tweets @manim_community tweeted in the front page would be great. What do you guys think?

The current look makes the page feel a bit cramped, also it might look better if there were just three elements to be centered.

Maybe there's solution that just removing it, but the current implementation feels off imo.

Currently the site is using Gatsby 3 and it would be better to migrate to version 4.
See https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/ and it should be fairly easy to do.

As in

I'm gonna revert 60ed9a3 until I find what going on.

I think as the library grows and as we acquire new contributors and users, the landing page should also reflect that by adding better examples.

Adding some docs on adding examples would be nice 😄.

If not included "self.wait()" in the construct method no video is generated, as no animarion is lauched, and an error is arisen.

Regardless of whether we go with Transifex or Lokalise for our internationalization efforts, we'd need to mention them on the main page of our website to be provided free service. Ideally, this should only be visible after scrolling down, regardless of what device you're using to view the site.

This would be needed for SEO, I guess. In the future, we may have extra pages in which case we would need a sitemap.

Aspect ratio looks a little weird here. Pasted the image somewhere else and it looked fine.

Details about the logo: https://www.nuclino.com/press

Clicking on: https://www.manim.community > Learn More > About Manim makes this link

https://docs.manim.community/en/stable/installation/versions.html

which goes to:

        \          SORRY            /
         \                         /
          \    This page does     /
           ]   not exist yet.    [    ,'|
           ]                     [   /  |
           ]___               ___[ ,'   |
           ]  ]\             /[  [ |:   |
           ]  ] \           / [  [ |:   |
           ]  ]  ]         [  [  [ |:   |
           ]  ]  ]__     __[  [  [ |:   |
           ]  ]  ] ]\ _ /[ [  [  [ |:   |
           ]  ]  ] ] (#) [ [  [  [ :===='
           ]  ]  ]_].nHn.[_[  [  [
           ]  ]  ]  HHHHH. [  [  [
           ]  ] /   `HH("N  \ [  [
           ]__]/     HHH  "  \[__[
           ]         NNN         [
           ]         N/"         [
           ]         N H         [
          /          N            \
         /           q,            \
        /                           \

As Crowdin does not provide a publicly viewable list of translators for Manim, we can consider using their API to create one on the website.

Rewriting code so that it fits in one line is fairly inconvenient.

Ideally supports rendering markdown.

Currently the site honestly looks totally boring. If I told people about this amazing tool called Manim and they went to the "landing page" they were like: "uuhhh pretty static site - but can you show me what it can do?". And I agree! There should be videos, screenshots, code snippets, etc. to showcase what Manim is capable of and how easy it is use it!

.... yeah just my two cents.