Internal Links for a Historical macOS Compatibility Archive
Connect build records, component tests, and diagnostics without overstating compatibility. Place links beside the claims they support and audit version boundaries.
“Ethernet worked under OS X Lion” is a thin claim in a motherboard report if the controller ID and tested driver live in a separate network diagnosis. Put a contextual link beside that claim, and readers can check the evidence without turning the motherboard report into a networking manual.
Internal links connect pages on the same site, but they also signal what those pages have in common. In a historical macOS compatibility archive, that might be a component, an OS version, a symptom, or a procedure. A link placed where that connection matters does more work than a loose list of related posts at the bottom.
Start with the decision the reader is making
Before adding a link, ask what the reader needs to decide. In a motherboard report, it may be whether the exact board revision was tested. In a boot-failure diagnosis, it may be whether the failure occurs at graphics handoff or because the system volume cannot be read. The pages might mention the same hardware, but they serve different questions.
Keep a small inventory for each substantial page: its main subject, the macOS or OS X versions covered, the hardware revision if known, and the decision the page helps readers make. Note what it does not resolve, too. Those gaps often suggest useful links. A tested build record may point to a procedure for changing a bootloader setting; the procedure should point back only if that build record provides evidence relevant to the change.
Sharing a component name is not enough. A Radeon result under one macOS release says nothing by itself about another. Make the boundary clear in the linking sentence: “For a separate test of this card under High Sierra, consult the High Sierra graphics report.” If the destination has no such test, do not link to it.
Build paths from broad records to specific evidence
An archive may contain complete build records, individual component reports, bounded procedures, and symptom-led diagnostics. Each offers a different kind of answer. Link between them when the destination answers a question the current page raises, rather than because both pages happen to mention a GPU or bootloader.
Use overview pages as routes, not substitutes for evidence
An overview helps readers find reports by platform or OS version. It should not suggest that every listed part was tested in the same build. Group links by a useful distinction, such as chipset generation, graphics architecture, or OS release, and give them brief qualifications. “Tested sleep and wake” and “controller identified; network speed unverified” tell readers more than article titles alone.
Link from a detailed report back to an overview when comparison would help. Someone assessing an untested motherboard revision might need an index of boards with separately documented revisions. A reader working through a narrow audio fix probably does not need a general platform index.
Join procedures to their prerequisites and risks
Place prerequisite links before the steps that depend on them. Before changing a bootloader configuration, filesystem layout, kext set, or firmware setting, readers need the applicable version limits, a verified backup, and any necessary compatibility checks. A warning after the change comes too late.
A migration plan that branches on filesystem support, for example, can point to the HFS+ versus APFS guide organized by macOS version before discussing disk changes. That guide helps readers identify the relevant filesystem discussion; it does not prove a particular build can boot either format. Changes to a working installation should start with a restorable backup and a check against the exact OS version and hardware configuration.

