wrolpi/app/public/index.html

<!DOCTYPE html>
<html lang="en" style="height: 100%">
<head>
    <meta charset="utf-8"/>
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"/>
    <meta name="theme-color" content="#000000"/>
    <meta
            name="description"
            content="The WROLPI webapp"
    />
    <link rel="icon" href="%PUBLIC_URL%/favicon.ico"/>
    <link rel="apple-touch-icon" sizes="180x180" href="%PUBLIC_URL%/apple-touch-icon.png">
    <link rel="icon" type="image/png" sizes="32x32" href="%PUBLIC_URL%/favicon-32x32.png">
    <link rel="icon" type="image/png" sizes="16x16" href="%PUBLIC_URL%/favicon-16x16.png">
    <link rel="mask-icon" href="%PUBLIC_URL%/safari-pinned-tab.svg" color="#5bbad5">
    <!--
      manifest.json provides metadata used when your web app is installed on a
      user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/
    -->
    <link rel="manifest" href="%PUBLIC_URL%/manifest.json"/>
    <!--
      Notice the use of %PUBLIC_URL% in the tags above.
      It will be replaced with the URL of the `public` folder during the build.
      Only files inside the `public` folder can be referenced from the HTML.

      Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
      work correctly both with client-side routing and a non-root public URL.
      Learn how to configure a non-root public URL by running `npm run build`.
    -->
    <title>WROLPi: Create your own off-grid library</title>
    <script>
        /*
          Stamp the saved theme, and the media filter it resolves to, on <html> before first
          paint.  ThemeProvider sets the same attributes once React mounts, but the bundle can
          take a while to arrive over a hotspot — without this the page would paint in the wrong
          theme first, and in night mode a flash of unfiltered thumbnails would cost the user the
          dark adaptation the theme exists to protect.

          Keep the storage keys, theme names, and filter defaults in sync with
          src/themes/names.ts.
        */
        (function () {
            var theme = 'light';
            var saved = null;
            // Only the storage read can throw (blocked cookies/storage).  Keep the try
            // around just that, so a device that prefers dark still gets dark.
            try {
                saved = localStorage.getItem('color-scheme');
            } catch (e) {
                saved = null;
            }
            if (saved === 'light' || saved === 'dark' || saved === 'night' || saved === 'amber') {
                theme = saved;
            } else if (window.matchMedia && window.matchMedia('(prefers-color-scheme: dark)').matches) {
                // `system`, unset, or written by an older version.
                theme = 'dark';
            }
            document.documentElement.setAttribute('data-theme', theme);

            // Which filter each theme uses, and whether it applies unless the user says otherwise.
            var filters = {night: 'night-red', amber: 'amber-mono'};
            var defaults = {night: true, amber: false};
            if (filters[theme]) {
                var enabled = defaults[theme];
                try {
                    var overrides = JSON.parse(localStorage.getItem('media-filter') || '{}');
                    if (typeof overrides[theme] === 'boolean') {
                        enabled = overrides[theme];
                    }
                } catch (e) {
                    // Blocked storage or malformed JSON: fall back to the theme's default.
                }
                if (enabled) {
                    document.documentElement.setAttribute('data-media-filter', filters[theme]);
                }
            }
        })();
    </script>
</head>
<body>
<noscript>You need to enable JavaScript to run this app.</noscript>
<div id="root"></div>
<!--
  This HTML file is a template.
  If you open it directly in the browser, you will see an empty page.

  You can add webfonts, meta tags, or analytics to this file.
  The build step will place the bundled scripts into the <body> tag.

  To begin the development, run `npm start` or `yarn start`.
  To create a production bundle, use `npm run build` or `yarn build`.
-->
</body>
</html>