Pixlland for Developers

Publishing architecture

Games should live outside the main platform in versioned builds and dedicated runtime hosting such as R2 or a CDN. The Pixlland page references the game through a safe URL.

Quality requirements

Each game needs to load quickly, respect orientation, declare devices, integrate start/end events, and offer clear controls for players.

Discovery and monetization

Metadata, category, tags, images, videos, ads, and telemetry help the platform discover good games and measure quality without mixing game code into the portal.

Pixlland platform standard

Pixlland public pages use language-specific URLs, self canonicals, full hreflang, structured data, and internal links to connect the home page, categories, games, privacy, Kids, and the developer area. Games stay in a separate runtime, usually through a safe iframe and versioned hosting outside the portal, so the catalog remains fast, crawlable, and easier to approve for search and ads systems.

• Routes such as /br, /en, and /en/g/starfall keep language explicit and indexing clean.
• The platform catalog is separate from game files, which can live on R2 or a CDN.
• Metadata, consent, analytics, and ads belong to the portal without mixing into the game build.
• Developer account pages keep publishing controls away from the public player journey.