Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Pewiz/ulagos360/llms.txt

Use this file to discover all available pages before exploring further.

A space is the fundamental unit of ULagos 360°. Every physical location that tutors track during the open-day event — from an Aula Magna to a taller workshop to a tutor-led campus tour group — is modeled as a space object with a category, a current status, and optional metadata such as capacity, supervisor, or assigned establishment. The full catalog of spaces is declared in src/constants/spaces.js and loaded into Zustand at startup if no persisted state already exists.

Space Categories

ULagos 360° organises spaces into five categories defined in the SPACE_TYPES constant.

bienvenida

Welcome rooms where arriving student groups receive their initial orientation. Includes large venues like the Aula Magna as well as smaller classrooms such as Sala 202 and Video Conferencia. Capacity values help tutors decide whether to redirect groups.

coffee

Coffee-break areas where groups rest between activities. Includes the Hall Principal, Casino, and dedicated Salas de Estudio. These spaces follow the same arrival-based lifecycle as bienvenida rooms.

campus_tour

Individual stops along the campus tour route — from the Turbina Eólica and FabLab to the laboratories, sports facilities, and health-sciences buildings. A tour group passes through these stops sequentially.

talleres

Degree-programme workshops run by supervisors in fixed locations. Each taller entry in SPACES_DATA carries a location (e.g. "Sala 101") and a supervisor name. These spaces have a session-based lifecycle: they start, run their course, and finish.

tours_en_curso

Active campus-tour groups, one entry per tutor leading a group. Each entry records the establishment (school) the visiting group belongs to. Like talleres, these follow the session-based lifecycle rather than an occupancy-based one.

Space Statuses

All seven status values are defined in the SPACE_STATUS constant. Not every status applies to every category — see the lifecycle section below for which path each category follows.
StatusMeaning
disponibleThe space is free and ready to receive a group. This is the default initial state for every space.
ocupadoA group is currently inside the space. Typically set for bienvenida, coffee, and campus_tour stops.
reservadoThe space has been claimed for an incoming group but the group has not yet arrived.
en_caminoA group is on its way to this space. Serves as an intermediate “heads-up” state before ocupado.
mantenimientoThe space is temporarily out of service. Can be applied to any category when a room becomes unavailable.
en_cursoA session is actively running. Used exclusively for talleres and tours_en_curso.
terminadoThe session has concluded. The space is cooling down before being reset to disponible.

Status Lifecycle

The lifecycle a space follows depends on its category. There are two distinct flows.

Bienvenida · Coffee · Campus Tour

These spaces track physical group occupancy: a group arrives, occupies the space, then leaves.
1

disponible

Space is empty and accepting groups. Tutors can claim it for an incoming group.
2

en_camino

A group has been assigned and is walking toward this space. Other tutors see it is about to be occupied.
3

ocupado

The group is inside. The space is fully in use; no new group should be directed here.
4

disponible

The group has departed. The space resets and is ready for the next group.

Talleres · Tours en Curso

These spaces represent scheduled sessions with a clear start and end rather than a flow-through occupancy model.
1

disponible

The session has not started. The taller or tour group is standing by.
2

en_curso

The session is actively running. The supervisor (for talleres) or tutor (for tours_en_curso) marks it live.
3

terminado

The session has finished. The space enters a concluded state before being manually reset.
4

disponible

Reset for the next session or the end of the day.
The mantenimiento status can interrupt any lifecycle at any point. A tutor with access can apply it when a room becomes unavailable, and clear it back to disponible once the issue is resolved.

Space Object Fields

When a space is initialised from SPACES_DATA and stored in Zustand, it carries the following fields:
FieldTypeDescription
idstringUnique identifier (e.g. "aula-magna", "tour-tutor-3"). Sourced from SPACES_DATA.
namestringHuman-readable display name shown in the UI (e.g. "Aula Magna", "Campus Tour - Karoll").
capacitynumber | undefinedMaximum number of people the space can hold. Not all spaces define this field.
statusstringCurrent status value from SPACE_STATUS. Defaults to "disponible" at initialisation.
occupiedBystring | nullName of the tutor or group currently occupying the space. Cleared on disponible.
reservedBystring | nullName of the tutor who reserved or is bringing a group. Set on reservado or en_camino.
lastUpdatestringISO 8601 timestamp of the most recent status change. Used for conflict resolution.
updatedBystring | nullDisplay name of the tutor who made the last change.
categorystringOne of the five SPACE_TYPES values, assigned during initialisation.
supervisorstring | undefinedSupervisor name for talleres entries (e.g. "Josefa - Tyaret").
locationstring | undefinedPhysical room or building for talleres entries (e.g. "Sala 101").
establishmentstring | undefinedVisiting school for tours_en_curso entries (e.g. "Liceo Industrial").
The authoritative list of all spaces — including every campus-tour stop, taller, and active tour group — lives in src/constants/spaces.js inside the SPACES_DATA object. Adding or renaming a space there is sufficient; Zustand will materialise the new entry with status: "disponible" on the next fresh load.

Build docs developers (and LLMs) love