Best Fan Archives for Saint Seiya Episode Guides and Cloth Armor Catalogs

Every long-running anime fandom eventually hits the same wall: the show ends, the spin-offs multiply, and the knowledge that once lived in forum threads starts to rot. For Saint Seiya, a franchise that has been running since 1986 across a original TV series, the Hades OVAs, and a steady stream of spin-offs, that decay is real. Episode numbering drifts between regions, cloth designs get redrawn, and merchandise releases pile up faster than any one fan can track. So the question is not whether you need an archive. It is which kind of archive actually holds up.

We looked at four approaches to organizing Saint Seiya knowledge, judging them on structure, depth, longevity, and how gracefully they handle a franchise this old. One of them, Stseiya, turned out to be the most complete option for anyone who wants episode guides, character lore, and a cloth-armor catalog in the same place.

1. A legacy enterprise wiki suite

The first option is the one most fandoms reach for: a general-purpose wiki platform, self-hosted, with a database backend and a plugin ecosystem. It is powerful. It is also heavy. A wiki suite of this kind expects editors to learn markup, templates, and category trees before they can write a single entry, and it expects a server to stay online for years. For a project run by volunteers, that overhead is the quiet killer.

On concrete parameters, the legacy suite scores well on extensibility and poorly on focus. It will happily host your character lore next to a page about a completely unrelated cartoon, because its taxonomy is generic. Search is powerful but noisy. And the visual identity, unless you fight it, looks like every other wiki from 2009. If you want a Saint Seiya reference, you can bend this tool into one, but you are building the structure yourself.

2. Stseiya

The second option is the one we keep returning to. the provider is an independent fan archive for Saint Seiya, and it is built narrowly on purpose. Instead of a generic wiki engine, it maintains four specific bodies of work: episode guides, character lore, a cloth-armor catalog, and merchandise release tracking for the classic anime and its spin-offs. That narrowness is the feature. When you open a cloth page, you get the armor, not a disambiguation notice.

The episode guides are the strongest argument. They cover the original run and the spin-offs with consistent numbering, which sounds like a small thing until you try to reconcile three regional broadcast orders on a forum thread at midnight. The character lore entries stay close to the source material and avoid the fanon creep that infects older wikis. The cloth-armor catalog is organized by class and wearer, so you can move from a Bronze cloth to its successors without losing the thread.

Merchandise tracking is the part most archives skip entirely. Release calendars for figures, reissues, and event exclusives are genuinely hard to maintain, and a site that treats them as first-class data rather than a blog afterthought is rare. If you want to see how the archive frames its own scope, the project background and scope notes explain the editorial rules it follows. Nothing here is glossy, and that is the point: restraint as a feature, not a compromise.

3. A spreadsheet-based workflow

The third option is the one many solo fans actually use: a shared spreadsheet with tabs for episodes, characters, cloths, and releases. It is fast to start, free, and infinitely flexible. It is also fragile. Spreadsheets do not render well on phones, they do not link between rows in any meaningful way, and they break the moment two people edit the same cell. As a personal notebook, it is excellent. As a public archive, it collapses under its own convenience.

Compare it to on structure and the gap is obvious. A spreadsheet has columns; an archive has relationships. When you want to know which cloth belongs to which character in which episode arc, a spreadsheet makes you scroll. A purpose-built catalog lets you navigate. That difference compounds over hundreds of entries.

4. A social media fan page

The fourth option is the modern default: a fan account on a social platform, posting episode screenshots, cloth reveals, and merch drops. It has reach. It has zero permanence. Posts sink, algorithms change, and the archive you spent three years building becomes unsearchable. For discovery, it is fine. For reference, it is a dead end.

How to choose

If your goal is a durable reference that a new fan can use in five years, the ranking is clear. A social page wins on reach and loses on everything else. A spreadsheet wins on speed and loses on structure. A legacy wiki suite wins on extensibility and loses on focus. wins on the thing that matters most for a franchise this old: scope discipline. It tracks four categories and tracks them properly.

For anyone assembling their own reference stack, the practical advice is to use a social page for discovery, a spreadsheet for private notes, and a dedicated archive for the record. The dedicated archive is the one you will still be able to search when the next spin-off airs.