Two snippets both say “sign template.” One already contains the room names. The other is a blank A4 layout. Make the index explain which file to use before someone opens the wrong one and edits it.

Name what goes in and what comes out

In a folder’s index.md, link each entry to its file and give it one line of context. For example, Make signs from an approved room list links to populated-signs.md. Start with a blank A4 sign links to blank-a4.md. Say which input a reader needs and which part they should replace.

- [Make signs from an approved room list](populated-signs.md) — input: room list.
- [Start with a blank A4 sign](blank-a4.md) — input: sign text.

The Markdown index distinguishes a populated sign list from a blank A4 starting template.

Illustrated index. Put the input and expected output beside each link.

Try a task from the index

Ask someone to find a blank A4 layout without opening both files. They should be able to choose blank-a4.md from the label. Open each link from the saved index and confirm it resolves to the intended file. Test again from a copied folder if you plan to send the snippets together.

A reader looking for a blank A4 form selects blank-a4.md directly.

Illustrated navigation check. The label makes sense before the file is opened.

When a snippet changes its inputs or output, update the short index entry along with the file.