Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Daniel-Stojanovski/finkiopendesk/llms.txt

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

The FinkiOpenDesk forum organizes community discussion around academic courses at FCSE. Every subject has a dedicated discussion space where students can ask questions, share notes, and post replies in threaded comment chains. Subjects are further divided into channels — focused sub-topics that keep conversations organized within a single course. The forum landing page presents a searchable grid of all subjects. You can narrow the list using filters before opening any discussion.

​
Search and filter

FilterValuesDescription
queryfree textMatches subject name
programe.g. SIIS, SEIS, KIAcademic program the subject belongs to
formatsubject format tagLecture, lab, or combined
hardnessL1, L2, L3Difficulty level (L1 = foundational, L3 = advanced)
semesterTypeW, SWinter or summer semester
Filters are applied client-side after the initial data load, and the search query uses a 1-second debounce before triggering a new API request.

​
Discussion workflow

1

Browse subjects

Open the Forum page. All subjects load automatically. Use the search bar to type a course name or apply program, format, hardness, or semester filters to narrow the list.
2

Open a subject discussion

Click any subject card to enter its discussion view. The page header shows the subject name and description. Comments posted directly here belong to the subject-level discussion.
3

Browse channels

The channel sidebar lists all active channels for the subject. Each channel targets a specific sub-topic. Select a channel to switch into its focused discussion thread.
4

Read and post comments

Scroll through the threaded comment list. To reply to a specific comment, select it — your new comment is attached as a child reply. Submit with the comment input at the bottom of the view.

​
Discussion views

The subject discussion is the primary thread for a course. It loads when you open a subject card from the forum.What you see:
  • Subject name and description header
  • Full comment thread for the subject, including parent and child (reply) comments
  • A channel sidebar listing active channels for that subject
  • A comment input fixed at the bottom; selecting an existing comment activates reply mode
API endpoints used:
GET /api/subjects/sid/{subjectId}
GET /api/subjects/channels/sid/{subjectId}/active
GET /api/comments/sid/{subjectId}
POST /api/comments/create

​
Comment structure

Each comment has the following shape: 
interface CommentDto {
  commentId: string;
  user: UserDto;
  type: "subject" | "profession" | "channel";
  content: string;
  subjectId?: string | null;
  professionId?: string | null;
  channelId?: string | null;
  parentId?: string | null;  // set when replying to another comment
}
A parentId links a reply to its parent comment. The UI renders these as nested threads. Top-level comments have no parentId.

​
Responsive behavior

The forum adapts to screen size. On tablet-sized viewports, the channel sidebar is hidden by default and can be opened with the diagram icon in the discussion header. On mobile, the main discussion sidebar (subject list) is also collapsed and accessed via a menu button.

Build docs developers (and LLMs) love

Get started for freeTalk to us