Physical form vs technology layer
Connector vs protocol guides
A connector name answers a physical-interface question. A protocol, standard version, bus mode, network service or charging mode answers a different implementation question. These focused guides keep those layers separate for the atlas’s highest-confusion topics.
USB-C vs USB, USB4 and Thunderbolt
Separate the USB-C physical connector from USB generations, USB4 and Thunderbolt technology labels.
Open guide →HDMI connector type vs HDMI version
Keep HDMI Type-A, Mini and Micro connector forms separate from HDMI specification-version capability.
Open guide →DisplayPort connector form vs DisplayPort version
Separate full-size and Mini DisplayPort connector identification from link-version and implementation capability.
Open guide →RJ45 / 8P8C vs Ethernet and PoE
Use the 8P8C physical form as an identification clue, then verify Ethernet service, rate and power behavior separately.
Open guide →M8 / M12 coding vs network service
Treat A-, B-, D-, X- and L-coding as physical-interface distinctions rather than a complete statement of network or power behavior.
Open guide →SD card form vs capacity and bus labels
Keep full-size SD and microSD physical form separate from capacity classes and bus-interface terminology.
Open guide →PCIe connector form vs PCI Express implementation
Distinguish PCIe card-edge and cabled physical forms from lane count, generation and exact system support.
Open guide →Open the compact connector-vs-protocol table →
These discovery surfaces route and reorganize facts already represented in the atlas. They do not add electrical ratings, universal pinouts, measured tolerances, exact-device support, wiring approval or an end-to-end compatibility result.