1<!doctype html> 2<html lang="en" class="dark"> 3 <head> 4 <meta charset="UTF-8" /> 5 <meta 6 name="viewport" 7 content="width=device-width, initial-scale=1.0, viewport-fit=cover" 8 /> 9 <meta name="mobile-web-app-capable" content="yes" /> 10 <meta name="apple-mobile-web-app-capable" content="yes" /> 11 <meta 12 name="apple-mobile-web-app-status-bar-style" 13 content="black-translucent" 14 /> 15 <meta name="apple-mobile-web-app-title" content="PC Anatomy" /> 16 <meta name="theme-color" content="#15191a" /> 17 <link rel="icon" type="image/png" sizes="96x96" href="/favicon-96.png" /> 18 <link rel="icon" type="image/x-icon" sizes="16x16 32x32 48x48 256x256" href="/favicon.ico" /> 19 <link rel="icon" type="image/svg+xml" sizes="any" href="/favicon.svg" /> 20 <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" /> 21 <link rel="manifest" href="/site.webmanifest" /> 22 <meta 23 name="description" 24 content="Explore a desktop PC in interactive 3D. Take apart the case, motherboard, GPU, CPU, cooling and storage, and learn how computer hardware works." 25 /> 26 <title>PC Anatomy</title> 27 <style> 28 /* 29 The block inside #root is for crawlers that do not run scripts and for 30 visitors without JavaScript. With JavaScript it is dead the moment 31 React mounts and clears #root â but the browser had already painted 32 it, so every load began with a flash of a page nobody was meant to 33 see. Hiding it costs those readers nothing: a crawler that does not 34 run scripts does not apply this stylesheet either, and one that does 35 run them gets the real application. The noscript rule below puts it 36 back for the only visitor who needs it. 37 */ 38 #no-script-intro { 39 display: none; 40 } 41 </style> 42 <noscript> 43 <style> 44 #no-script-intro { 45 display: block; 46 } 47 </style> 48 </noscript> 49 <link rel="canonical" href="https://pc-anatomy.com/" /> 50 <meta name="robots" content="index, follow, max-image-preview:large" /> 51 <meta property="og:type" content="website" /> 52 <meta property="og:site_name" content="PC Anatomy" /> 53 <meta property="og:title" content="PC Anatomy â Explore a Computer in 3D" /> 54 <meta 55 property="og:description" 56 content="Explore a desktop PC in interactive 3D. Take apart the case, motherboard, GPU, CPU, cooling and storage, and learn how computer hardware works." 57 /> 58 <meta property="og:url" content="https://pc-anatomy.com/" /> 59 <meta 60 property="og:image" 61 content="https://pc-anatomy.com/social-preview.png" 62 /> 63 <meta property="og:image:width" content="1200" /> 64 <meta property="og:image:height" content="630" /> 65 <meta 66 property="og:image:alt" 67 content="PC Anatomy: an interactive 3D desktop PC with its motherboard, graphics card and cooling visible." 68 /> 69 <meta name="twitter:card" content="summary_large_image" /> 70 <meta 71 name="twitter:title" 72 content="PC Anatomy â Interactive 3D PC Hardware Explorer" 73 /> 74 <meta 75 name="twitter:description" 76 content="Explore a desktop PC in interactive 3D. Take apart the case, motherboard, GPU, CPU, cooling and storage, and learn how computer hardware works." 77 /> 78 <meta 79 name="twitter:image" 80 content="https://pc-anatomy.com/social-preview.png" 81 /> 82
82<script type="application/ld+json"> 83 { 84 "@context": "https://schema.org", 85 "@graph": [ 86 { 87 "@type": "WebSite", 88 "@id": "https://pc-anatomy.com/#website", 89 "url": "https://pc-anatomy.com/", 90 "name": "PC Anatomy", 91 "description": "Explore a desktop PC in interactive 3D. Take apart the case, motherboard, GPU, CPU, cooling and storage, and learn how computer hardware works.", 92 "inLanguage": "en" 93 }, 94 { 95 "@type": "WebApplication", 96 "@id": "https://pc-anatomy.com/#app", 97 "url": "https://pc-anatomy.com/", 98 "name": "PC Anatomy", 99 "description": "Explore a desktop PC in interactive 3D. Take apart the case, motherboard, GPU, CPU, cooling and storage, and learn how computer hardware works.", 100 "applicationCategory": "EducationalApplication", 101 "operatingSystem": "Any", 102 "isAccessibleForFree": true, 103 "browserRequirements": "Requires JavaScript and WebGL", 104 "image": "https://pc-anatomy.com/social-preview.png", 105 "author": { 106 "@type": "Person", 107 "name": "Yoseph" 108 }, 109 "offers": { 110 "@type": "Offer", 111 "price": "0", 112 "priceCurrency": "USD" 113 }, 114 "featureList": [ 115 "Interactive 3D PC disassembly", 116 "Motherboard and CPU exploration", 117 "RTX 5090 and GPU architecture", 118 "Power supply, cooling and storage exploration" 119 ], 120 "isPartOf": { 121 "@id": "https://pc-anatomy.com/#website" 122 } 123 } 124 ] 125 } 126 </script>
126 127
127<script type="module" crossorigin src="/assets/index-x8EjsJb1.js"></script>
127 128 <link rel="stylesheet" crossorigin href="/assets/index-BRwox9vn.css"> 129 </head> 130 <body> 131 <div id="root"> 132 <main 133 id="no-script-intro" 134 style=" 135 max-width: 760px; 136 margin: 12vh auto; 137 padding: 24px; 138 font-family: system-ui; 139 color: #e4e7e9; 140 background: #15191a; 141 border-radius: 16px; 142 " 143 > 144 <h1>PC Anatomy â Interactive 3D PC Hardware Explorer</h1> 145 <p> 146 Explore a desktop PC in interactive 3D. Take apart the case, 147 motherboard, GPU, CPU, cooling and storage, and learn how computer 148 hardware works. 149 </p> 150 <p> 151 Start with an assembled ATX tower, inspect the motherboard and RTX 152 5090 graphics card, then explore processors, memory, power, cooling 153 and storage. Each component includes explanations and source 154 references. 155 </p> 156 <p> 157 <a href="/guide/index.html" style="color: #a1d9e2" 158 >Learn how PC components work</a 159 > 160 · 161 <a 162 href="https://github.com/Yoosseph/pc-anatomy" 163 style="color: #a1d9e2" 164 >Open-source project</a 165 > 166 </p> 167 <noscript 168 ><p> 169 Enable JavaScript to use the 3D explorer. The hardware guide works 170 without JavaScript. 171 </p></noscript 172 > 173 </main> 174 </div> 175 </body> 176</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.