Write link text that states the relationship
A good anchor briefly describes what readers will find. “This GPU test under Mojave” works if the destination really documents a Mojave test. The surrounding sentence can say why it matters: the reader may be comparing OS versions, checking a prerequisite, reviewing a test method, or diagnosing a symptom.
Use exact part identifiers when they distinguish reports, but leave out keyword clutter. A controller model and OS version may be essential; a string of every board, bootloader, and symptom on the page rarely is. Do not promise a fix when the destination records only an observation. “Recorded wake behavior on this build” is more accurate than “fix sleep” unless the linked page establishes a general fix.
Link text should still make sense when read outside its paragraph. The MDN guide to creating links recommends text that identifies the destination or action. In a compatibility archive, that means keeping the scope visible: an OS X Lion report is not evidence for High Sierra, and one board revision does not represent every board sold under the same name.
Choose the direction of each link deliberately
Links need not run both ways. A troubleshooting page may cite a component report for its controller identification, while that report has no reason to point to a diagnosis of an unrelated failure. Reciprocal links make sense when the pages genuinely complement each other: one establishes a tested baseline and the other explains a change to that baseline.
It helps to give each proposed link a job:
- Prerequisite: information needed before the current instructions are safe or meaningful.
- Evidence: a test record supporting a specific statement on the current page.
- Alternative path: another diagnosis to consider when a stated condition is absent.
- Comparison: a report on another version or revision, labeled as a separate result.
- Continuation: a possible next task, without suggesting every reader must do it.
If a proposed link has no clear role, reread both pages. The shared component may be incidental. Linking every post to a popular article can also make that article appear authoritative on subjects it does not cover.
Handle version boundaries in the linking sentence
Version boundaries matter in historical compatibility records. Graphics driver support can differ between releases; filesystem choices can depend on installer behavior; and a controller found on one board revision may be missing from another. The linking sentence should stop readers from treating a dated result as universal.
Suppose a verified OS X build report mentions a later upgrade attempt. If that attempt was inconclusive, say so: “The later upgrade log records a boot failure after the graphics handoff; it does not establish support for this GPU.” Readers can inspect the evidence without mistaking an attempted upgrade for a compatibility result.
Risk needs the same care. Do not present firmware flashing as a routine next step for a graphics problem. If it is relevant to the discussion, frame the link around limits and hazards: the guide to when legacy GPU VBIOS flashing may help—and when it will not. Readers should verify the exact card and preserve recoverable backups before any change. A link is not an endorsement of modifying firmware.
Place links where they resolve uncertainty
Put a link beside the statement that prompts the question, not only in a list below the article. In a boot diagnostic, that could be the step asking whether the volume is HFS+ or APFS. In a motherboard report, it could follow the onboard Ethernet controller ID. A build record might link from the table row naming the tested OS release.
One link at the first substantive mention is usually enough. Repeating it on every occurrence interrupts the page. A later link earns its place if it has a different purpose—for example, the first cites the tested baseline, while the second leads to a separate recovery procedure.
Tables need context as well. A linked “Pass” or “Yes” cell does not reveal whether the destination contains test conditions, a workaround, or instructions. Put the qualification in the cell or adjacent prose, particularly if testing covered only basic output rather than sleep, acceleration, or multiple displays.

Audit the network as the archive changes
A working URL can still lead to misleading evidence. When new testing narrows a compatibility report’s conclusion, check the pages that cite it. If the report now separates two hardware revisions, update links whose anchors or surrounding sentences previously treated them as one.
A short audit sheet can track the relationships that matter without imposing a rigid hierarchy:
| Current page | Destination’s role | Scope to verify | Action |
|---|---|---|---|
| Tested build record | Network diagnostic evidence | Controller ID and OS release match | Keep or qualify link |
| Upgrade procedure | Filesystem prerequisite | Starting and target versions stated | Place before disk changes |
| GPU report | Different-version comparison | Separate results remain distinct | Label version in anchor |
Look for accurate reports with few or no incoming links. Find a page where their evidence resolves a real uncertainty, and link from that point. If there is no natural place to link, the report’s scope may be unclear. A more precise title and opening description may need to come first.
When merging or retiring a post, point existing links to the page that preserves its evidence. Redirecting a detailed test report to a category page avoids an error but strands anyone checking the cited observation. If the observation is no longer available, remove or revise the claim that relied on it.
Check the reader’s path, not just the link count
Test one realistic route through the archive. Start with a build record: can you identify the tested motherboard revision, find what happened to Ethernet under the stated OS release, and reach the diagnostic evidence? At each stop, check that the destination delivers what the anchor promises. If a category page leaves you guessing, clarify or move the link in the originating page.
A small archive can be reviewed by hand. Record the current page, the sentence containing the link, the destination title, and the fact it is meant to support. Then check that the destination still states that fact with the same OS and hardware qualifications. A broken-link checker cannot catch a valid URL attached to the wrong claim.
On the next report you edit, take a statement such as “onboard audio was tested after sleep” and find the test note behind it. If the note names a different codec, board revision, or OS release, qualify the statement rather than linking it. If the details match, put a descriptive link beside the claim so the evidence is one step away.
