Guild website, member area and Discord bot for an esports guild
Overview
The complete web presence of the World of Warcraft raiding guild Amaya — not a static page, but a public layer on top of the guild's real data. Roster, raid progress, raid schedule, live streams and applications come straight from the Discord bot, Warcraft Logs, the Blizzard API and Twitch. Plus a member area with a CMS and a custom Discord bot, all from one codebase and one database. The video shows the site with demo content; the current state is live at amaya-guild.de.
The Challenge
Guild websites are usually either an outdated forum or a pretty but lifeless business card: nobody keeps manually updating who is on the team, how far raid progress is or when the next raid happens. Meanwhile, organisation, sign-ups and applications already live in Discord. Amaya needed a presence that looks like an esports team from the outside and still keeps itself up to date.
How We Got There
Built as a monorepo with Next.js 16 (App Router), Prisma and PostgreSQL, shared by the website and the Discord bot (discord.js). The public site reads directly from the same tables the bot maintains: kills and best attempts from Warcraft Logs, boss lists from the Blizzard Dungeon Journal, world ranks from Raider.io, live status via the Twitch API. The hero is an animated guild banner with the name branded into it, while the bosses of the current raid rise in front of it — killed bosses in colour, the progress boss filled up to the best attempt. The application form shows wanted classes and specs live and opens every application as a Discord thread. Login runs through Discord (Auth.js); officers manage news, partners and pages in a custom mini CMS. Hosted on a self-managed VPS with Nginx, PM2, zero-downtime deploys and nightly backups to a second server.
The Outcome
amaya-guild.de has been live since September 2026. The guild only maintains editorial content — everything else updates itself through the bot and APIs. The architecture is multi-tenant from day one: more guilds can launch on the same platform with their own subdomain or domain, without a second deployment.