The problem
A growing mod collection was spread across individual repositories and distribution platforms. Users needed one place to understand what exists, what changed, and where to get each project.
Back to Work
Case study · Open-source catalog
RGX Mods
One release and discovery surface for a growing family of game mods.
Mod CatalogReactOpen SourceRepository SyncRelease TrackingResponsive UI
Live catalog
The solution
cranberriestudios built a unified catalog that models each package, synchronizes repository context, and provides dedicated ecosystem and mod pages with search and filtering.
The result
The RGX collection can be explored as a coherent product family while individual repositories remain the source for releases, code, and project-specific documentation.
Live WoW catalog
Measurable project facts
Counts taken from the current catalog and route implementation.
26
Catalog packages
The current public catalog data contains 26 mod packages with dedicated metadata and routes.
24
WoW addons
World of Warcraft is the largest catalog lane, with its own browse and discovery experience.
2
Diablo II mods
Diablo II projects are separated into their own catalog lane instead of being mixed into WoW results.
26
Dedicated mod pages
The application includes a specialized page implementation for every current catalog package.
What we implemented
01
Repository-backed catalog
Release versions, activity metadata, documentation, and source links are synchronized from external repositories into a public catalog.
02
Game-specific discovery
World of Warcraft and Diablo II have distinct catalog surfaces, visual treatment, and browse paths.
03
Search and category filters
Visitors can search the catalog and narrow WoW addons by category without leaving the page.
04
Semantic mod routes
Each package has a stable /mod/... route that can surface overview, release, source, and documentation context.
05
README and release presentation
Repository documentation is brought into the mod experience instead of forcing users to reconstruct project context across sites.
06
Static-first fallback
Bundled catalog data lets the public surface render even when the live API layer is unavailable.
Implementation
The public experience combines a static catalog baseline with repository/API synchronization. That keeps browsing resilient while letting release and project metadata stay tied to source repositories.
React
JavaScript
Custom design system
GitHub/GitLab repositories
Static catalog fallback
API synchronization
Semantic routes
Cloudflare delivery
What changed
- A collection of separate mod repositories became one searchable public destination.
- Release and repository information can be synchronized into a consistent catalog model instead of being rewritten by hand.
- Visitors can move from ecosystem → package → documentation/source/download without losing project context.
- The terminal-inspired interface gives a large technical catalog a recognizable visual system while retaining mobile browse paths.
Managing a growing project catalog?
We can turn distributed repositories and release data into a branded discovery experience without replacing the systems that already own the source.