Skip to content

fix: clarify within-collection vs cross-collection link conventions#246

Merged
tuxmea merged 1 commit into
OpenVoxProject:masterfrom
miharp:fix/contributing-link-conventions
May 23, 2026
Merged

fix: clarify within-collection vs cross-collection link conventions#246
tuxmea merged 1 commit into
OpenVoxProject:masterfrom
miharp:fix/contributing-link-conventions

Conversation

@miharp
Copy link
Copy Markdown
Contributor

@miharp miharp commented May 23, 2026

Fixes #245

Summary

Replaces the ambiguous "Use absolute paths when pointing to files from other sections" with explicit guidance that distinguishes two distinct cases:

  • Within a versioned collection (e.g. docs/_openvox_8x/): use relative links (page.html). Absolute /latest/ links silently cross version boundaries when a new major version is added.
  • Across collections (e.g. _openvox_8x/_openvoxdb_8x/): use absolute paths (/openvoxdb/latest/page.html). This matches existing practice throughout the docs.

Also adds the ./page.htmlpage.html preference noted in the issue.

Test plan

  • Review wording for clarity

Closes OpenVoxProject#245

Replace the ambiguous "Use absolute paths when pointing to files from
other sections" with explicit guidance distinguishing:
- Within a versioned collection: use relative links to avoid silently
  crossing version boundaries when a new major version is added
- Across collections: use absolute paths

Signed-off-by: Michael Harp <mike@mikeharp.com>
@miharp miharp requested a review from a team as a code owner May 23, 2026 12:14
@tuxmea tuxmea merged commit 285e5ad into OpenVoxProject:master May 23, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify link conventions in CONTRIBUTING.md for within-collection vs cross-collection links

2 participants