I Built a Wiki for Task Bar Hero After Getting Tired of Looking Up Item Drops
While playing Task Bar Hero, I kept running into the same questions:
- Where does this item drop?
- Is it tradable?
- Does it actually sell on Steam?
- Is farming it worth the time?
The information existed, but it was scattered across Discord messages, Steam discussions, and spreadsheets.
So I decided to build a dedicated wiki and tool site.
The Goal
I wanted a single place where players could:
- search any item
- see drop locations
- check Steam Market availability
- compare farming routes
- access item-specific tools
The project eventually became:
https://taskbarhero.nanobananas.me
Building the Item Database
The first challenge was structuring item data.
Every item page needed:
- rarity
- level
- category
- drop sources
- market status
- related items
Instead of writing pages manually, I generated them from a structured dataset and created static routes with Next.js.
Example item page:
/items/minor-ruby
Creating a Drop Finder
The most-used feature became the Drop Finder.
Instead of navigating through multiple pages, players can search an item directly and immediately see:
- where it drops
- which stages contain it
- farming options
This ended up being much faster than searching through community posts.
Handling Steam Market Pages
One unexpected SEO issue involved Steam Market data.
Some items are technically tradable but have no active market listings.
Initially I generated market pages for every item.
The result:
- thousands of low-value pages
- thin content
- poor index quality
To solve this, I split pages into two categories:
Indexed
Items with actual Steam Market data.
Noindexed
Items without meaningful market information.
Users can still access those pages, but search engines are instructed not to index them.
This significantly improved the quality of pages submitted through the sitemap.
Multilingual SEO
The site also supports multiple languages.
One challenge was that English uses the root path:
/items/minor-ruby
while other languages use locale prefixes:
/zh/items/minor-ruby
To avoid duplicate-content issues I implemented:
- canonical URLs
- hreflang alternates
- locale-specific sitemaps
This keeps language versions connected while allowing search engines to understand the preferred URL structure.
Tech Stack
- Next.js
- TypeScript
- Static Generation
- XML Sitemap Generation
- Structured Data
- Canonical URLs
- Hreflang Alternates
What I'd Improve Next
The current roadmap includes:
- better farming calculators
- richer item relationships
- drop-rate analytics
- player-contributed data
The project started as a small utility for myself, but it's becoming a useful resource for other players as well.
If you play Task Bar Hero, I'd love to hear what information you find hardest to locate in-game.
That meant internal links, sitemap URLs, canonical URLs, and language switching all had to follow the same rule.
Why I Built It
Game wiki pages are useful, but I wanted something more decision-focused:
“Where should I farm this?”
“Does it have a market price?”
“What drops it?”
“What item should I compare it with?”
So the site is more like a database plus a set of small tools.
What I’m Improving Next
Next things I want to improve:
better farming route recommendations
more market confidence signals
cleaner guide pages
more item comparison tools
better visual summaries for new players
If you play Task Bar Hero or like game-data tools, feedback is welcome.
Main site:
👉 https://taskbarhero.nanobananas.me/?utm_source=devto&utm_medium=post&utm_campaign=500uv_week
Top comments (0)