Editorial Policy
Effective date: 2025-01-01
Purpose & Standards
DockLynx exists to deliver verified, scenario‑first docking guidance. Our content is evidence‑based, transparent, and replicable. We avoid marketing hype and publish the data needed to reproduce results.
Independence & Integrity
- Recommendations are brand‑agnostic and scenario‑driven.
- Manufacturers cannot pay for placement, influence rankings, or preview conclusions.
- When vendors provide samples, we disclose it and apply the same tests and criteria as retail units.
Methodology Summary
We run cross‑platform stress tests across Mac, Windows, and Linux. We validate display pipelines (Alt Mode, MST/DSC, DisplayLink), measure sustained power delivery, Ethernet throughput, thermals, sleep/wake stability, and firmware behavior. Each review includes plain‑language matrices, Port Map diagrams, and setup flows.
Evidence & Replicability
- We list exact test rigs: laptop model/CPU/GPU, OS build, dock firmware, driver versions, cables, and monitors.
- Pass/fail criteria are defined per scenario (e.g., dual 4K60 with ≥100W sustained PD and stable link post‑sleep).
- Known limitations and edge cases are called out.
Corrections & Updates
If we discover an error, we correct the page and add a dated changelog note. Firmware/driver changes that impact results trigger retests and updates to our matrices.
Conflicts of Interest
Editors and contributors must disclose any financial interests or prior employment with vendors covered and recuse themselves where needed.
Affiliate Disclosure & Monetization
Some articles include affiliate links. If you use these links, we may earn a commission at no extra cost to you. Affiliate status does not affect test design, data collection, or recommendations. Ads, if present, will be clearly labeled and kept separate from test content.
Community Input
We welcome reproducible reader reports. When user findings meet our evidence bar (versioned specs, logs, repeatable steps), we incorporate them with attribution.
Contact the Editors
Questions or concerns about our coverage? Email [email protected] with the URL, your evidence, and suggested correction.