FS
Loading work / Загружаю работы...
Interactive lore archiveIn Development
Reaper WRLD
A large story universe turned into dossiers, factions, relationship maps and an archive that makes the lore usable.
Project metrics
Measured outcomes
20Team scalecreative production
AtlasCore interfacerelationship mapping
FactionsSystem layerfamilies, zones, bonds
2Archive surfacesinteractive map and dossiers
Stack / tags
Interactive lore archive
A large story universe turned into dossiers, factions, relationship maps and an archive that makes the lore usable.
Next.jsTypeScriptNarrative SystemsWorldbuildingGame Designlore archiverelationship atlasworldbuildinginteractive database
Case frame
How the project was run.
Active production period / archived as portfolio case
20 people
Reaper WRLD takes raw worldbuilding and gives it structure: characters become dossiers, factions become readable groups, relationships become map logic, and archive assets stop living as disconnected files. My role covered narrative department direction, game design and the interface logic needed to make the universe navigable.
Production material
Selected frames and assets.
Screens, illustrations and UI surfaces pulled from the actual work.
Reaper dossier
The archive now has dedicated interfaces.
The case explains my role and the outcome. The map and dossiers open as standalone product surfaces instead of overloading the portfolio page.
relationship edges197
Interactive relationship map
A dedicated full-screen atlas for characters, factions, conflicts, family ties and alliances.
Open the mapcharacter files105
Character dossier archive
A separate dossier interface with biographies, stats, capabilities, equipment and known ties.
Open dossiersDeep dive
Case detail.
What I owned
I organized Reaper WRLD so the world could be read, searched and extended. The work was part narrative direction, part game design, part information architecture.
Core surfaces
- Lore archive
- Relationship atlas
- Character dossiers
- Faction logic
- Relationship mapping
- Media board
- Case assets
- Archive / atlas / dossier structure
Structure I shaped
- Faction zones and group logic
- Character state and dossier framing
- Bonds, rivalries and family ties mapped as relationships
- Media-board grouping for hero art and archive material
- Portfolio shell that keeps the microsite connected to the case
Next product moves
- Expand relationship atlas interactions
- Move lore and changelog into structured data
- Add documentation for the archive model
- Expose build and release signals
- Present Reaper as a serious production record