Neon-ranked play by RAMGIULIA LLC

Gulia

A visual-first online game arena where squads climb ladders, organizers launch seasons, and every match feels like a broadcast-ready final.

6competitive formats designed for solo players, squads, creators, and invitational events
2language surfaces built from one shared product system for English and Chinese audiences
5public OneHub endpoints integrated for auth, contact, content, settings, and subscriptions
100%Workers-ready architecture with server-side backend forwarding and locale-aware routes

Game-first platform

Competition that looks fast, feels sharp, and keeps the scoreboard honest.

Gulia is shaped for online competitive games: quick entry, readable stakes, live season context, and a strong visual identity that makes victory feel public.

Ranked ladders

Persistent seasonal ladders give players a clear climb, clean division logic, and visible pressure near promotion lines.

Tournament rooms

Organizers can frame bracket nights, special cups, invitational finals, and community scrims as distinct competitive moments.

Squad clashes

Teams get shared identity, coordinated entry, and a social layer around repeat rivalry.

Creator showdowns

Influencers and streamers can turn challenges into watchable mini-events with score context already built in.

Fair-play guardrails

Rules, account signals, and report paths sit close to the match surface, reducing friction when integrity matters.

Spectator energy

Bright status language, trophy cues, and matchup pacing make the site feel like a live gaming venue.

Arena engine

From lobby spark to trophy flash, the flow is built around momentum.

The homepage uses the visual grammar of the reference image: angular shields, cyan and magenta light, gold victory cues, and dense game-console details.

Match readiness

Players see clear states for queue, registration, verification, and entry so the next action never feels buried.

Live dispatches

The content module pulls published entries from OneHub when they exist, with honest loading, empty, error, and rate-limit states.

Community signals

Guilds, crews, and recurring rivals are treated as part of the competitive loop rather than decoration.

Policy proximity

Terms, privacy, and acceptable use pages are first-class routes linked from account creation and the footer.

Prize rhythm

Season, bracket, and leaderboard modules use trophy language without implying unconfigured cash payouts.

Localization core

Every visible string is stored in locale messages so the English and Chinese site stay structurally aligned.

Season loop

A complete competitive arc without waiting for a separate event microsite.

Gulia presents the whole run of play: arrival, qualification, bracket pressure, finals, and the community aftermath that keeps players returning.

01

Ignite the queue

Players enter through account pages that support email or phone, then move toward ranked play, scrims, or tournament registration.

02

Seed the bracket

Formats can be framed for qualifiers, elimination rounds, round-robin tests, or creator-hosted showdowns.

03

Resolve results

The site language keeps win states, dispute expectations, and fair-play policies near the competitive surface.

04

Carry the story

Published dispatches, newsletters, and community spotlights can turn results into ongoing editorial content.

Runtime operations

Public configuration and data capture are wired for a real backend.

The site uses server-side route handlers for OneHub requests, keeping site context on the server while the UI handles loading and failure states gracefully.

Settings reader

Public settings can change without a new deployment, making the site ready for support channels, region text, feature flags, or live notices.

Contact intake

Partnership and tournament inquiries post to the OneHub contact endpoint with source URL context preserved.

Subscriber loop

The newsletter form submits to the idempotent subscriber endpoint with game and tournament tags.

OpenAPI content

Live dispatch slots stay connected to OneHub content.

If the backend publishes Gulia dispatches, they render here. If not, the page reports the empty state instead of pretending the data exists.

Loading

Checking live dispatches

The site is contacting OneHub for published Gulia content.

Loading

Checking live dispatches

The site is contacting OneHub for published Gulia content.

Loading

Checking live dispatches

The site is contacting OneHub for published Gulia content.

Community energy

Players need more than a match list; they need a place that remembers rivalry.

Gulia gives squads, creators, and returning competitors a branded home for challenges, recaps, and future seasonal announcements.

Guild identity

Teams can rally around a shared competitive identity and see themselves in the public rhythm of the platform.

Creator hooks

Showdowns can be packaged for streams, highlight clips, and recurring challenge formats.

Support routes

Account help, policy questions, and event inquiries route through visible support and contact channels.

Partnership lane

Bring a game, season, sponsor, or community event into the arena.

The contact form is backed by the provided OpenAPI contract and forwards directly to OneHub, including name, email, phone, company, topic, message, and source URL.

Backed by OneHub contact intake.

Quick read

The public site is ready for launch conversations.

Is Gulia only a tournament site?

No. Tournaments are one surface; the broader product is an online competitive platform for ranked play, squads, creator events, and ongoing community seasons.

Does registration support phone and email?

Yes. Login and registration both provide a controlled email or phone switch, and the submitted payload follows the backend contract.

Can the homepage show backend content?

Yes. The dispatch and settings modules read from public OneHub endpoints and show honest empty or error states when no data is configured.

Is it deployable on Cloudflare Workers?

The project includes OpenNext Cloudflare configuration, a Workers wrangler file, and scripts for build and dry-run deployment validation.