Sample: One-file experiments with MDX

Sample content: this MDX entry demonstrates that the collection accepts both Markdown and MDX.

Small experiments often begin as an explanation with one moving part. Keeping the prose and the component in one MDX file makes the boundary obvious: the article supplies context; the component supplies the thing to touch.

A useful limit

The sample rule is simple: if an experiment needs application state, its own navigation, or more than one focused interaction, it graduates out of the article and into the experiments archive.

An embedded component should remain understandable when JavaScript is unavailable. The static rendering explains its state, while the client-side enhancement adds only the interaction.

Why keep the failed ones?

An archive is more useful when it records what did not become a product. A short note about the constraint that stopped an idea can save more time than a polished demo with no history.