Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Taykl12/Classify/llms.txt

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

The Classify Calendar provides a unified view of every scheduled event across all projects accessible to the logged-in user. Events represent milestones, review dates, submission deadlines, or any other time-bound marker relevant to a project. Because the calendar is scoped to your accessible projects automatically, students and professors each see only the events that are relevant to them.

Viewing the Calendar

Navigate to Calendar in the sidebar to open the full calendar view. Events are displayed on their scheduled date and colour-coded by priority. Clicking an event shows the event title, description, associated project name, and priority. Events are returned from GET /api/calendar/events ordered by date ascending, so the earliest upcoming event always appears first.

Creating a Calendar Event

Events are attached to a specific project and require at minimum a title and an event date.
{
  "projectId": "proj_abc123",
  "title": "Mid-term Review Presentation",
  "description": "Live demo of the sensor dashboard to the professor panel. Prepare slides and a working prototype.",
  "priority": "Alta",
  "eventDate": "2024-11-20"
}
Classify calls the create_evento_calendario database function to persist the event and link it to the project’s calendar.
1

Open the Calendar page

Click Calendar in the main sidebar navigation.
2

Select a date or click New Event

Click on a day in the calendar grid to pre-fill the date, or click New Event to open the creation form.
3

Fill in the event details

Enter the event title, select the associated project, choose a priority, and confirm the date. An optional description can provide context for team members.
4

Save the event

Click Save. The event appears on the calendar immediately and is visible to all members of the associated project.

Event Priority Levels

Calendar events share the same priority scale as tasks.

Alta

High-priority event — a submission deadline or formal review. Highlighted prominently on the calendar.

Media

Standard milestone or team checkpoint. The default priority for new events.

Baja

Informational marker or low-stakes reminder with no hard consequence.

Event Fields Reference

projectId
string
required
The ID of the project this event is associated with. The user must have access to that project.
title
string
required
Short label for the event displayed on the calendar grid.
description
string
Optional longer description shown in the event detail popover.
priority
string
default:"Media"
One of Alta, Media, or Baja.
eventDate
string
required
The scheduled date in YYYY-MM-DD format. Times are not tracked — events are day-level markers.

Event Response Shape

When you fetch events, each entry in the response array includes the following fields.
id
string
Unique identifier for the calendar event, sourced from eventos_calendario.
title
string
The event’s display title.
description
string
Optional description text.
date
string
The event date in YYYY-MM-DD format.
projectName
string
Human-readable name of the associated project, resolved by the API automatically.
projectId
string
The ID of the associated project for client-side navigation or filtering.
type
string
Always "event" — used by the client to distinguish calendar entries from other item types.
priority
string
The event priority: Alta, Media, or Baja.

Project Scoping

The calendar only surfaces events from projects you can access — either as an owner, a member, or an assigned professor.
Professors see events from all projects assigned to them, giving them an aggregated timeline of upcoming deliverables across their entire cohort without switching between individual project views.
Use Alta priority for hard deadlines like final submissions or external demos so they stand out visually against routine milestones on busy calendar months.

Build docs developers (and LLMs) love