Some documentation files apply to both Concept Exercises and Practice Exercises. These cross-exercise files are located within the track's exercises/shared/.docs directory:
debug.md: explains how a student that is coding in the browser can still do "debugging" (optional)help.md: contains track-specific instructions on how to get help (required)representations.md: explains which normalizations are applied to a solution to create its representation (optional)tests.md: contains track-specific instructions on how to run the tests (required)The Presentation document describes how these files are used to present content to the student.
debug.md
Purpose: Explain how a student that is coding in the browser can still do "debugging"
Presence: Optional
The in-browser editor does not have any built-in debugging support. If the track's test runner supports capturing console output, the student can still do some form of "debugging" and this document explains how to do that.
The contents of this file are only shown in the online editor; the CLI will ignore this file.
# Debug
To help with debugging, you can use the fact that any [console output](https://www.programiz.com/csharp-programming/basic-input-output) will be shown in the test results window. You can write to the console using:
```csharp
Console.WriteLine("Debug message");
```
help.md
Purpose: Explain how a student can get help
Presence: Required
Describe how a student can get help, specifically for this track (not Exercism-wide).
The contents of this file are only used by the CLI, which includes it in the HELP.md file.
The instructions should be short and to the point.
You could link to resources like Gitter channels, forums or mailing lists: whatever can help a student become unstuck.
The links in this document can overlap with those in docs/LEARNING.md or docs/RESOURCES.md.
This document should not link to Exercism-wide (track-agnostic) help resources, as those resources will automatically be included in the HELP.md file.
# Help
To get help if you're having trouble, you can use one of the following resources:
- [Kotlin Documentation](https://kotlinlang.org/docs/reference/)
- [Kotlin Forums](https://discuss.kotlinlang.org/)
- [Kotlin Slack Channel](https://kotlinlang.slack.com/): [get invite here](https://slack.kotlinlang.org/)
- [Stack Overflow](https://stackoverflow.com/questions/tagged/kotlin)
- [Kotlin Subreddit](https://www.reddit.com/r/kotlin)
representations.md
Purpose: Explains which normalizations are applied to a solution to create its representation
Presence: Optional
When a track has implemented a representer, each submitted solution will have a representation created for it.
This document should list all the normalizations the representer applies to a solution.
This helps a mentor while adding representation comments.
# Representations
The representer applies the following normalizations:
- All comments are removed
- All import declarations are removed
- The code is formatted
- Identifiers are normalized to a placeholder value
If your track has a docs/REPRESENTER_NORMALIZATIONS.md file, we recommend to link the normalizations to the corresponding section in that file.
tests.md
Purpose: Contains track-specific instructions on how to run the tests
Presence: Required
Describe how to run the tests for this particular exercise.
The contents of this file are only used by the CLI, which includes it in the HELP.md file.
The instructions should be short and to the point.
The docs/TESTS.md file can contain a more verbose description on how to run tests.
# Tests
To run the tests, run the command `dotnet test` from within the exercise directory.
Note: this is not yet implemented
Exercises can overwrite the track-specific files by creating an identically named file in the exercise's .docs directory (e.g. .docs/debug.md). This should only rarely be needed (if at all).