I wanted the actual odds
In Classic WoW, you level a profession by crafting. Each craft has a chance to raise your skill by a point, and the game colours every recipe by that chance: orange always gives a point, yellow usually does, green rarely does and grey never does. As your skill rises, each recipe works its way from orange to grey.
The colours hide the odds. Through yellow and green the chance falls a little with every point of skill, from certain at the start of yellow to nothing at grey, so two yellow recipes can be very different bets. Materials cost gold, and auction house prices move. I wanted to see which recipe was worth making, and what levelling would cost.
I was playing Classic WoW myself, and the Burning Crusade release gave me a deadline. I wanted the tool live while people were levelling their professions.
From odds to gold
You picked a recipe and a range of skill, and Professions.gg worked out how many crafts it would take on average, from the chance at every point in that range. It allowed for the races that get a bonus in a profession, which moves the colours. Each profession had a recommended route, recipe by recipe, and you could follow it or pick your own.
Then it priced those crafts, using auction house prices from NexusHub for your realm and faction, or for the whole of Europe or the US. Each item used a seven-day average weighted by how many were listed, or the latest scan. Vendor items used the vendor price, a reagent you could craft yourself could be costed from its own materials, and anything you already had could be left out. What you made could be sold, so some routes showed a profit.
The data was the work
I needed every recipe in a usable shape: 1,266 in Classic alone, each with its reagents, where it's taught and the skill levels where it changes colour. My Puppeteer scraper for Wowhead kept tripping over cookie popups, slow pages and race conditions, so I moved it to Apify for its request queue and retries. The data still had holes, like missing reagents and colour thresholds out of order. Clean-up scripts checked and patched it before it went into PostgreSQL.
Item details, like vendor prices and whether an item could be traded, came from NexusHub's open-source item database. I got to know its creator and contributed to it myself, to keep it working for Professions.gg.
Every recipe and profession had its own page, built ahead of time from the database and listed in a sitemap, so a search for a recipe could land straight on it. Any view could be shared, because your skill level, the recipe and the range you'd picked all lived in the address.
One codebase ran Classic and Burning Crusade Classic, and later Wrath of the Lich King. Each was a separate deployment on its own subdomain, with its own recipes, skill cap and theme.
StackNext.js (Pages Router), TypeScript, PostgreSQL, Tailwind, Prisma, Vercel, Apify
Then people turned up
I posted it to Reddit and about 20,000 people used it on the first day. It wasn't built for that much traffic, and I spent the day keeping it online. I'd put the database and the server in different regions, a mistake I should have caught long before launch. Caching as much as I could at Vercel's edge kept it up, and then I moved the database next to the server. About half the visitors were on phones, and the mobile layout needed work too. Real users found both problems before I did.
Professions.gg is retired
I stopped maintaining the site when NexusHub, which supplied the live auction house prices, shut down. Without those prices, the most useful part of the tool was gone. I don't plan to bring it back for later expansions or servers.
I've left the old database dump below. If you want to remake it for a later Classic release, please do. I'd try an in-game addon that reads prices from an existing auction house addon, though I haven't tested that.