# Portable docs lab

This fictional handoff shows why keeping a Markdown folder together matters. Start with [the project overview](docs/overview.md), then follow its [decision](docs/local-files-decision.md). The [diagram](assets/reading-path.svg) is a local SVG. No code or installer is included.

## Try three changes

1. Copy the entire folder to a new location. Its relative links still point within the copy.
2. Move only `docs/overview.md` elsewhere. Its link to `../assets/reading-path.svg` no longer points to the original asset.
3. Rename `assets/reading-path.svg` without updating the Markdown. The image reference becomes stale.

These are path-resolution examples, not a benchmark of an application. The intentionally broken link in `broken/example.md` is labelled and should not be treated as a package error.
