Comment by Someone

That’s not funny; it’s good use of the most prominent part of the site.

A site (re)design starts with determining who’s your audience, and what you want to tell them.

These sites will want to serve both existing and new developers.

What they want to tell them will be different for the two groups, but the existing ones won’t be chased away by a short description aimed at newcomers, but newcomers can easily turn away by the lack of such a description.

As to what to put in the description: it sort-of is an advert, so you often don’t exactly say what you are, but more what you want to be.

https://www.swift.org is a clear example. They definitely want to tell everybody that Swift is multiplatform, giving cloud services, command line tools and embedded development more prominence than iOS apps.

I think they do that particularly well, much better than this ruby site (https://www.ruby-lang.org/en/)

For example, on the swift site, they claim ‘embedded’. If you click on that, you get examples for various platforms such as Raspberry Pi and STM32 (https://www.swift.org/get-started/embedded/). That allows you to verify that claim.

In contrast, this Ruby site makes claims such as 'Easy to write, easy to read. Natural syntax like spoken language’, 'Do more with less code', but it’s not easy for users to check whether that’s true.