We've moved the Evenings docs to evenings.fm/docs

We've rebuilt the Evenings docs and moved them to our own site at evenings.fm/docs. Here's what changed and why we did it.

Why we left GitBook

When we started building Evenings and its API, we reached for whatever let us move quickly. GitBook let us write and host our documentation for free, which mattered a lot to a small team with a product to build. We didn't have to design anything, and we could spend our time on the platform instead. GitBook is a good tool, and we'd still recommend it to any team in the position we were in.

Since then, building our own docs has stopped being the big project it once was. We have better tools now (yes, coding agents helped), and we wanted the docs to feel like the rest of Evenings: the same design, the same voice, and pages we can shape around how stations actually use them.

To be honest with you, there's a business reason too. We're an independent company, and we want people searching for things like how to stream internet radio with OBS to find a guide on our site. Every guide that helps a station that way also brings a few more people to Evenings, which is how we keep growing and keep supporting more stations.

What's in the docs

The docs are grouped by what you're trying to do:

• Start here covers how Evenings works, setting up your station and your first broadcast.
• Guides walk through streaming with OBS, Audio Hijack or BUTT, scheduling live and prerecorded shows, embedding a player on your own site, and more.
• API and API Reference cover API keys and the Events, Tracks and Streams APIs, with real request and response examples.

Run your station your way

We've always wanted stations to be able to build on top of Evenings, not only broadcast through it. You can put your stream in an HTML audio player on your own website, and the Events API lets you show your schedule there too. An API is only as useful as its documentation, so we'll keep the docs current as the platform changes.

Have a look around evenings.fm/docs. If you get stuck on a page, or go looking for a guide that isn't there yet, email contact@evenings.email with what you were trying to do. We read every email, and they shape which guides we write next.