Cards hub
Card pages turn official previews into reusable evergreen entry points
The first cards hub stays intentionally small. It exists to prove the site can support card-level entity pages without pretending the full database is already public.
Cluster
Cards
Live pages
2
Source style
Official previews
Next layer
Broader card library
Why the cards hub should start small
Card coverage is where a search-first resource site can explode in size. That is exactly why this hub should begin with a tiny, controlled sample set.
The goal is not to fake a complete database on day one. The goal is to prove:
- the route rules are stable
- the card fields are useful
- the site can separate official preview facts from editorial interpretation
What the first card pages are testing
The first two live card pages are built around cards that Mega Crit publicly previewed with readable text.
That makes them good template tests because the site can publish:
- the official name
- the currently visible card text
- a cautious explanation of why the card matters
without pretending every surrounding combo and matchup is already solved.
Why cards should connect outward, not stay isolated
A card page becomes more useful when it acts as a bridge:
- back to the cards hub
- sideways to mechanics
- outward to class and build pages that give the card context
That is the pattern this first hub is trying to lock in.
First card pages
Two sample card entities built from official previews
These pages are enough to test field design, route stability, and internal linking before the card library grows wider.
entity
Slay the Spire 2 Thrumming Hatchet
See what is officially shown about Thrumming Hatchet in Slay the Spire 2 and keep the card explanation grounded in the public preview text.
entity
Slay the Spire 2 Rolling Boulder
See what is officially shown about Rolling Boulder in Slay the Spire 2 and why it makes sense as an early scaling-oriented card page.
Next clicks
The two best adjacent clusters after cards
Card pages usually make more sense once the user has either a broader mechanics lens or a relic-level follow-up route.
FAQ
Why this cluster starts with a tiny sample set
A small first card hub is enough to prove the system and keep the wording disciplined.
Why launch a cards hub with only a few pages first?
Because card pages only work at scale if the site proves the entity template, route rules, and linking logic before trying to flood the cluster.
Should card pages claim every previewed card is confirmed in the live build?
No. A first card page should separate what was officially shown from what is confirmed to be playable today.
Which card pages are live first?
The first public set focuses on Thrumming Hatchet and Rolling Boulder as officially previewed sample entries.