I created iAffiliate's brand and corporate website from the ground up. The work then expanded into iDB, an internal back office where editors manage operator data, offers and assets shared across Noxwin and Casino.online.
View live siteWhat began as a company website became an internal content back office.
The website gave the new brand a clear face for partners and candidates. Behind it, the same operator facts, offers and assets also had to stay consistent across brands and markets. That need became iDB.
First, make the company easy to understand
The site had three jobs: explain the business, build trust with partners and show people why they should join. I shaped one continuous page around proof: the business model, partner logos, work, employee voices, benefits and open roles.
Values designed to feel alive
A shared set of principles became an interactive system for the company website, giving every value its own symbol, voice and responsive state.
The same content was needed in more than one place
iDB is an internal back-office product, not a customer-facing website. Content editors use it to create and maintain operator records, deals, bonuses, payment methods, licences, assets and market rules, then publish consistent information across Noxwin and Casino.online.
Instead of maintaining the same information separately in each affiliate product, iDB acts as the shared source of truth. It connects operators and offers with providers, affiliate websites, rankings and assets while keeping market and publishing context attached to the content.
From content gap to published operator
Editors can spot missing website coverage, update the operator once, and publish consistent content across markets and affiliate products.
Three decisions made iDB easier to use
Dense operational data had to be easy to find, update and reuse.
Keep everything around the operator
Each operator became one record. Related deals, bonuses, software, payments, licences and details sit in predictable tabs, so editors can work from a single context.
Show coverage before opening a record
The operator list shows whether content is available to Noxwin or Casino.online. Editors can spot coverage gaps without opening records one by one.
Organise the detail, don't hide it
The domain needs many fields. Instead of removing useful detail, we grouped it into clear sections such as Casino, Restrictions, Sport, App and Support, using the same control patterns throughout.
Reusable patterns kept the product consistent
The system worked at three levels: foundations set the visual rules, reusable components handled interaction states, and product screens assembled them into workflows. The same patterns had to support dashboards, tables, forms and navigation in both light and dark themes.
A shared foundation for the brand and its content operations
The corporate website launched with one clear story for partners, candidates and employees. For iDB, the outcome was a shared content structure that brought operator details, offers, assets and publishing context into one system.
Editors could see coverage gaps from the operator list and manage related information from a single record instead of navigating disconnected content areas. The reusable UI patterns also gave future workflows a consistent foundation across tables, forms and dashboards.
Formal post-launch metrics were not available, so I evaluate the work through the shipped scope and the workflow improvements built into the product.
- Time needed to create or update an operator
- Time needed to identify missing website coverage
- Content discrepancies between brands and markets
- Completion rate of required operator information
- Editor confidence and usability feedback
