How joperor/kotlin_onboarding_introduction works
Project Type & Purpose
• This is a Kotlin-based, multi-module “course” repository.
• Each top-level folder (AlmostDone, Chat, FeedbackSurvey, Hangman, Introduction, LastPush, MastermindAdvanced, TheFirstDateWithProgramming, WarmUp) is a self-contained lesson/task module.
• The utils module provides shared code (Util.kt, Variable.kt) and resources (images).
• Gradle (Kotlin DSL) orchestrates builds, compilation, testing and packaging across all modules.
Key Components
• Root Build System
– settings.gradle.kts: defines included subprojects
– build.gradle.kts (root): common plugin/dependency versions
– gradle/ & gradlew(.bat): wrapper files
• Lesson Modules (e.g. Hangman, WarmUp, …)
– task-info.yaml, lesson-info.yaml, task.md: metadata for the learning platform
– src/main/kotlin: Kotlin source under package jetbrains.kotlin.course.<module>
– src/test or task/test: unit tests for the module
– build/, out/: Gradle build artifacts
• utils Module
– src/main/kotlin/util: shared helpers
– src/main/resources/images: shared images for lessons
– build.gradle.kts: compiles to utils.jar
Relationships & Interactions
• Root Build System → All Modules
– Orchestrates compileKotlin, compileTestKotlin, test, jar tasks in each subproject.
• Lesson Modules → utils
– Each module declares a compile-time dependency on the utils JAR.
• Lesson Modules ↔ Their Tests
– Source files feed into unit tests located under test directories.
Architectural Patterns
• Monorepo Multi-Module
– Enables independent lesson development & testing.
• Shared Library Pattern
– Common logic & assets centralized in utils.
• Convention-Over-Configuration
– Each lesson module follows the same directory layout (metadata, src, test).