LAIC 2025

There are two main types of users, and they look for very different things.

Competitors need clarity around the tournament itself:

• formats and structure
• what’s allowed and what isn’t
• what to bring, and how to participate

Spectators, on the other hand, are navigating the event:

• schedules
• activities
• what’s happening and where

Both depend on the same platform. The challenge was organizing that information so each group can find what they need quickly, without getting in each other’s way.

The structure came first. Instead of designing pages individually, the site was built around content types:

• competitor information
• event schedules
• registration flows
• general event content

Each one follows its own logic, but they all connect through a shared system.

The Competitor Info pages are the clearest example. They’re dense, but predictable. Once you understand one, you understand all of them.

That consistency removes friction, especially when users are looking for specific details.

The visual direction follows the seasonal identity defined for the tournament, but it’s applied with restraint.

In content-heavy sections, visual elements step back. Structure does the work:

• clear headings
• modular sections
• lists instead of long paragraphs

The focus is on making information easy to scan, not on adding visual noise.

The site was built using Astro, with static generation for each language (English, Spanish, Portuguese).

Content is structured in JSON files, which keeps everything predictable and easier to maintain across languages.

This becomes especially important in more complex components like Side Events, where the system supports:

• search
• filtering by category
• day-based navigation
• multiple view modes

All of this runs without a reactive framework. State and rendering are handled with vanilla JavaScript, keeping the implementation lightweight and controlled.

The site includes dark mode and a reduce motion option, both persisted as user preferences, allowing the experience to adapt without affecting the overall structure.

The result is a platform that works in real conditions.

Competitors can quickly check tournament-specific information without digging through unrelated content. Spectators can understand what’s happening and navigate the event more easily.

The structure stays consistent across languages, and the system can be reused for future editions without needing to rebuild from scratch.

The key was not to simplify the event content, but to organize it around the different ways competitors, spectators, and organizers use the platform.