There are two versions of Chorus: coupled and headless. Both provide a suite of modern content tools that help organizations publish at scale, but they offer different options for how Chorus behaves on the front-end.
Coupled Chorus combines the front-end that audiences see with the back-end tools that editorial teams use. Although design elements like brand colors and fonts differ on organizations using coupled Chorus, the audience experiences share some consistencies. For instance, link sets always appear at the end of stories in coupled Chorus.
Headless Chorus allows organizations to own the audience-facing experience. They can fully create their own site and front-end based on the content editorial teams produce on Chorus. For instance, link sets could appear anywhere on the story page or not appear at all.
Throughout our documentation, you'll find some information that is specific to coupled or headless Chorus (such as the guide on author profiles). Make sure you're always viewing the version of information that is relevant to your organization.
Organizations using coupled Chorus
- Vox Media networks, including:
- Eater
- Polygon
- SB Nation
- The Verge
- Vox
- The Ringer
- Draft Kings Nation
- The McElroy Family
Organizations using headless Chorus
- The Star Tribune
- Chicago Sun-Times
- Deseret News
- Chalkbeat
- THE CITY