mattery 0.0.1.alpha

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 (51) hide show
  1. checksums.yaml +7 -0
  2. data/.DS_Store +0 -0
  3. data/.gitignore +12 -0
  4. data/.rspec +2 -0
  5. data/.travis.yml +5 -0
  6. data/CODE_OF_CONDUCT.md +74 -0
  7. data/Gemfile +5 -0
  8. data/LICENSE.txt +21 -0
  9. data/README.md +41 -0
  10. data/Rakefile +6 -0
  11. data/bin/console +14 -0
  12. data/bin/matter +5 -0
  13. data/bin/setup +8 -0
  14. data/lib/matter.rb +36 -0
  15. data/lib/matter/.DS_Store +0 -0
  16. data/lib/matter/cli/application.rb +47 -0
  17. data/lib/matter/version.rb +3 -0
  18. data/matter.gemspec +30 -0
  19. data/matter_source/.DS_Store +0 -0
  20. data/matter_source/.editorconfig +13 -0
  21. data/matter_source/.gitattributes +1 -0
  22. data/matter_source/.gitignore +2 -0
  23. data/matter_source/.htaccess +984 -0
  24. data/matter_source/404.html +60 -0
  25. data/matter_source/LICENSE.txt +7 -0
  26. data/matter_source/apple-touch-icon.png +0 -0
  27. data/matter_source/assets/.DS_Store +0 -0
  28. data/matter_source/assets/css/main.css +271 -0
  29. data/matter_source/assets/css/normalize.css +424 -0
  30. data/matter_source/assets/img/.gitignore +0 -0
  31. data/matter_source/assets/js/.DS_Store +0 -0
  32. data/matter_source/assets/js/main.js +0 -0
  33. data/matter_source/assets/js/vendor/jquery-1.12.0.min.js +5 -0
  34. data/matter_source/assets/js/vendor/modernizr-2.8.3.min.js +4 -0
  35. data/matter_source/browserconfig.xml +12 -0
  36. data/matter_source/crossdomain.xml +15 -0
  37. data/matter_source/doc/TOC.md +29 -0
  38. data/matter_source/doc/css.md +162 -0
  39. data/matter_source/doc/extend.md +663 -0
  40. data/matter_source/doc/faq.md +46 -0
  41. data/matter_source/doc/html.md +227 -0
  42. data/matter_source/doc/js.md +37 -0
  43. data/matter_source/doc/misc.md +178 -0
  44. data/matter_source/doc/usage.md +130 -0
  45. data/matter_source/favicon.ico +0 -0
  46. data/matter_source/humans.txt +15 -0
  47. data/matter_source/index.html +41 -0
  48. data/matter_source/robots.txt +5 -0
  49. data/matter_source/tile-wide.png +0 -0
  50. data/matter_source/tile.png +0 -0
  51. metadata +151 -0
