RubyGems - reportir - Versions diffs - 0.2.1 → 0.3.0 - Mend

reportir 0.2.1 → 0.3.0

Files changed (38) hide show

data/lib/reportir/static_site_template/doc/faq.md DELETED Viewed

@@ -1,62 +0,0 @@
-[HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
-table of contents](TOC.md)
-# Frequently asked questions
-* [Why don't you automatically load the latest version of jQuery from the Google
-  CDN?](#why-dont-you-automatically-load-the-latest-version-of-jquery-from-the-google-cdn)
-* [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 don't you automatically load the latest version of jQuery from the Google CDN?
-The [file](https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.js) to which
-the Google [CDN](https://en.wikipedia.org/wiki/Content_delivery_network) points
-to is [no longer updated and will stay locked at version `1.11.1` in order to
-prevent inadvertent web
-breakage](http://blog.jquery.com/2014/07/03/dont-use-jquery-latest-js/).
-In general, version updating should be an intentional decision! You shouldn't
-include a URL that will always point to the latest version, as that version:
- * may not be compatible with the existing plugins/code on the site
- * will have a very short cache time compare to the specific version,
-   which means that users won't get the benefits of long-term caching
-### 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.
-However, having the code at the bottom of the page [helps improve
-performance](https://stevesouders.com/efws/inline-scripts-bottom.php).
-### How can I integrate [Bootstrap](http://getbootstrap.com/) with HTML5 Boilerplate?
-One simple way is to use [Initializr](http://www.initializr.com/) and create a
-custom build that includes both HTML5 Boilerplate and
-[Bootstrap](http://getbootstrap.com/).
-Read more 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).

data/lib/reportir/static_site_template/doc/html.md DELETED Viewed

@@ -1,223 +0,0 @@
-[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 the `lang`
-attribute to `<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/en-us/library/ie/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](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.
-## 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">
-```
-## Favicons and Touch Icon
-The shortcut icons should be put in the root directory of your site. 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.
-## Modernizr
-HTML5 Boilerplate uses a custom build of Modernizr.
-[Modernizr](http://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.
-In general, in order to keep page load times to a minimum, it's best to call
-any JavaScript at the end of the page because if a script is slow to load
-from an external server it may cause the whole page to hang. That said, the
-Modernizr script *needs* to run *before* the browser begins rendering the page,
-so that browsers lacking support for some of the new HTML5 elements are able to
-handle them properly. Therefore the Modernizr script is the only JavaScript
-file synchronously loaded at the top of the document.
-## 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="https://cdn.polyfill.io/v1/polyfill.min.js"></script>
-    <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js"></script>
-    <script>window.jQuery || document.write('<script src="js/vendor/jquery-1.11.2.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. Also using
-this technique, make sure 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).
-## 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 6/7. If you intended to support IE 6/7, then you
-should remove the snippet of code.
-### Google CDN for jQuery
-The Google CDN version of the jQuery JavaScript library is referenced towards
-the bottom of the page using a protocol-independent path (read more about this
-in the [FAQ](faq.md)). A local fallback of jQuery is included for rare instances
-when the CDN version might not be available, and to facilitate offline
-development.
-The Google CDN version is chosen over other [potential candidates (like the
-jQuery CDN](https://jquery.com/download/#using-jquery-with-a-cdn)) because
-it's fast in absolute terms and it has the best overall
-[penetration](http://httparchive.org/trends.php#perGlibs) which increases the
-odds of having a copy of the library in your user's browser cache.
-While the Google 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/) or
-[YSlow](https://developer.yahoo.com/yslow/) 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!

data/lib/reportir/static_site_template/doc/js.md DELETED Viewed

@@ -1,37 +0,0 @@
-[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.
-For larger projects, you can make use of a JavaScript module loader, like
-[Require.js](http://requirejs.org/), to load any other scripts you need to
-run.
-## plugins.js
-This file can be used to contain all your plugins, such as jQuery plugins and
-other 3rd party scripts.
-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](http://www.modernizr.com/download/).

data/lib/reportir/static_site_template/doc/misc.md DELETED Viewed

@@ -1,175 +0,0 @@
-[HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
-table of contents](TOC.md)
-# Miscellaneous
-* [.gitignore](#gitignore)
-* [.editorconfig](#editorconfig)
-* [Server Configuration](#server-configuration)
-* [crossdomain.xml](#crossdomainxml)
-* [robots.txt](#robotstxt)
-* [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 will 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. 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 a
-[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
-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).
-## crossdomain.xml
-The _cross-domain policy file_ is an XML document that gives a web client —
-such as Adobe Flash Player, Adobe Reader, etc. — permission to handle data
-across multiple domains, by:
- * granting read access to data
- * permitting the client to include custom headers in cross-domain requests
- * granting permissions for socket-based connections
-__e.g.__ If a client hosts content from a particular source domain and that
-content makes requests directed towards a domain other than its own, the remote
-domain would need to host a cross-domain policy file in order to grant access
-to the source domain and allow the client to continue with the transaction.
-For more in-depth information, please see Adobe's [cross-domain policy file
-specification](https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html).
-## 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)
-## 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/en-us/library/ie/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/en-us/library/ie/dn320426.aspx).

data/lib/reportir/static_site_template/doc/usage.md DELETED Viewed

@@ -1,130 +0,0 @@
-[HTML5 Boilerplate homepage](https://html5boilerplate.com) | [Documentation
-table of contents](TOC.md)
-# Usage
-Once you have cloned or downloaded HTML5 Boilerplate, creating a site or app
-usually involves the following:
-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. (Optionally run a build script to automate the optimization of your site -
-   e.g. [ant build script](https://github.com/h5bp/ant-build-script))
-5. Deploy your site.
-## 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
-├── apple-touch-icon.png
-├── browserconfig.xml
-├── index.html
-├── humans.txt
-├── robots.txt
-├── crossdomain.xml
-├── favicon.ico
-├── tile-wide.png
-└── tile.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.
-For more info on this topic, please refer to
-[MSDN](https://msdn.microsoft.com/en-us/library/ie/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.
-### crossdomain.xml
-A template for working with cross-domain requests. [About
-crossdomain.xml](misc.md#crossdomainxml).
-### 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).
-You might want to check out Hans' handy [HTML5 Boilerplate Favicon and Apple
-Touch Icon
-PSD-Template](https://drublic.de/blog/html5-boilerplate-favicons-psd-template/).

data/lib/reportir/static_site_template/humans.txt DELETED Viewed

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

data/lib/reportir/static_site_template/img/pagination.png DELETED Viewed

Binary file

data/lib/reportir/static_site_template/robots.txt DELETED Viewed

@@ -1,5 +0,0 @@
-# www.robotstxt.org/
-# Allow crawling of all content
-User-agent: *
-Disallow:

data/lib/reportir/static_site_template/tile-wide.png DELETED Viewed

Binary file

data/lib/reportir/static_site_template/tile.png DELETED Viewed

Binary file

data/reportir-0.2.0.gem DELETED Viewed

Binary file