This is a good point if we were selling physical goods and limited by the amount of information we can convey on a screen but we aren't. I'd honestly include t

This is a good point if we were selling physical goods and limited by the amount of information we can convey on a screen but we aren't. I'd honestly include things like the what and why as critical to documentation. Most libraries, tools, and tech in general are bad at documentation. It's an active choice to omit discussing these things when they should obviously be included but writing good copy is hard. IDK seems like a good thing to invest in especially if you want your tool to become a dominate player instead of an encroaching tangent. While there are separate pages for the why and comparisons for vite (but it's only comparing itself to other bleeding edge tools rather than popular ones like webpack, browserify, gulp, grunt) they should be snippets of these sections on the front page. Right now there are 6 title cards of with wasted space with very little information. Compare this with playwright's home page you and immediately know why you want to use the tool: https://playwright.dev/ https://playwright.dev/ For a personal taste thing, I'm not really a fan of these open source tools creating homepages similar to as you would see for various startups/products. My mind immediately goes "oh paid tool, oh well." They do say it's free in a lovely medium size text that doesn't standout much and is beyond the fold.