For content creators›Overview›Core Concepts and Terms

1.4Core Concepts and Terms

These are the terms you will see throughout this guide. They are grouped by what they describe: the spaces and people in Thidal, the content you create, and how work is run and reviewed.

1.4.1Spaces and People

Department
A self-contained workspace for an institution, training programme, or organisation. Each department has its own questions, cohorts, assessments, and data. Data and content are not shared between departments.
Admin
A department role that manages the department, its settings, users, and team.
Contributor
A department role that creates and runs content but does not manage the department, its settings, or team.
Cohort
A named group of learners who are given access to specific learning pathways or activities.

1.4.2Content

Question Bank
The shared, reusable store of coding questions. A question can be used in multiple learning pathways and assessments.
Question type
Defines where a question can be used: Assessment, Pathway, or Both. Question pickers automatically filter questions based on their type.
Solution type
Defines the kind of solution a question expects: Problem for classic test-case coding, Web Project for multi-file HTML, CSS, and JavaScript projects, or Java Project for projects with multiple Java files.
Test case
An input and expected output pair used to evaluate a submission. The first test case is visible to learners as a sample. Other test cases can remain hidden and are used when the learner submits the solution.
Difficulty
The level assigned to a question: Easy, Medium, or Hard.
Global question
A question that is shared across all departments and marked with a global question badge.
Pathway
An ordered, concept-tagged sequence of questions that learners work through. A pathway can include optional release and due dates.
Assessment
A timed set of questions that learners complete through a shared link in Battleground.

1.4.3Running and Reviewing

Arena
The learner's workspace during an assessment. It includes the problem list, code editor, live countdown, and progress information.
Run and Submit
Run checks the code against the visible sample case and provides quick feedback. Submit evaluates the code against all test cases and records the result.
Solution Playback
A keystroke-level replay that shows how a submission was written. Trainers can use it to review a submission after it has been completed.