data/matter_source/doc/faq.md ADDED
@@ -0,0 +1,46 @@
1
+ [HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
2
+ table of contents](TOC.md)
3
+
4
+ # Frequently asked questions
5
+
6
+ * [Why is the Google Analytics code at the bottom? Google recommends it be
7
+ placed in the `<head>`.](#why-is-the-google-analytics-code-at-the-bottom-google-recommends-it-be-placed-in-the-head)
8
+ * [How can I integrate Bootstrap with HTML5
9
+ Boilerplate?](#how-can-i-integrate-bootstrap-with-html5-boilerplate)
10
+ * [Do I need to upgrade my site each time a new version of HTML5 Boilerplate is
11
+ released?](#do-i-need-to-upgrade-my-site-each-time-a-new-version-of-html5-boilerplate-is-released)
12
+ * [Where can I get help with support
13
+ questions?](#where-can-i-get-help-with-support-questions)
14
+
15
+ --
16
+
17
+
18
+ ### Why is the Google Analytics code at the bottom? Google recommends it be placed in the `<head>`.
19
+
20
+ The main advantage of placing it in the `<head>` is that you will track the
21
+ user's `pageview` even if they leave the page before it has been fully loaded.
22
+ However, having the code at the bottom of the page [helps improve
23
+ performance](https://stevesouders.com/efws/inline-scripts-bottom.php).
24
+
25
+
26
+ ### How can I integrate [Bootstrap](http://getbootstrap.com/) with HTML5 Boilerplate?
27
+
28
+ One simple way is to use [Initializr](http://www.initializr.com/) and create a
29
+ custom build that includes both HTML5 Boilerplate and
30
+ [Bootstrap](http://getbootstrap.com/).
31
+
32
+ Read more about how [HTML5 Boilerplate and Bootstrap complement each
33
+ other](https://www.quora.com/Is-Bootstrap-a-complement-or-an-alternative-to-HTML5-Boilerplate-or-viceversa/answer/Nicolas-Gallagher).
34
+
35
+
36
+ ### Do I need to upgrade my site each time a new version of HTML5 Boilerplate is released?
37
+
38
+ No, same as you don't normally replace the foundation of a house once it
39
+ was built. However, there is nothing stopping you from trying to work in the
40
+ latest changes, but you'll have to assess the costs/benefits of doing so.
41
+
42
+
43
+ ### Where can I get help with support questions?
44
+
45
+ Please ask for help on
46
+ [StackOverflow](https://stackoverflow.com/questions/tagged/html5boilerplate).
data/matter_source/doc/html.md ADDED
@@ -0,0 +1,227 @@
1
+ [HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
2
+ table of contents](TOC.md)
3
+
4
+ # The HTML
5
+
6
+ By default, HTML5 Boilerplate provides two `html` pages:
7
+
8
+ * [`index.html`](#indexhtml) - a default HTML skeleton that should form the
9
+ basis of all pages on your website
10
+ * [`404.html`](#404html) - a placeholder 404 error page
11
+
12
+
13
+ ## `index.html`
14
+
15
+
16
+ ### The `no-js` class
17
+
18
+ The `no-js` class is provided in order to allow you to more easily and
19
+ explicitly add custom styles based on whether JavaScript is disabled
20
+ (`.no-js`) or enabled (`.js`). Using this technique also helps [avoid the
21
+ FOUC](https://www.paulirish.com/2009/avoiding-the-fouc-v3/).
22
+
23
+
24
+ ## Language attribute
25
+
26
+ Please consider specifying the language of your content by adding the `lang`
27
+ attribute to `<html>` as in this example:
28
+
29
+ ```html
30
+ <html class="no-js" lang="en">
31
+ ```
32
+
33
+ ### The order of the `<title>` and `<meta>` tags
34
+
35
+ The order in which the `<title>` and the `<meta>` tags are specified is
36
+ important because:
37
+
38
+ 1) the charset declaration (`<meta charset="utf-8">`):
39
+
40
+ * must be included completely within the [first 1024 bytes of the
41
+ document](https://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#charset)
42
+
43
+ * should be specified as early as possible (before any content that could
44
+ be controlled by an attacker, such as a `<title>` element) in order to
45
+ avoid a potential [encoding-related security
46
+ issue](https://code.google.com/p/doctype-mirror/wiki/ArticleUtf7) in
47
+ Internet Explorer
48
+
49
+ 2) the meta tag for compatibility mode
50
+ (`<meta http-equiv="x-ua-compatible" content="ie=edge">`):
51
+
52
+ * [needs to be included before all other tags except for the `<title>` and
53
+ the other `<meta>`
54
+ tags](https://msdn.microsoft.com/en-us/library/cc288325.aspx)
55
+
56
+
57
+ ### `x-ua-compatible`
58
+
59
+ Internet Explorer 8/9/10 support [document compatibility
60
+ modes](https://msdn.microsoft.com/en-us/library/cc288325.aspx) that affect the
61
+ way webpages are interpreted and displayed. Because of this, even if your site's
62
+ visitor is using, let's say, Internet Explorer 9, it's possible that IE will not
63
+ use the latest rendering engine, and instead, decide to render your page using
64
+ the Internet Explorer 5.5 rendering engine.
65
+
66
+ Specifying the `x-ua-compatible` meta tag:
67
+
68
+ ```html
69
+ <meta http-equiv="x-ua-compatible" content="ie=edge">
70
+ ```
71
+
72
+ or sending the page with the following HTTP response header
73
+
74
+ ```
75
+ X-UA-Compatible: IE=edge
76
+ ```
77
+
78
+ will force Internet Explorer 8/9/10 to render the webpage in the highest
79
+ available mode in [the various cases when it may
80
+ not](https://hsivonen.fi/doctype/#ie8), and therefore, ensure that anyone
81
+ browsing your site is treated to the best possible user experience that
82
+ browser can offer.
83
+
84
+ If possible, we recommend that you remove the `meta` tag and send only the
85
+ HTTP response header as the `meta` tag will not always work if your site is
86
+ served on a non-standard port, as Internet Explorer's preference option
87
+ `Display intranet sites in Compatibility View` is checked by default.
88
+
89
+ If you are using Apache as your webserver, including the
90
+ [`.htaccess`](https://github.com/h5bp/server-configs-apache) file takes care of
91
+ the HTTP header. If you are using a different server, check out our [other
92
+ server config](https://github.com/h5bp/server-configs).
93
+
94
+ Starting with Internet Explorer 11, [document modes are
95
+ deprecated](https://msdn.microsoft.com/en-us/library/ie/bg182625.aspx#docmode).
96
+ If your business still relies on older web apps and services that were
97
+ designed for older versions of Internet Explorer, you might want to consider
98
+ enabling [Enterprise Mode](http://blogs.msdn.com/b/ie/archive/2014/04/02/stay-up-to-date-with-enterprise-mode-for-internet-explorer-11.aspx) throughout your company.
99
+
100
+
101
+ ## Mobile viewport
102
+
103
+ There are a few different options that you can use with the [`viewport` meta
104
+ tag](https://docs.google.com/present/view?id=dkx3qtm_22dxsrgcf4 "Viewport and
105
+ Media Queries - The Complete Idiot's Guide"). You can find out more in [the
106
+ Apple developer docs](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html).
107
+ HTML5 Boilerplate comes with a simple setup that strikes a good balance for general use cases.
108
+
109
+ ```html
110
+ <meta name="viewport" content="width=device-width, initial-scale=1">
111
+ ```
112
+
113
+ ## Favicons and Touch Icon
114
+
115
+ The shortcut icons should be put in the root directory of your site. HTML5
116
+ Boilerplate comes with a default set of icons (include favicon and one Apple
117
+ Touch Icon) that you can use as a baseline to create your own.
118
+
119
+ Please refer to the more detailed description in the [Extend section](extend.md)
120
+ of these docs.
121
+
122
+ ## Modernizr
123
+
124
+ HTML5 Boilerplate uses a custom build of Modernizr.
125
+
126
+ [Modernizr](http://modernizr.com) is a JavaScript library which adds classes to
127
+ the `html` element based on the results of feature test and which ensures that
128
+ all browsers can make use of HTML5 elements (as it includes the HTML5 Shiv).
129
+ This allows you to target parts of your CSS and JavaScript based on the
130
+ features supported by a browser.
131
+
132
+ In general, in order to keep page load times to a minimum, it's best to call
133
+ any JavaScript at the end of the page because if a script is slow to load
134
+ from an external server it may cause the whole page to hang. That said, the
135
+ Modernizr script *needs* to run *before* the browser begins rendering the page,
136
+ so that browsers lacking support for some of the new HTML5 elements are able to
137
+ handle them properly. Therefore the Modernizr script is the only JavaScript
138
+ file synchronously loaded at the top of the document.
139
+
140
+ ## What about polyfills?
141
+
142
+ If you need to include [polyfills](https://remysharp.com/2010/10/08/what-is-a-polyfill)
143
+ in your project, you must make sure those load before any other JavaScript. If you're
144
+ using some polyfill CDN service, like [cdn.polyfill.io](https://cdn.polyfill.io/),
145
+ just put it before the other scripts in the bottom of the page:
146
+
147
+ ```html
148
+ <script src="https://cdn.polyfill.io/v1/polyfill.min.js"></script>
149
+ <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js"></script>
150
+ <script>window.jQuery || document.write('<script src="js/vendor/jquery-1.11.2.min.js"><\/script>')</script>
151
+ <script src="js/plugins.js"></script>
152
+ <script src="js/main.js"></script>
153
+ </body>
154
+ ```
155
+
156
+ If you like to just include the polyfills yourself, you could include them in
157
+ `js/plugins.js`. When you have a bunch of polyfills to load in, you could
158
+ also create a `polyfills.js` file in the `js/vendor` directory. Also using
159
+ this technique, make sure the polyfills are all loaded before any other
160
+ Javascript.
161
+
162
+ There are some misconceptions about Modernizr and polyfills. It's important
163
+ to understand that Modernizr just handles feature checking, not polyfilling
164
+ itself. The only thing Modernizr does regarding polyfills is that the team
165
+ maintains [a huge list of cross Browser polyfills](https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills).
166
+
167
+ ## The content area
168
+
169
+ The central part of the boilerplate template is pretty much empty. This is
170
+ intentional, in order to make the boilerplate suitable for both web page and
171
+ web app development.
172
+
173
+ ### Browser Upgrade Prompt
174
+
175
+ The main content area of the boilerplate includes a prompt to install an up to
176
+ date browser for users of IE 6/7. If you intended to support IE 6/7, then you
177
+ should remove the snippet of code.
178
+
179
+ ### jQuery CDN for jQuery
180
+
181
+ The jQuery CDN version of the jQuery JavaScript library is referenced towards
182
+ the bottom of the page. A local fallback of jQuery is included for rare instances
183
+ when the CDN version might not be available, and to facilitate offline
184
+ development.
185
+
186
+ The jQuery CDN version was chosen over other potential candidates
187
+ ([like Google's Hosted Libraries](https://developers.google.com/speed/libraries/))
188
+ because it's fast ([comparable or faster than Google by some
189
+ measures](https://www.cdnperf.com/#jsdelivr,cdnjs,google,yandex,microsoft,jquery,bootstrapcdn/https/90))
190
+ and, (unlike Google's CDN) is available to China's hundreds of millions of internet users.
191
+ For many years we [chose](https://github.com/h5bp/html5-boilerplate/issues/1191)
192
+ the Google Hosted version over the jQuery CDN because it was available
193
+ over HTTPS (the jQuery CDN was not,) and it offered a better chance of
194
+ hitting the cache lottery owing to the popularity of the Google CDN.
195
+ The first issue is no longer valid and the second is far outweighed by
196
+ being able to serve jQuery to Chinese users.
197
+
198
+ While the jQuery CDN is a strong default solution your site or application may
199
+ require a different configuration. Testing your site with services like
200
+ [WebPageTest](https://www.webpagetest.org/) and browser tools like
201
+ [PageSpeed Insights](https://developers.google.com/speed/pagespeed/insights/) or
202
+ [YSlow](https://developer.yahoo.com/yslow/) will help you examine the real
203
+ world performance of your site and can show where you can optimize your specific
204
+ site or application.
205
+
206
+ ### Google Universal Analytics Tracking Code
207
+
208
+ Finally, an optimized version of the Google Universal Analytics tracking code is
209
+ included. Google recommends that this script be placed at the top of the page.
210
+ Factors to consider: if you place this script at the top of the page, you’ll
211
+ be able to count users who don’t fully load the page, and you’ll incur the max
212
+ number of simultaneous connections of the browser.
213
+
214
+ Further information:
215
+
216
+ * [Optimizing the Google Universal Analytics
217
+ Snippet](https://mathiasbynens.be/notes/async-analytics-snippet#universal-analytics)
218
+ * [Introduction to
219
+ Analytics.js](https://developers.google.com/analytics/devguides/collection/analyticsjs/)
220
+ * [Google Analytics Demos & Tools](https://ga-dev-tools.appspot.com/)
221
+
222
+ **N.B.** The Google Universal Analytics snippet is included by default mainly
223
+ because Google Analytics is [currently one of the most popular tracking
224
+ solutions](https://trends.builtwith.com/analytics/Google-Analytics) out there.
225
+ However, its usage isn't set in stone, and you SHOULD consider exploring the
226
+ [alternatives](https://en.wikipedia.org/wiki/List_of_web_analytics_software)
227
+ and use whatever suits your needs best!
data/matter_source/doc/js.md ADDED
@@ -0,0 +1,37 @@
1
+ [HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
2
+ table of contents](TOC.md)
3
+
4
+ # The JavaScript
5
+
6
+ Information about the default JavaScript included in the project.
7
+
8
+ ## main.js
9
+
10
+ This file can be used to contain or reference your site/app JavaScript code.
11
+ For larger projects, you can make use of a JavaScript module loader, like
12
+ [Require.js](http://requirejs.org/), to load any other scripts you need to
13
+ run.
14
+
15
+ ## plugins.js
16
+
17
+ This file can be used to contain all your plugins, such as jQuery plugins and
18
+ other 3rd party scripts.
19
+
20
+ One approach is to put jQuery plugins inside of a `(function($){ ...
21
+ })(jQuery);` closure to make sure they're in the jQuery namespace safety
22
+ blanket. Read more about [jQuery plugin
23
+ authoring](https://learn.jquery.com/plugins/#Getting_Started).
24
+
25
+ By default the `plugins.js` file contains a small script to avoid `console`
26
+ errors in browsers that lack a `console`. The script will make sure that, if
27
+ a console method isn't available, that method will have the value of empty
28
+ function, thus, preventing the browser from throwing an error.
29
+
30
+
31
+ ## vendor
32
+
33
+ This directory can be used to contain all 3rd party library code.
34
+
35
+ Minified versions of the latest jQuery and Modernizr libraries are included by
36
+ default. You may wish to create your own [custom Modernizr
37
+ build](http://www.modernizr.com/download/).
data/matter_source/doc/misc.md ADDED
@@ -0,0 +1,178 @@
1
+ [HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
2
+ table of contents](TOC.md)
3
+
4
+ # Miscellaneous
5
+
6
+ * [.gitignore](#gitignore)
7
+ * [.editorconfig](#editorconfig)
8
+ * [Server Configuration](#server-configuration)
9
+ * [crossdomain.xml](#crossdomainxml)
10
+ * [robots.txt](#robotstxt)
11
+ * [browserconfig.xml](#browserconfigxml)
12
+
13
+ --
14
+
15
+ ## .gitignore
16
+
17
+ HTML5 Boilerplate includes a basic project-level `.gitignore`. This should
18
+ primarily be used to avoid certain project-level files and directories from
19
+ being kept under source control. Different development-environments will
20
+ benefit from different collections of ignores.
21
+
22
+ OS-specific and editor-specific files should be ignored using a "global
23
+ ignore" that applies to all repositories on your system.
24
+
25
+ For example, add the following to your `~/.gitconfig`, where the `.gitignore`
26
+ in your HOME directory contains the files and directories you'd like to
27
+ globally ignore:
28
+
29
+ ```gitignore
30
+ [core]
31
+ excludesfile = ~/.gitignore
32
+ ```
33
+
34
+ * More on global ignores: https://help.github.com/articles/ignoring-files
35
+ * Comprehensive set of ignores on GitHub: https://github.com/github/gitignore
36
+
37
+
38
+ ## .editorconfig
39
+
40
+ The `.editorconfig` file is provided in order to encourage and help you and
41
+ your team define and maintain consistent coding styles between different
42
+ editors and IDEs.
43
+
44
+ By default, `.editorconfig` includes some basic
45
+ [properties](http://editorconfig.org/#supported-properties) that reflect the
46
+ coding styles from the files provided by default, but you can easily change
47
+ them to better suit your needs.
48
+
49
+ In order for your editor/IDE to apply the
50
+ [properties](http://editorconfig.org/#supported-properties) from the
51
+ `.editorconfig` file, you will need to [install a
52
+ plugin]( http://editorconfig.org/#download).
53
+
54
+ __N.B.__ If you aren't using the server configurations provided by HTML5
55
+ Boilerplate, we highly encourage you to configure your server to block
56
+ access to `.editorconfig` files, as they can disclose sensitive information!
57
+
58
+ For more details, please refer to the [EditorConfig
59
+ project](http://editorconfig.org/).
60
+
61
+
62
+ ## Server Configuration
63
+
64
+ H5BP includes a [`.htaccess`](#htaccess) file for the [Apache HTTP
65
+ server](https://httpd.apache.org/docs/). If you are not using Apache
66
+ as your web server, then you are encouraged to download a
67
+ [server configuration](https://github.com/h5bp/server-configs) that
68
+ corresponds to your web server and environment.
69
+
70
+ A `.htaccess` (hypertext access) file is a [Apache HTTP server
71
+ configuration file](https://github.com/h5bp/server-configs-apache).
72
+ The `.htaccess` file is mostly used for:
73
+
74
+ * Rewriting URLs
75
+ * Controlling cache
76
+ * Authentication
77
+ * Server-side includes
78
+ * Redirects
79
+ * Gzipping
80
+
81
+ If you have access to the main server configuration file (usually called
82
+ `httpd.conf`), you should add the logic from the `.htaccess` file in, for
83
+ example, a <Directory> section in the main configuration file. This is usually
84
+ the recommended way, as using .htaccess files slows down Apache!
85
+
86
+ To enable Apache modules locally, please see:
87
+ https://github.com/h5bp/server-configs-apache/wiki/How-to-enable-Apache-modules.
88
+
89
+ In the repo the `.htaccess` is used for:
90
+
91
+ * Allowing cross-origin access to web fonts
92
+ * CORS header for images when browsers request it
93
+ * Enable `404.html` as 404 error document
94
+ * Making the website experience better for IE users better
95
+ * Media UTF-8 as character encoding for `text/html` and `text/plain`
96
+ * Enabling the rewrite URLs engine
97
+ * Forcing or removing the `www.` at the begin of a URL
98
+ * It blocks access to directories without a default document
99
+ * It blocks access to files that can expose sensitive information.
100
+ * It reduces MIME type security risks
101
+ * It forces compressing (gzipping)
102
+ * It tells the browser whether they should request a specific file from the
103
+ server or whether they should grab it from the browser's cache
104
+
105
+ When using `.htaccess` we recommend reading all inline comments (the rules after
106
+ a `#`) in the file once. There is a bunch of optional stuff in it.
107
+
108
+ If you want to know more about the `.htaccess` file check out the
109
+ [Apache HTTP server docs](https://httpd.apache.org/docs/) or more
110
+ specifically the [htaccess
111
+ section](https://httpd.apache.org/docs/current/howto/htaccess.html).
112
+
113
+ Notice that the original repo for the `.htaccess` file is [this
114
+ one](https://github.com/h5bp/server-configs-apache).
115
+
116
+
117
+ ## crossdomain.xml
118
+
119
+ The _cross-domain policy file_ is an XML document that gives a web client —
120
+ such as Adobe Flash Player, Adobe Reader, etc. — permission to handle data
121
+ across multiple domains, by:
122
+
123
+ * granting read access to data
124
+ * permitting the client to include custom headers in cross-domain requests
125
+ * granting permissions for socket-based connections
126
+
127
+ __e.g.__ If a client hosts content from a particular source domain and that
128
+ content makes requests directed towards a domain other than its own, the remote
129
+ domain would need to host a cross-domain policy file in order to grant access
130
+ to the source domain and allow the client to continue with the transaction.
131
+
132
+ For more in-depth information, please see Adobe's [cross-domain policy file
133
+ specification](https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html).
134
+
135
+
136
+ ## robots.txt
137
+
138
+ The `robots.txt` file is used to give instructions to web robots on what can
139
+ be crawled from the website.
140
+
141
+ By default, the file provided by this project includes the next two lines:
142
+
143
+ * `User-agent: *` - the following rules apply to all web robots
144
+ * `Disallow:` - everything on the website is allowed to be crawled
145
+
146
+ If you want to disallow certain pages you will need to specify the path in a
147
+ `Disallow` directive (e.g.: `Disallow: /path`) or, if you want to disallow
148
+ crawling of all content, use `Disallow: /`.
149
+
150
+ The `/robots.txt` file is not intended for access control, so don't try to
151
+ use it as such. Think of it as a "No Entry" sign, rather than a locked door.
152
+ URLs disallowed by the `robots.txt` file might still be indexed without being
153
+ crawled, and the content from within the `robots.txt` file can be viewed by
154
+ anyone, potentially disclosing the location of your private content! So, if
155
+ you want to block access to private content, use proper authentication instead.
156
+
157
+ For more information about `robots.txt`, please see:
158
+
159
+ * [robotstxt.org](http://www.robotstxt.org/)
160
+ * [How Google handles the `robots.txt` file](https://developers.google.com/webmasters/control-crawl-index/docs/robots_txt)
161
+
162
+
163
+ ## browserconfig.xml
164
+
165
+ The `browserconfig.xml` file is used to customize the tile displayed when users
166
+ pin your site to the Windows 8.1 start screen. In there you can define custom
167
+ tile colors, custom images or even [live tiles](https://msdn.microsoft.com/en-us/library/ie/dn455106.aspx#CreatingLiveTiles).
168
+
169
+ By default, the file points to 2 placeholder tile images:
170
+
171
+ * `tile.png` (558x558px): used for `Small`, `Medium` and `Large` tiles.
172
+ This image resizes automatically when necessary.
173
+ * `tile-wide.png` (558x270px): user for `Wide` tiles.
174
+
175
+ Notice that IE11 uses the same images when adding a site to the `favorites`.
176
+
177
+ For more in-depth information about the `browserconfig.xml` file, please
178
+ see [MSDN](https://msdn.microsoft.com/en-us/library/ie/dn320426.aspx).