Post History

Thoughts on hiding challenge sections with expandable details tags

I've recently started experimenting with hiding some of the sections in a challenge, using an expandable `<details>` tag. This seems to have some advantages, but I'm interested to hear how people find this - any good and bad points and general advice on how and where to use this.

I'm asking this in the context of **challenges** specifically, not general Q&A.

I'm not expecting this to lead to rules, just guidance on what people find easiest to use. I'm interested in hearing from people who write answers and people who browse answers, and people who do both. I'm interested in what you find useful on a first reading of a new challenge, and also what you find useful when revisiting a challenge you have already read, to see new answers.

How does this vary on different types of device - small or large screens, landscape or portrait, touchscreen or mouse and keyboard. I don't want to disadvantage one device type.

---

For example, I initially just hid a terminology section, but more recently I'm considering also hiding the input, output, and test cases sections, so only the introductory overview is visible.

# Partially hidden example

A brief introductory overview of what the challenge is about.

<details><summary>Terminology</summary>
The terms used in a particular field; nomenclature.
</details>

## Input
- The data provided to your code
- Specific details

## Output
- The data produced by your code
- Specific details

## Test cases
Test cases are in the format `input : output`

```text
A : apple
B : banana
C : citrus
```

# Fully hidden example

A brief introductory overview of what the challenge is about.

<details><summary>Terminology</summary>
The terms used in a particular field; nomenclature.
</details>

<details><summary>Input</summary>

- The data provided to your code
- Specific details
</details>

<details><summary>Output</summary>

- The data produced by your code
- Specific details
</details>

<details><summary>Test cases</summary>
Test cases are in the format <code>input : output</code>

```text
A : apple
B : banana
C : citrus
```
</details>