Currently, the README has some old screenshots and links that need to be fixed. I would also reduce the README to the core information to make it more readable.

Further ideas can be discussed below.

One nice feature would be to get a daily challenge and deliver it to the user by mail.

The daily challenge can be fetched from a variety of platforms (CodeWars, LeetCode, Advent of Code, etc.)

While this can be a great addition to have, there are a few things to take into consideration:

• There is no clear way the user would know if he correctly solved the challenge, different platforms use different methods to validate the solutions.
• It seems like there is no official APIs, this would require some web-scraping, which, for a lot of cases, it's against the TOS of the platform (+ it can become difficult to maintain).

We could consider making this a weekly challenge instead. We could manually get, modify and even create the challenge, to make sure it is of good quality. We could even create our own platform, where we can accept user-submitted challenges (but this is beyond our scope right now).

Further ideas can be discussed below.

Configuration section

  mv config.py.template instance/config.py

The file name in the root directory is config.template.py whereas in the Readme.md it is config.py.template.

I will make those changes to README.md and commit those changes.

it is not directing back me to home page

Get a trending repository from the GitHub trending repositories page.

There doesn't seem to be an official API endpoint for this, but scraping doesn't seem to be against GitHub Acceptable Use Policies which states:

You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise:

• Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are open access.
• Archivists may use public information from the Service for archival purposes.

Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler.

Further ideas can be discussed below.

The idea would be to add pre-commit hooks and GitHub actions activated when there are new commits to the master branch, to make sure that the code style is clean and consistent.
I would add black (for formatting) and isort (for sorting imports).
Any additional plugins/ideas can be discussed below.

The typewriter effect on the home page overflows it's container when it has a long phrase and goes behind the subscribe form. The best way to fix this would probably be to increase the set height of that element or set it to auto.