Most sites "for Go developers" are really for search engines. A wall of
libraries nobody vetted, release notes copied from go.dev a week late, a
playground that's really just an ad for something else. None of that is
particularly useful once you've been writing Go for more than a weekend.
Golangy is an attempt at the opposite: a small set of things that are actually useful, kept current, with an opinion attached.
The release tracker. Every Go release, what actually changed, and whether it's worth an unscheduled upgrade. Security releases are called out, not buried in a changelog.
The directory. Not an index of every package on pkg.go.dev — a shortlist of what's worth reaching for, organized by the problem you're solving, with a sentence of real judgment instead of a copied tagline.
The playground. Paste a snippet, run it, see the output. No account, no local toolchain, nothing to install.
The blog. Notes on writing Go well — the parts of the standard library that don't get enough attention, tooling that's worth your time, patterns that hold up once a codebase gets big.
This is a scaffold as much as a launch — the release and directory data you're seeing is seed content, and there's plenty of room for more here.