Simplify the documentation

[monolithed]

First of all, I want to say thank you, guys, for your hard work!

Now, let me explain why I'm writing this text. Initially, for my projects, I chose Next.js because it seemed like an industry standard, and everyone I asked had already used it for their projects. I really liked how well-structured their documentation was, and within a day, I was able to create a couple of pages for my new project. However, when it came to optimizing image loading, compressing styles, eliminating unnecessary requests, and speeding up rendering, I found that Next.js is not suitable for production use at all. It gave me the feeling that the project was abandoned. There are over 2.5k open issues, and critical problems that require immediate attention have been hanging around for years.

For example, I had to invest my own time to write an alternative to the Image component because the original implementation automatically compresses images and doesn't allow me to set srcset with the desired proportions. They seem to think they know better how users' interface designs should look, even though that's not the framework's job.
Recently, I discovered that many styles are duplicated three times, and this bug has been around for three years. And when I deployed my project to production, I saw that the page loading speed was at least 2.7 seconds, even though I have purely static content.
To my surprise, I started looking for an alternative to Next.js and came across your comparative article. I am very interested in your project, but after reading the documentation, I couldn't conduct a comparative analysis of the features I need. The examples contain a lot of visual noise with Tailwind, Prisma, server code, and magical routing (this part is probably ok, I just haven’t figured it out yet because it’s unusual.).

I would like to request that you make the documentation simpler and more geared towards a quick start with examples of how to add Ant Design, generate favicons, add image previews and use a static content, so that it resembles an alternative to Next.js because right now, I can't even make a comparison.

Thank you.