When I look at Stripe's website, I immediately read: "The new standard in online payments". Ok, they handle online payments, that's really clear.
When I look at Sourcehut, the first thing I read is that Drew DeVault posted: "Announcing the SourceHut project hub". Ok? Is that really the first thing I should know? Then I read further and still have zero idea what the actual tools are until I actually dig deeper.
The whole point of the Stripe website is to make people want to use Stripe. That's the function, and if a lot of form helps with that, the function achieved. And I'm pretty sure the Strips homepage is doing a good job drumming up business considering their success.
SourceHut's site tells you what it does, how it does it, what features you can find in there and a bunch of other things. It is packed with information.
When i want to learn about what something is, i want information about what that something is.
In other words, the value it offers you. How it enables you to achieve what you want to achieve. That's what matters, the technical functionality does not.
I don't care that Nike uses vulcanized rubber and cotton, I care that my friends will think they look cool, and thus make me look cool.
So they focus on communicating that value proposition rather than an info dump about the product.
Sourcehut says "lots of open source mini services that work without JavaScript". Cool, why do I care? Is there a cost saving? Would my devs prefer this? Can it do something other paid services can't? Why should I use it?
This is sales, not engineering.
https://i.imgur.com/kdKK3cY.png
On the left side SourceHut has almost everything you want to know, on the right side Stripe has... a couple of background images, one button to "START NOW" (start what?) and to contact sales (for what?).
Stripe's site is a classic case where form took precedence over function.