Core purpose
A series answers which works belong to the same long-running context, not which books one person grouped together. Each member retains its own identity, source, language, release, and content; the series only establishes an intelligible relationship.
For web novels and light novels, a series can include main stories, sequels, side stories, different generations, and even works with their own platform sources and publication versions.
What is available now
- Create series identities with localized names and summaries.
- Connect books, media, software, and releases to a series.
- View other members from a work.
- Present traceable releases on a series detail page.
- Let communities maintain relationships without rewriting members.
Deliberate first-version boundary
The first version centers on members and release-version relationships; it does not enable content structure for a series. Complex ordering, branches, and interpretation can first be described in posts, avoiding the premature forcing of every series into one tree structure before clear product interactions exist.
Canonical/variant relationships do not remove a variant’s capabilities. Communities can prioritize maintaining the canonical entry’s series, while variants still participate in relationships through the same mechanism and, when needed, refer to works related to the canonical entry.
In development
Real cases will determine the needed structure for formal order, branches, derivative series, and cross-media series. Until then, relationships remain simple, explainable, and free of false guarantees.
Relationships and boundaries
A series is not a release, collection, tag, or content catalogue. Releases describe an occurrence, collections express user organization, tags classify, and content structure orders content.