npm - polkamarkets-js - Versions diffs - 3.1.0 → 3.1.2 - Mend

polkamarkets-js 3.1.0 → 3.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2901) hide show

package/lib/reality-eth-monorepo/packages/website/webroot/doc/faq.md ADDED Viewed

@@ -0,0 +1,47 @@
+[HTML5 Boilerplate homepage](https://html5boilerplate.com/) | [Documentation
+table of contents](TOC.md)
+# Frequently asked questions
+* [Why is the Google Analytics code at the bottom? Google recommends it be
+  placed in the `<head>`.](#why-is-the-google-analytics-code-at-the-bottom-google-recommends-it-be-placed-in-the-head)
+* [How can I integrate Bootstrap with HTML5
+  Boilerplate?](#how-can-i-integrate-bootstrap-with-html5-boilerplate)
+* [Do I need to upgrade my site each time a new version of HTML5 Boilerplate is
+  released?](#do-i-need-to-upgrade-my-site-each-time-a-new-version-of-html5-boilerplate-is-released)
+* [Where can I get help with support
+  questions?](#where-can-i-get-help-with-support-questions)
+---
+### Why is the Google Analytics code at the bottom? Google recommends it be placed in the `<head>`.
+The main advantage of placing it in the `<head>` is that you will track the
+user's `pageview` even if they leave the page before it has been fully loaded.
+Here's a handy quote from [Mathias Bynens](https://mathiasbynens.be/notes/async-analytics-snippet#comment-50) about our placement choice.
+>I should point out that it’s Google — not me — recommending to place this
+script before all other scripts in the document. The only real advantage is to
+catch a pageView call if your page fails to load completely (for example, if
+the user aborts loading, or quickly closes the page, etc.). Personally, I
+wouldn’t count that as a page view, so I actually prefer to place this script
+at the bottom, after all other scripts. This keeps all the scripts together and
+reinforces that scripts at the bottom are the right move. (Usually I
+concatenate and minify all my scripts into one .js file — the GA snippet being
+the suffix.)
+### How can I integrate [Bootstrap](https://getbootstrap.com/) with HTML5 Boilerplate?
+Here's Nicolas Gallagher writing about how [HTML5 Boilerplate and Bootstrap complement each
+other](https://www.quora.com/Is-Bootstrap-a-complement-or-an-alternative-to-HTML5-Boilerplate-or-viceversa/answer/Nicolas-Gallagher).
+### Do I need to upgrade my site each time a new version of HTML5 Boilerplate is released?
+No, same as you don't normally replace the foundation of a house once it
+was built. However, there is nothing stopping you from trying to work in the
+latest changes, but you'll have to assess the costs/benefits of doing so.
+### Where can I get help with support questions?
+Please ask for help on
+[StackOverflow](https://stackoverflow.com/questions/tagged/html5boilerplate).

package/lib/reality-eth-monorepo/packages/website/webroot/doc/html.md ADDED Viewed

@@ -0,0 +1,250 @@
+[HTML5 Boilerplate homepage](https://html5boilerplate.com/) | [Documentation
+table of contents](TOC.md)
+# The HTML
+By default, HTML5 Boilerplate provides two `html` pages:
+* [`index.html`](#indexhtml) - a default HTML skeleton that should form the
+  basis of all pages on your website
+* [`404.html`](#404html) - a placeholder 404 error page
+## `index.html`
+### The `no-js` Class
+The `no-js` class is provided in order to allow you to more easily and
+explicitly add custom styles based on whether JavaScript is disabled
+(`.no-js`) or enabled (`.js`). Using this technique also helps [avoid the
+FOUC](https://www.paulirish.com/2009/avoiding-the-fouc-v3/).
+## Language Attribute
+Please consider specifying the language of your content by adding a [value](https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) to the `lang`
+attribute in the `<html>` as in this example:
+```html
+<html class="no-js" lang="en">
+```
+### The order of the `<title>` and `<meta>` tags
+The order in which the `<title>` and the `<meta>` tags are specified is
+important because:
+1) the charset declaration (`<meta charset="utf-8">`):
+   * must be included completely within the [first 1024 bytes of the
+     document](https://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#charset)
+   * should be specified as early as possible (before any content that could
+     be controlled by an attacker, such as a `<title>` element) in order to
+     avoid a potential [encoding-related security
+     issue](https://code.google.com/p/doctype-mirror/wiki/ArticleUtf7) in
+     Internet Explorer
+2) the meta tag for compatibility mode
+   (`<meta http-equiv="x-ua-compatible" content="ie=edge">`):
+   * [needs to be included before all other tags except for the `<title>` and
+     the other `<meta>`
+     tags](https://msdn.microsoft.com/en-us/library/cc288325.aspx)
+### `x-ua-compatible`
+Internet Explorer 8/9/10 support [document compatibility
+modes](https://msdn.microsoft.com/en-us/library/cc288325.aspx) that affect the
+way webpages are interpreted and displayed. Because of this, even if your site's
+visitor is using, let's say, Internet Explorer 9, it's possible that IE will not
+use the latest rendering engine, and instead, decide to render your page using
+the Internet Explorer 5.5 rendering engine.
+Specifying the `x-ua-compatible` meta tag:
+```html
+<meta http-equiv="x-ua-compatible" content="ie=edge">
+```
+or sending the page with the following HTTP response header
+```
+X-UA-Compatible: IE=edge
+```
+will force Internet Explorer 8/9/10 to render the webpage in the highest
+available mode in [the various cases when it may
+not](https://hsivonen.fi/doctype/#ie8), and therefore, ensure that anyone
+browsing your site is treated to the best possible user experience that
+browser can offer.
+If possible, we recommend that you remove the `meta` tag and send only the
+HTTP response header as the `meta` tag will not always work if your site is
+served on a non-standard port, as Internet Explorer's preference option
+`Display intranet sites in Compatibility View` is checked by default.
+If you are using Apache as your webserver, including the
+[`.htaccess`](https://github.com/h5bp/server-configs-apache) file takes care of
+the HTTP header. If you are using a different server, check out our [other
+server config](https://github.com/h5bp/server-configs).
+Starting with Internet Explorer 11, [document modes are
+deprecated](https://msdn.microsoft.com/library/bg182625.aspx#docmode).
+If your business still relies on older web apps and services that were
+designed for older versions of Internet Explorer, you might want to consider
+enabling [Enterprise Mode](https://blogs.msdn.microsoft.com/ie/2014/04/02/stay-up-to-date-with-enterprise-mode-for-internet-explorer-11/) throughout your company.
+## Meta Description
+The `description` meta tag provides a short description of the page.
+In some situations this description is used as a part of the snippet
+shown in the search results.
+```html
+<meta name="description" content="This is a description">
+```
+## Mobile Viewport
+There are a few different options that you can use with the [`viewport` meta
+tag](https://docs.google.com/present/view?id=dkx3qtm_22dxsrgcf4 "Viewport and
+Media Queries - The Complete Idiot's Guide"). You can find out more in [the
+Apple developer docs](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html).
+HTML5 Boilerplate comes with a simple setup that strikes a good balance for general use cases.
+```html
+<meta name="viewport" content="width=device-width, initial-scale=1">
+```
+## Web App Manifest
+HTML5 Boilerplate includes a simple web app manifest file.
+The web app manifest is a simple JSON file that allows you to control how your
+app appears on a device's home screen, what it looks like when it launches
+in that context and what happens when it is launched. This allows for much greater
+control over the UI of a saved site or web app on a mobile device.
+It's linked to from the HTML as follows:
+```html
+        <link rel="manifest" href="site.webmanifest">
+```
+Our [site.webmanifest](https://github.com/h5bp/html5-boilerplate/blob/master/src/site.webmanifest) contains a very skeletal "app" definition, just to show the basic usage.
+You should fill this file out with [more information about your site or application](https://developer.mozilla.org/en-US/docs/Web/Manifest)
+## Favicons and Touch Icon
+The shortcut icons should be put in the root directory of your site. `favicon.ico`
+is automatically picked up by browsers if it's placed in the root.  HTML5
+Boilerplate comes with a default set of icons (include favicon and one Apple
+Touch Icon) that you can use as a baseline to create your own.
+Please refer to the more detailed description in the [Extend section](extend.md)
+of these docs.
+## The Content Area
+The central part of the boilerplate template is pretty much empty. This is
+intentional, in order to make the boilerplate suitable for both web page and
+web app development.
+### Browser Upgrade Prompt
+The main content area of the boilerplate includes a prompt to install an up to
+date browser for users of IE 8 and lower. If you intended to support IE 8, then you
+should remove the snippet of code.
+## Modernizr
+HTML5 Boilerplate uses a custom build of Modernizr.
+[Modernizr](https://modernizr.com/) is a JavaScript library which adds classes to
+the `html` element based on the results of feature test and which ensures that
+all browsers can make use of HTML5 elements (as it includes the HTML5 Shiv).
+This allows you to target parts of your CSS and JavaScript based on the
+features supported by a browser.
+Starting with version 3 Modernizr can be customized using the [modernizr-config.json](https://github.com/h5bp/html5-boilerplate/blob/master/modernizr-config.json) and the
+[Modernizr command line utility](https://www.npmjs.com/package/modernizr-cli).
+## What About Polyfills?
+If you need to include [polyfills](https://remysharp.com/2010/10/08/what-is-a-polyfill)
+in your project, you must make sure those load before any other JavaScript. If you're
+using some polyfill CDN service, like [cdn.polyfill.io](https://cdn.polyfill.io/),
+just put it before the other scripts in the bottom of the page:
+```html
+    <script src="js/vendor/modernizr-3.6.0.min.js"></script>
+    <script src="https://cdn.polyfill.io/v2/polyfill.min.js"></script>
+    <script src="https://code.jquery.com/jquery-3.3.1.min.js" integrity="sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8=" crossorigin="anonymous"></script>
+    <script>window.jQuery || document.write('<script src="js/vendor/jquery-3.3.1.min.js"><\/script>')</script>
+    <script src="js/plugins.js"></script>
+    <script src="js/main.js"></script>
+</body>
+```
+If you like to just include the polyfills yourself, you could include them in
+`js/plugins.js`. When you have a bunch of polyfills to load in, you could
+also create a `polyfills.js` file in the `js/vendor` directory or include the files
+individually and combine them using a build tool. Always ensure that the polyfills
+are all loaded before any other JavaScript.
+There are some misconceptions about Modernizr and polyfills. It's important
+to understand that Modernizr just handles feature checking, not polyfilling
+itself. The only thing Modernizr does regarding polyfills is that the team
+maintains [a huge list of cross Browser polyfills](https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills).
+### jQuery CDN for jQuery
+The jQuery CDN version of the jQuery JavaScript library is referenced towards
+the bottom of the page. A local fallback of jQuery is included for rare instances
+when the CDN version might not be available, and to facilitate offline
+development.
+The jQuery CDN version was chosen over other potential candidates
+([like Google's Hosted Libraries](https://developers.google.com/speed/libraries/))
+because it's fast ([comparable or faster than Google by some
+measures](https://www.cdnperf.com/#jsdelivr,cdnjs,google,yandex,microsoft,jquery,bootstrapcdn/https/90))
+and, (unlike Google's CDN) is available to China's hundreds of millions of internet users.
+For many years we [chose](https://github.com/h5bp/html5-boilerplate/issues/1191)
+the Google Hosted version over the jQuery CDN because it was available
+over HTTPS (the jQuery CDN was not,) and it offered a better chance of
+hitting the cache lottery owing to the popularity of the Google CDN.
+The first issue is no longer valid and the second is far outweighed by
+being able to serve jQuery to Chinese users.
+While the jQuery CDN is a strong default solution your site or application may
+require a different configuration. Testing your site with services like
+[WebPageTest](https://www.webpagetest.org/) and browser tools like
+[PageSpeed Insights](https://developers.google.com/speed/pagespeed/insights/) will help you examine the real
+world performance of your site and can show where you can optimize your specific
+site or application.
+### Google Universal Analytics Tracking Code
+Finally, an optimized version of the Google Universal Analytics tracking code is
+included. Google recommends that this script be placed at the top of the page.
+Factors to consider: if you place this script at the top of the page, you’ll
+be able to count users who don’t fully load the page, and you’ll incur the max
+number of simultaneous connections of the browser.
+Further information:
+* [Optimizing the Google Universal Analytics
+  Snippet](https://mathiasbynens.be/notes/async-analytics-snippet#universal-analytics)
+* [Introduction to
+  Analytics.js](https://developers.google.com/analytics/devguides/collection/analyticsjs/)
+* [Google Analytics Demos & Tools](https://ga-dev-tools.appspot.com/)
+**N.B.** The Google Universal Analytics snippet is included by default mainly
+because Google Analytics is [currently one of the most popular tracking
+solutions](https://trends.builtwith.com/analytics/Google-Analytics) out there.
+However, its usage isn't set in stone, and you SHOULD consider exploring the
+[alternatives](https://en.wikipedia.org/wiki/List_of_web_analytics_software)
+and use whatever suits your needs best!

package/lib/reality-eth-monorepo/packages/website/webroot/doc/js.md ADDED Viewed

@@ -0,0 +1,36 @@
+[HTML5 Boilerplate homepage](https://html5boilerplate.com/) | [Documentation
+table of contents](TOC.md)
+# The JavaScript
+Information about the default JavaScript included in the project.
+## main.js
+This file can be used to contain or reference your site/app JavaScript code.
+If you're working on something more advanced you might replace this file
+entirely. That's cool.
+## plugins.js
+This file can be used to contain all your plugins, such as jQuery plugins and
+other 3rd party scripts for a simple site.
+One approach is to put jQuery plugins inside of a `(function($){ ...
+})(jQuery);` closure to make sure they're in the jQuery namespace safety
+blanket. Read more about [jQuery plugin
+authoring](https://learn.jquery.com/plugins/#Getting_Started).
+By default the `plugins.js` file contains a small script to avoid `console`
+errors in browsers that lack a `console`. The script will make sure that, if
+a console method isn't available, that method will have the value of empty
+function, thus, preventing the browser from throwing an error.
+## vendor
+This directory can be used to contain all 3rd party library code.
+Minified versions of the latest jQuery and Modernizr libraries are included by
+default. You may wish to create your own [custom Modernizr
+build with the online builder](https://www.modernizr.com/download/) or [command
+line tool](https://modernizr.com/docs#command-line-config).

package/lib/reality-eth-monorepo/packages/website/webroot/doc/misc.md ADDED Viewed

@@ -0,0 +1,173 @@
+[HTML5 Boilerplate homepage](https://html5boilerplate.com/) | [Documentation
+table of contents](TOC.md)
+# Miscellaneous
+* [.gitignore](#gitignore)
+* [.editorconfig](#editorconfig)
+* [Server Configuration](#server-configuration)
+* [robots.txt](#robotstxt)
+* [humans.txt](#humanstxt)
+* [browserconfig.xml](#browserconfigxml)
+--
+## .gitignore
+HTML5 Boilerplate includes a basic project-level `.gitignore`. This should
+primarily be used to avoid certain project-level files and directories from
+being kept under source control. Different development-environments will
+benefit from different collections of ignores.
+OS-specific and editor-specific files should be ignored using a "global
+ignore" that applies to all repositories on your system.
+For example, add the following to your `~/.gitconfig`, where the `.gitignore`
+in your HOME directory contains the files and directories you'd like to
+globally ignore:
+```gitignore
+[core]
+    excludesfile = ~/.gitignore
+```
+* More on global ignores: https://help.github.com/articles/ignoring-files/
+* Comprehensive set of ignores on GitHub: https://github.com/github/gitignore
+## .editorconfig
+The `.editorconfig` file is provided in order to encourage and help you and
+your team define and maintain consistent coding styles between different
+editors and IDEs.
+By default, `.editorconfig` includes some basic
+[properties](http://editorconfig.org/#supported-properties) that reflect the
+coding styles from the files provided by default, but you can easily change
+them to better suit your needs.
+In order for your editor/IDE to apply the
+[properties](http://editorconfig.org/#supported-properties) from the
+`.editorconfig` file, you may need to [install a
+plugin]( http://editorconfig.org/#download).
+__N.B.__ If you aren't using the server configurations provided by HTML5
+Boilerplate, we highly encourage you to configure your server to block
+access to `.editorconfig` files, as they can disclose sensitive information!
+For more details, please refer to the [EditorConfig
+project](http://editorconfig.org/).
+## Server Configuration
+H5BP includes a [`.htaccess`](#htaccess) file for the [Apache HTTP
+server](https://httpd.apache.org/docs/). If you are not using Apache
+as your web server, then you are encouraged to download a
+[server configuration](https://github.com/h5bp/server-configs) that
+corresponds to your web server and environment.
+A `.htaccess` (hypertext access) file is an [Apache HTTP server
+configuration file](https://github.com/h5bp/server-configs-apache).
+The `.htaccess` file is mostly used for:
+* Rewriting URLs
+* Controlling cache
+* Authentication
+* Server-side includes
+* Redirects
+* Gzipping
+If you have access to the main server configuration file (usually called
+`httpd.conf`), you should add the logic from the `.htaccess` file in, for
+example, a <Directory> section in the main configuration file. This is usually
+the recommended way, as using .htaccess files slows down Apache!
+To enable Apache modules locally, please see:
+https://github.com/h5bp/server-configs-apache/wiki/How-to-enable-Apache-modules.
+In the repo the `.htaccess` is used for:
+* Allowing cross-origin access to web fonts
+* CORS header for images when browsers request it
+* Enable `404.html` as 404 error document
+* Making the website experience better for IE users better
+* Media UTF-8 as character encoding for `text/html` and `text/plain`
+* Enabling the rewrite URLs engine
+* Forcing or removing the `www.` at the begin of a URL
+* It blocks access to directories without a default document
+* It blocks access to files that can expose sensitive information.
+* It reduces MIME type security risks
+* It forces compressing (gzipping)
+* It tells the browser whether they should request a specific file from the
+  server or whether they should grab it from the browser's cache
+When using `.htaccess` we recommend reading all inline comments (the rules after
+a `#`) in the file once. There is a bunch of optional stuff in it.
+If you want to know more about the `.htaccess` file check out the
+[Apache HTTP server docs](https://httpd.apache.org/docs/) or more
+specifically the [htaccess
+section](https://httpd.apache.org/docs/current/howto/htaccess.html).
+Notice that the original repo for the `.htaccess` file is [this
+one](https://github.com/h5bp/server-configs-apache).
+## robots.txt
+The `robots.txt` file is used to give instructions to web robots on what can
+be crawled from the website.
+By default, the file provided by this project includes the next two lines:
+ * `User-agent: *` -  the following rules apply to all web robots
+ * `Disallow:` - everything on the website is allowed to be crawled
+If you want to disallow certain pages you will need to specify the path in a
+`Disallow` directive (e.g.: `Disallow: /path`) or, if you want to disallow
+crawling of all content, use `Disallow: /`.
+The `/robots.txt` file is not intended for access control, so don't try to
+use it as such. Think of it as a "No Entry" sign, rather than a locked door.
+URLs disallowed by the `robots.txt` file might still be indexed without being
+crawled, and the content from within the `robots.txt` file can be viewed by
+anyone, potentially disclosing the location of your private content! So, if
+you want to block access to private content, use proper authentication instead.
+For more information about `robots.txt`, please see:
+  * [robotstxt.org](http://www.robotstxt.org/)
+  * [How Google handles the `robots.txt` file](https://developers.google.com/webmasters/control-crawl-index/docs/robots_txt)
+## humans.txt
+The `humans.txt` file is used to provide information about people involved with
+the website.
+The provided file contains three sections:
+  * `TEAM` - this is intented to list the group of people responsible for the website
+  * `THANKS` - this is intended to list the group of people that have contributed
+  to the webste
+  * `TECHNOLOGY COLOPHON` - the section lists technologies used to make the website
+For more information about `humans.txt`, please see: http://humanstxt.org/
+## browserconfig.xml
+The `browserconfig.xml` file is used to customize the tile displayed when users
+pin your site to the Windows 8.1 start screen. In there you can define custom
+tile colors, custom images or even [live tiles](https://msdn.microsoft.com/library/dn455106.aspx#CreatingLiveTiles).
+By default, the file points to 2 placeholder tile images:
+* `tile.png` (558x558px): used for `Small`, `Medium` and `Large` tiles.
+  This image resizes automatically when necessary.
+* `tile-wide.png` (558x270px): user for `Wide` tiles.
+Notice that IE11 uses the same images when adding a site to the `favorites`.
+For more in-depth information about the `browserconfig.xml` file, please
+see [MSDN](https://msdn.microsoft.com/library/dn320426.aspx).

package/lib/reality-eth-monorepo/packages/website/webroot/doc/usage.md ADDED Viewed

@@ -0,0 +1,130 @@
+[HTML5 Boilerplate homepage](https://html5boilerplate.com/) | [Documentation
+table of contents](TOC.md)
+# Usage
+The most basic usage of HTML5 Boilerplate is to create a static site or simple
+app. Once you've downloaded or cloned the project, that process looks something
+like this:
+1. Set up the basic structure of the site.
+2. Add some content, style, and functionality.
+3. Run your site locally to see how it looks.
+4. Deploy your site.
+Cool, right? _It is_. That said, the smart defaults, baseline elements, default
+attribute values and various other utilities that HTML5 Boilerplate offers can
+serve as the foundation for whatever you're interested in building.
+Even the basic use-case of a simple static site can be enhanced by manipulating
+the code through an automated build process. Moving up in complexity HTML5
+Boilerplate can be integrated with whatever front-end framework, CMS or
+e-commerce platform you're working with. Mix-and-match to your heart's content.
+Use what you need (toss it in a blender if you need to) and discard the rest.
+HTML5 Boilerplate is a starting point, not a destination.
+## Basic structure
+A basic HTML5 Boilerplate site initially looks something like this:
+```
+.
+├── css
+│   ├── main.css
+│   └── normalize.css
+├── doc
+├── img
+├── js
+│   ├── main.js
+│   ├── plugins.js
+│   └── vendor
+│       ├── jquery.min.js
+│       └── modernizr.min.js
+├── .editorconfig
+├── .htaccess
+├── 404.html
+├── browserconfig.xml
+├── favicon.ico
+├── humans.txt
+├── icon.png
+├── index.html
+├── robots.txt
+├── site.webmanifest
+├── tile.png
+└── tile-wide.png
+```
+What follows is a general overview of each major part and how to use them.
+### css
+This directory should contain all your project's CSS files. It includes some
+initial CSS to help get you started from a solid foundation. [About the
+CSS](css.md).
+### doc
+This directory contains all the HTML5 Boilerplate documentation. You can use it
+as the location and basis for your own project's documentation.
+### js
+This directory should contain all your project's JS files. Libraries, plugins,
+and custom code can all be included here. It includes some initial JS to help
+get you started. [About the JavaScript](js.md).
+### .htaccess
+The default web server configs are for Apache. For more information, please
+refer to the [Apache Server Configs
+repository](https://github.com/h5bp/server-configs-apache).
+Host your site on a server other than Apache? You're likely to find the
+corresponding server configs project listed in our [Server Configs
+](https://github.com/h5bp/server-configs/blob/master/README.md) repository.
+### 404.html
+A helpful custom 404 to get you started.
+### browserconfig.xml
+This file contains all settings regarding custom tiles for IE11 and Edge.
+For more info on this topic, please refer to
+[MSDN](https://msdn.microsoft.com/library/dn455106.aspx).
+### .editorconfig
+The `.editorconfig` file is provided in order to encourage and help you and
+your team to maintain consistent coding styles between different
+editors and IDEs. [Read more about the `.editorconfig` file](misc.md#editorconfig).
+### index.html
+This is the default HTML skeleton that should form the basis of all pages on
+your site. If you are using a server-side templating framework, then you will
+need to integrate this starting HTML with your setup.
+Make sure that you update the URLs for the referenced CSS and JavaScript if you
+modify the directory structure at all.
+If you are using Google Universal Analytics, make sure that you edit the
+corresponding snippet at the bottom to include your analytics ID.
+### humans.txt
+Edit this file to include the team that worked on your site/app, and the
+technology powering it.
+### robots.txt
+Edit this file to include any pages you need hidden from search engines.
+### Icons
+Replace the default `favicon.ico`, `tile.png`, `tile-wide.png` and Apple
+Touch Icon with your own.
+If you want to use different Apple Touch Icons for different resolutions please
+refer to the [according documentation](extend.md#apple-touch-icons).

package/lib/reality-eth-monorepo/packages/website/webroot/favicon.ico ADDED Viewed

Binary file

package/lib/reality-eth-monorepo/packages/website/webroot/humans.txt ADDED Viewed

@@ -0,0 +1,15 @@
+# humanstxt.org/
+# The humans responsible & technology colophon
+# TEAM
+    <name> -- <role> -- <twitter>
+# THANKS
+    <name>
+# TECHNOLOGY COLOPHON
+    CSS3, HTML5
+    Apache Server Configs, jQuery, Modernizr, Normalize.css