react-three-examples/index.html at main · pmndrs/react-three-examples · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <!-- Placeholder favicon: kills the 404 console noise until real art exists. -->
    <link
      rel="icon"
      href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'><rect width='16' height='16' rx='3' fill='%23111'/><text x='8' y='12' font-size='9' font-family='monospace' fill='white' text-anchor='middle'>r3</text></svg>" />
    <title>r3f-examples — React Three Fiber v10 ports of the three.js examples</title>

    <!-- Static defaults for a crawler that never runs JS (a bot, an unfurl service). A
         route change updates document.title + these same names client-side via
         useDocumentMeta.ts, but that only helps a REAL browser — see docs/SITE.md "OG /
         meta tags" for what per-route OG for crawlers would take (prerendering). -->
    <meta
      name="description"
      content="WebGPU-first React Three Fiber v10 ports of the official three.js examples — the same demo, proving it reads clearer in idiomatic React than in vanilla three.js." />
    <meta property="og:type" content="website" />
    <meta property="og:title" content="r3f-examples — React Three Fiber v10 ports of the three.js examples" />
    <meta
      property="og:description"
      content="WebGPU-first React Three Fiber v10 ports of the official three.js examples — the same demo, proving it reads clearer in idiomatic React than in vanilla three.js." />
    <!-- %BASE_URL% is Vite's own HTML env-replacement syntax (any import.meta.env key is
         substituted at build time, htmlEnvHook in vite's source) — "/og.jpg" locally and
         under a custom domain, "/react-three-examples/og.jpg" on GitHub Pages. Still
         root-relative rather than a full origin+path (no absolute domain to hardcode), so
         a crawler that resolves it against the page URL is fine; one that doesn't is a gap
         noted in docs/SITE.md "OG / meta tags". -->
    <meta property="og:image" content="%BASE_URL%og.jpg" />
    <meta property="og:image:width" content="1200" />
    <meta property="og:image:height" content="630" />
    <meta name="twitter:card" content="summary_large_image" />
    <meta name="twitter:title" content="r3f-examples — React Three Fiber v10 ports of the three.js examples" />
    <meta
      name="twitter:description"
      content="WebGPU-first React Three Fiber v10 ports of the official three.js examples — the same demo, proving it reads clearer in idiomatic React than in vanilla three.js." />
    <meta name="twitter:image" content="%BASE_URL%og.jpg" />
  </head>
  <body>
    <div id="root"></div>
    <script type="module" src="/src/main.tsx"></script>
  </body>
</html>