Portals

A portal is a site of yours that lists games from the Filudi catalog and runs them in frames. Players get saves, leaderboards and accounts from the API; you get the catalog, the frame handshake, server keys and statistics. The guides take you from a pending site to a published catalog.

• Start here: the account, a portal in the console, approval, domains.
• Three ways to build a portal: a front on hub-core, a front of your own, a backend with server keys, and how to pick.
• A front on hub-core: fetchCatalog, GameFrame, PlayerClient, tokens.css, the playground.
• A front of your own: the public catalog, the handshake message by message, the game token exchange, frame-ancestors.
• A backend with server keys: keys and scopes, players by your own user id, a token for the browser.
• Listing games: distribution, what you may list, why an add is refused.
• Statistics: what the console shows for a site and what a key reads.
• Going live: publish, the CDN, the approval queue.

filudi.com is built the first way and is the reference for what hub-core does. The API behind every way is in the API reference.