middleman-gdpr 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 644b704a5ba83280c4d287fa1f271ac3c0a938db390c6086d98a1d58b1e486ed
+  data.tar.gz: 46b00fd0a01b1f24e96244602209e0ca450047e929dd219371a7ef0f0a4c59a0
+SHA512:
+  metadata.gz: 01b92206c792ebdbb447fb06197a8fbdfc9c3e3ba69d43e7af270c7e54e4ea01b954d54c9a8ccc4e0968b41873f97e58960641a81db2c7467c5767ffb1d3b384
+  data.tar.gz: 6ff5caee0f6e04ace4b7cf5ebc475b5067cfde9ff70817f8585e581a374a75913296e1adfdd150d596676659dce71accbac46db9816086ab742551508077be93

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2018 Les Poupées Russes
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,65 @@
+# Middleman GDPR
+Helps getting your Middleman website GDPR compliant
+
+## Installation
+Add this line to your Gemfile:
+
+```ruby
+gem 'middleman-gdpr'
+```
+
+And then execute:
+```bash
+$ bundle
+```
+
+Or install it yourself as:
+```bash
+$ gem install middleman-gdpr
+```
+
+Activate [Sprockets](https://github.com/middleman/middleman-sprockets) and [I18n](https://middlemanapp.com/advanced/localization/):
+```ruby
+# config.rb
+activate :sprockets
+activate :i18n
+```
+
+Add this to the layout:
+```ruby
+  <%= gdpr %>
+```
+
+Add this to javascripts:
+```js
+//= require gdpr/cookie_consent
+```
+
+Add this to stylesheets:
+```sass
+@import 'gdpr/cookie_consent'
+```
+
+Set the privacy policy url in the locales.
+
+## Checklist
+
+https://www.eugdpr.org/
+
+- [x] Cookie consent
+- [ ] Privacy policy
+- [ ] There must be an optin
+- [ ] Optin must be unchecked by default
+- [ ] Account must be deletable
+- [ ] Users must have access to their data
+- [ ] Users must be able to modify their data 
+
+## Thanks
+
+Inspired by cookies_eu (https://github.com/infinum/cookies_eu), thank you :)
+
+## Contributing
+Feel free to pull request!
+
+## License
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,26 @@
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+
+require 'rdoc/task'
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'Gdpr'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.md')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+require 'bundler/gem_tasks'
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = false
+end
+
+task default: :test

data/lib/middleman-gdpr.rb

@@ -0,0 +1,14 @@
+require 'middleman-sprockets'
+
+module Middleman
+  module Gdpr
+
+  end
+end
+
+Middleman::Extensions.register :gdpr do
+  require 'middleman-gdpr/version'
+  require 'middleman-gdpr/extension'
+
+  Middleman::Gdpr::Extension
+end

data/lib/middleman-gdpr/extension.rb

@@ -0,0 +1,51 @@
+module Middleman
+  module Gdpr
+    class Extension < Extension
+      # def initialize(app, options_hash={}, &block)
+      #   super
+      # end
+
+      def after_configuration
+        puts "\e[91mGDPR: Sprockets extension not found, GDPR extension has not been activated\e[39m" and return if sprockets.blank?
+        puts "\e[91mGDPR: I18n extension not found, GDPR extension has not been activated\e[39m" and return if i18n.blank?
+
+        ['source/stylesheets', 'source/javascripts', 'node_modules'].each do |path|
+          sprockets.environment.append_path root + path
+        end
+
+        I18n.load_path.concat Dir[root + 'locales/*.yml']
+      end
+
+      def root
+        Pathname.new(__dir__) + '../..'
+      end
+
+      helpers do
+        def gdpr
+          <<~HTML
+            <div class="gdpr__cookie_consent js-gdpr__cookie_consent">
+              <div class="gdpr__cookie_consent__text">
+                #{t 'gdpr.cookie_consent.text'}
+                <br />
+                #{t 'gdpr.cookie_consent.learn_more_html', link: t('gdpr.privacy_policy')}
+              </div>
+              <div class="gdpr__cookie_consent__buttons">
+                <button class="gdpr__cookie_consent__buttons__ok js-gdpr__cookie_consent__buttons__ok"> #{t 'gdpr.cookie_consent.button' }</button>
+              </div>
+            </div>
+          HTML
+        end
+      end
+
+      private
+
+      def sprockets
+        @app.extensions[:sprockets]
+      end
+
+      def i18n
+        @app.extensions[:i18n]
+      end
+    end
+  end
+end

data/lib/middleman-gdpr/version.rb

@@ -0,0 +1,5 @@
+module Middleman
+  module Gdpr
+    VERSION = '0.1.0'
+  end
+end

data/lib/middleman_extension.rb

@@ -0,0 +1 @@
+require 'middleman-gdpr'

data/locales/de.yml

@@ -0,0 +1,7 @@
+de:
+  gdpr:
+    privacy_policy: https://www.eugdpr.org
+    cookie_consent:
+      text: "Indem Sie Ihre Navigation auf dieser Website fortsetzen, akzeptieren Sie die Verwendung von Cookies, die insbesondere dazu dienen, Ihnen personalisierte Funktionen anzubieten und Ihre Besuche auf der Website zu erfassen."
+      button: "Ich habe verstanden"
+      learn_more_html: "Für weitere Informationen und Einstellen der Cookies : <a href=\"%{link}\" target=\"_blank\">bitte hier klicken</a>"

data/locales/en.yml

@@ -0,0 +1,7 @@
+en:
+  gdpr:
+    privacy_policy: https://www.eugdpr.org
+    cookie_consent:
+      text: 'By navigating on this website, you agree to our use of cookies to personalize certain website features and to measure the audience and use of this website.'
+      button: "I agree"
+      learn_more_html: "To learn more about cookies and how to customize your cookies options: <a href=\"%{link}\" target=\"_blank\">click here</a>"

data/locales/es.yml

@@ -0,0 +1,7 @@
+es:
+  gdpr:
+    privacy_policy: https://www.eugdpr.org
+    cookie_consent:
+      text: "Al continuar su navegación por este sitio, acepta la utilización de cookies, que tienen por objeto proponerle funcionalidades personalizadas y realizar mediciones de audiencia."
+      button: "Entendido"
+      learn_more_html: "Para saber más y definir la configuración de estas cookies: <a href=\"%{link}\" target=\"_blank\">hacer clic aquí</a>"

data/locales/fr.yml

@@ -0,0 +1,7 @@
+fr:
+  gdpr:
+    privacy_policy: https://www.eugdpr.org
+    cookie_consent:
+      text: "En poursuivant votre navigation sur ce site, vous acceptez l’utilisation de Cookies pour vous proposer notamment des fonctionnalités personnalisées et pour réaliser des mesures d’audience."
+      button: "J'ai compris"
+      learn_more_html: "Pour en savoir plus et paramétrer ces cookies : <a href=\"%{link}\" target=\"_blank\">cliquer ici</a>"

data/locales/it.yml

@@ -0,0 +1,7 @@
+it:
+  gdpr:
+    privacy_policy: https://www.eugdpr.org
+    cookie_consent:
+      text: "Proseguendo nella navigazione del Sito, l'utente acconsente all'utilizzo dei cookie allo scopo di fornire funzioni personalizzate e di misurazione dell'audience."
+      button: "Ho capito"
+      learn_more_html: "Per maggiori informazioni e per configurare i cookie: <a href=\"%{link}\" target=\"_blank\">cliccare qui</a>"

data/locales/zh.yml

@@ -0,0 +1,7 @@
+zh:
+  gdpr:
+    privacy_policy: https://www.eugdpr.org
+    cookie_consent:
+      text: '在瀏覽本網站之時，您同意本網站收集閣下Cookies（如有）及用於獲取配置數據以及分析上網認識的瀏覽習慣。Cookies可免除閣下每次瀏覽網站是重新登記的麻煩，並追蹤閣下喜歡的網頁主題選項，為閣下提供更個性化服務。阁下如不希望接受Cookies，可以修改有关互联网选项或阁下计算机系统的浏览选项，但阁下可能因此无法使用或启动本网站的若干功能。'
+      button: "同意"
+      learn_more_html: "<a href=\"%{link}\" target=\"_blank\">關於Cookies以及設置閣下計算機系統的瀏</a>"

data/node_modules/js-cookie/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+## Issues
+
+- Report issues or feature requests on [GitHub Issues](https://github.com/js-cookie/js-cookie/issues).
+- If reporting a bug, please add a [simplified example](http://sscce.org/).
+
+## Pull requests
+- Create a new topic branch for every separate change you make.
+- Create a test case if you are fixing a bug or implementing an important feature.
+- Make sure the build runs successfully.
+
+## Development
+
+### Tools
+We use the following tools for development:
+
+- [Qunit](http://qunitjs.com/) for tests.
+- [NodeJS](http://nodejs.org/download/) required to run grunt.
+- [Grunt](http://gruntjs.com/getting-started) for task management.
+
+### Getting started 
+Install [NodeJS](http://nodejs.org/).  
+Install globally grunt-cli using the following command:
+
+    $ npm install -g grunt-cli
+
+Browse to the project root directory and install the dev dependencies:
+
+    $ npm install -d
+
+To execute the build and tests run the following command in the root of the project:
+
+    $ grunt
+
+You should see a green message in the console:
+
+    Done, without errors.
+
+### Tests
+You can also run the tests in the browser.  
+Start a test server from the project root:
+
+    $ grunt connect:tests
+
+This will automatically open the test suite at http://127.0.0.1:10000 in the default browser, with livereload enabled.
+
+_Note: we recommend cleaning all the browser cookies before running the tests, that can avoid false positive failures._
+
+### Automatic build
+You can build automatically after a file change using the following command:
+
+    $ grunt watch
+
+## Integration with server-side
+
+js-cookie allows integrating the encoding test suite with solutions written in other server-side languages. To integrate successfully, the server-side solution need to execute the `test/encoding.html` file in it's integration testing routine with a web automation tool, like [Selenium](http://www.seleniumhq.org/). js-cookie test suite exposes an API to make this happen.
+
+### ?integration_baseurl
+
+Specify the base url to pass the cookies into the server through a query string. If `integration_baseurl` query is not present, then js-cookie will assume there's no server.
+
+### window.global_test_results
+
+After the test suite has finished, js-cookie exposes the global `window.global_test_results` property containing an Object Literal that represents the [QUnit's details](http://api.qunitjs.com/QUnit.done/). js-cookie also adds an additional property representing an Array containing the tests data.
+
+### Handling requests
+
+When js-cookie encoding tests are executed, it will request a url in the server through an iframe representing each test being run. js-cookie expects the server to handle the input and return the proper `Set-Cookie` headers in the response. js-cookie will then read the response and verify if the encoding is consistent with js-cookie default encoding mechanism
+
+js-cookie will send some requests to the server from the baseurl in the format `/encoding?name=<cookie>`, where `<cookie>` represents the cookie-name to be read from the request.
+
+The server should handle those requests, internally parsing the cookie from the request and writing it again. It must set an `application/json` content type containing an object literal in the content body with `name` and `value` keys, each representing the cookie-name and cookie-value decoded by the server-side implementation.
+
+If the server fails to respond with this specification in any request, the related QUnit test will fail. This is to make sure the server-side implementation will always be in sync with js-cookie encoding tests for maximum compatibility.
+
+### Projects using it
+
+This hook is being used in the following projects:
+
+* [Java Cookie](https://github.com/js-cookie/java-cookie).

data/node_modules/js-cookie/LICENSE

@@ -0,0 +1,20 @@
+Copyright 2014 Klaus Hartl
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/node_modules/js-cookie/README.md

@@ -0,0 +1,304 @@
+<p align="center">
+  <img src="https://cloud.githubusercontent.com/assets/835857/14581711/ba623018-0436-11e6-8fce-d2ccd4d379c9.gif">
+</p>
+
+# JavaScript Cookie [![Build Status](https://travis-ci.org/js-cookie/js-cookie.svg?branch=master)](https://travis-ci.org/js-cookie/js-cookie) [![Code Climate](https://codeclimate.com/github/js-cookie/js-cookie.svg)](https://codeclimate.com/github/js-cookie/js-cookie) [![jsDelivr Hits](https://data.jsdelivr.com/v1/package/npm/js-cookie/badge?style=rounded)](https://www.jsdelivr.com/package/npm/js-cookie)
+
+A simple, lightweight JavaScript API for handling cookies
+
+* Works in [all](https://saucelabs.com/u/js-cookie) browsers
+* Accepts [any](#encoding) character
+* [Heavily](test) tested
+* No dependency
+* [Unobtrusive](#json) JSON support
+* Supports AMD/CommonJS
+* [RFC 6265](https://tools.ietf.org/html/rfc6265) compliant
+* Useful [Wiki](https://github.com/js-cookie/js-cookie/wiki)
+* Enable [custom encoding/decoding](#converters)
+* **~900 bytes** gzipped!
+
+**If you're viewing this at https://github.com/js-cookie/js-cookie, you're reading the documentation for the master branch.
+[View documentation for the latest release.](https://github.com/js-cookie/js-cookie/tree/latest#readme)**
+
+## Build Status Matrix
+
+[![Selenium Test Status](https://saucelabs.com/browser-matrix/js-cookie.svg)](https://saucelabs.com/u/js-cookie)
+
+## Installation
+
+### Direct download
+
+Download the script [here](https://github.com/js-cookie/js-cookie/blob/latest/src/js.cookie.js) and include it (unless you are packaging scripts somehow else):
+
+```html
+<script src="/path/to/js.cookie.js"></script>
+```
+
+Or include it via [jsDelivr CDN](https://www.jsdelivr.com/package/npm/js-cookie):
+
+```html
+<script src="https://cdn.jsdelivr.net/npm/js-cookie@2/src/js.cookie.min.js"></script>
+```
+
+**Do not include the script directly from GitHub (http://raw.github.com/...).** The file is being served as text/plain and as such being blocked
+in Internet Explorer on Windows 7 for instance (because of the wrong MIME type). Bottom line: GitHub is not a CDN.
+
+### Package Managers
+
+JavaScript Cookie supports [npm](https://www.npmjs.com/package/js-cookie) and [Bower](http://bower.io/search/?q=js-cookie) under the name `js-cookie`.
+
+### Module Loaders
+
+JavaScript Cookie can also be loaded as an AMD, CommonJS or [ES6](https://github.com/js-cookie/js-cookie/issues/233#issuecomment-233187386) module.
+
+## Basic Usage
+
+Create a cookie, valid across the entire site:
+
+```javascript
+Cookies.set('name', 'value');
+```
+
+Create a cookie that expires 7 days from now, valid across the entire site:
+
+```javascript
+Cookies.set('name', 'value', { expires: 7 });
+```
+
+Create an expiring cookie, valid to the path of the current page:
+
+```javascript
+Cookies.set('name', 'value', { expires: 7, path: '' });
+```
+
+Read cookie:
+
+```javascript
+Cookies.get('name'); // => 'value'
+Cookies.get('nothing'); // => undefined
+```
+
+Read all visible cookies:
+
+```javascript
+Cookies.get(); // => { name: 'value' }
+```
+
+Delete cookie:
+
+```javascript
+Cookies.remove('name');
+```
+
+Delete a cookie valid to the path of the current page:
+
+```javascript
+Cookies.set('name', 'value', { path: '' });
+Cookies.remove('name'); // fail!
+Cookies.remove('name', { path: '' }); // removed!
+```
+
+*IMPORTANT! when deleting a cookie, you must pass the exact same path and domain attributes that was used to set the cookie, unless you're relying on the [default attributes](#cookie-attributes).*
+
+*Note: Removing unexisting cookie does not raise any exception nor return any value*
+
+## Namespace conflicts
+
+If there is any danger of a conflict with the namespace `Cookies`, the `noConflict` method will allow you to define a new namespace and preserve the original one. This is especially useful when running the script on third party sites e.g. as part of a widget or SDK.
+
+```javascript
+// Assign the js-cookie api to a different variable and restore the original "window.Cookies"
+var Cookies2 = Cookies.noConflict();
+Cookies2.set('name', 'value');
+```
+
+*Note: The `.noConflict` method is not necessary when using AMD or CommonJS, thus it is not exposed in those environments.*
+
+## JSON
+
+js-cookie provides unobtrusive JSON storage for cookies.
+
+When creating a cookie you can pass an Array or Object Literal instead of a string in the value. If you do so, js-cookie will store the string representation of the object according to `JSON.stringify`:
+
+```javascript
+Cookies.set('name', { foo: 'bar' });
+```
+
+When reading a cookie with the default `Cookies.get` api, you receive the string representation stored in the cookie:
+
+```javascript
+Cookies.get('name'); // => '{"foo":"bar"}'
+```
+
+```javascript
+Cookies.get(); // => { name: '{"foo":"bar"}' }
+```
+
+When reading a cookie with the `Cookies.getJSON` api, you receive the parsed representation of the string stored in the cookie according to `JSON.parse`:
+
+```javascript
+Cookies.getJSON('name'); // => { foo: 'bar' }
+```
+
+```javascript
+Cookies.getJSON(); // => { name: { foo: 'bar' } }
+```
+
+*Note: To support IE6-7 ([and IE 8 compatibility mode](http://stackoverflow.com/questions/4715373/json-object-undefined-in-internet-explorer-8)) you need to include the JSON-js polyfill: https://github.com/douglascrockford/JSON-js*
+
+## Encoding
+
+This project is [RFC 6265](http://tools.ietf.org/html/rfc6265#section-4.1.1) compliant. All special characters that are not allowed in the cookie-name or cookie-value are encoded with each one's UTF-8 Hex equivalent using [percent-encoding](http://en.wikipedia.org/wiki/Percent-encoding).  
+The only character in cookie-name or cookie-value that is allowed and still encoded is the percent `%` character, it is escaped in order to interpret percent input as literal.  
+Please note that the default encoding/decoding strategy is meant to be interoperable [only between cookies that are read/written by js-cookie](https://github.com/js-cookie/js-cookie/pull/200#discussion_r63270778). To override the default encoding/decoding strategy you need to use a [converter](#converters).
+
+## Cookie Attributes
+
+Cookie attributes defaults can be set globally by setting properties of the `Cookies.defaults` object or individually for each call to `Cookies.set(...)` by passing a plain object in the last argument. Per-call attributes override the default attributes.
+
+### expires
+
+Define when the cookie will be removed. Value can be a [`Number`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number) which will be interpreted as days from time of creation or a [`Date`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date) instance. If omitted, the cookie becomes a session cookie.
+
+To create a cookie that expires in less than a day, you can check the [FAQ on the Wiki](https://github.com/js-cookie/js-cookie/wiki/Frequently-Asked-Questions#expire-cookies-in-less-than-a-day).
+
+**Default:** Cookie is removed when the user closes the browser.
+
+**Examples:**
+
+```javascript
+Cookies.set('name', 'value', { expires: 365 });
+Cookies.get('name'); // => 'value'
+Cookies.remove('name');
+```
+
+### path
+
+A [`String`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String) indicating the path where the cookie is visible.
+
+**Default:** `/`
+
+**Examples:**
+
+```javascript
+Cookies.set('name', 'value', { path: '' });
+Cookies.get('name'); // => 'value'
+Cookies.remove('name', { path: '' });
+```
+
+**Note regarding Internet Explorer:**
+
+> Due to an obscure bug in the underlying WinINET InternetGetCookie implementation, IE’s document.cookie will not return a cookie if it was set with a path attribute containing a filename.
+
+(From [Internet Explorer Cookie Internals (FAQ)](http://blogs.msdn.com/b/ieinternals/archive/2009/08/20/wininet-ie-cookie-internals-faq.aspx))
+
+This means one cannot set a path using `path: window.location.pathname` in case such pathname contains a filename like so: `/check.html` (or at least, such cookie cannot be read correctly).
+
+### domain
+
+A [`String`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String) indicating a valid domain where the cookie should be visible. The cookie will also be visible to all subdomains.
+
+**Default:** Cookie is visible only to the domain or subdomain of the page where the cookie was created, except for Internet Explorer (see below).
+
+**Examples:**
+
+Assuming a cookie that is being created on `site.com`:
+
+```javascript
+Cookies.set('name', 'value', { domain: 'subdomain.site.com' });
+Cookies.get('name'); // => undefined (need to read at 'subdomain.site.com')
+```
+
+**Note regarding Internet Explorer default behavior:**
+
+> Q3: If I don’t specify a DOMAIN attribute (for) a cookie, IE sends it to all nested subdomains anyway?  
+> A: Yes, a cookie set on example.com will be sent to sub2.sub1.example.com.  
+> Internet Explorer differs from other browsers in this regard.
+
+(From [Internet Explorer Cookie Internals (FAQ)](http://blogs.msdn.com/b/ieinternals/archive/2009/08/20/wininet-ie-cookie-internals-faq.aspx))
+
+This means that if you omit the `domain` attribute, it will be visible for a subdomain in IE.
+
+### secure
+
+Either `true` or `false`, indicating if the cookie transmission requires a secure protocol (https).
+
+**Default:** No secure protocol requirement.
+
+**Examples:**
+
+```javascript
+Cookies.set('name', 'value', { secure: true });
+Cookies.get('name'); // => 'value'
+Cookies.remove('name');
+```
+
+## Converters
+
+### Read
+
+Create a new instance of the api that overrides the default decoding implementation.  
+All get methods that rely in a proper decoding to work, such as `Cookies.get()` and `Cookies.get('name')`, will run the converter first for each cookie.  
+The returning String will be used as the cookie value.
+
+Example from reading one of the cookies that can only be decoded using the `escape` function:
+
+```javascript
+document.cookie = 'escaped=%u5317';
+document.cookie = 'default=%E5%8C%97';
+var cookies = Cookies.withConverter(function (value, name) {
+    if ( name === 'escaped' ) {
+        return unescape(value);
+    }
+});
+cookies.get('escaped'); // 北
+cookies.get('default'); // 北
+cookies.get(); // { escaped: '北', default: '北' }
+```
+
+### Write
+
+Create a new instance of the api that overrides the default encoding implementation:
+
+```javascript
+Cookies.withConverter({
+    read: function (value, name) {
+        // Read converter
+    },
+    write: function (value, name) {
+        // Write converter
+    }
+});
+```
+
+## Server-side integration
+
+Check out the [Servers Docs](SERVER_SIDE.md)
+
+## Contributing
+
+Check out the [Contributing Guidelines](CONTRIBUTING.md)
+
+## Security
+
+For vulnerability reports, send an e-mail to `jscookieproject at gmail dot com`
+
+## Manual release steps
+
+* Increment the "version" attribute of `package.json`
+* Increment the version number in the `src/js.cookie.js` file
+* If `major` bump, update jsDelivr CDN major version link on README
+* Commit with the message "Release version x.x.x"
+* Create version tag in git
+* Create a github release and upload the minified file
+* Change the `latest` tag pointer to the latest commit
+  * `git tag -f latest`
+  * `git push <remote> :refs/tags/latest`
+  * `git push origin master --tags`
+* Release on npm
+
+## Authors
+
+* [Klaus Hartl](https://github.com/carhartl)
+* [Fagner Brack](https://github.com/FagnerMartinsBrack)
+* And awesome [contributors](https://github.com/js-cookie/js-cookie/graphs/contributors)

data/node_modules/js-cookie/SERVER_SIDE.md

@@ -0,0 +1,107 @@
+# Server-side integration
+
+There are some servers that are not compliant with the [RFC 6265](http://tools.ietf.org/html/rfc6265). For those, some characters that are not encoded by JavaScript Cookie might be treated differently.
+
+Here we document the most important server-side peculiarities and their workarounds. Feel free to send a [Pull Request](https://github.com/js-cookie/js-cookie/blob/master/CONTRIBUTING.md#pull-requests) if you see something that can be improved.
+
+*Disclaimer: This documentation is entirely based on community provided information. The examples below should be used only as a reference.*
+
+## PHP
+
+In PHP, `setcookie()` function encodes cookie values using `urlencode()` function, which applies `%`-encoding but also encodes spaces as `+` signs, [for historical reasons](http://php.net/manual/en/function.urlencode.php#function.urlencode). When cookies are read back via `$_COOKIE` or `filter_input(INPUT_COOKIE)`, they would go trough a decoding process which decodes `%`-encoded sequences and also converts `+` signs back to spaces. However, the plus (`+`) sign is valid cookie character by itself, which means that libraries that adhere to standards will interpret `+` signs differently to PHP.
+
+This presents two types of problems:
+
+1. PHP writes a cookie via `setcookie()` and all spaces get converted to `+` signs. JavaScript Cookie read `+` signs and uses them literally, since it is a valid cookie character.
+2. JavaScript Cookie writes a cookie with a value that contains `+` signs and stores it as is, since it is a valid cookie character. PHP read a cookie and converts `+` signs to spaces.
+
+To make both PHP and JavaScript Cookie play nicely together?
+
+**In PHP**, use `setrawcookie()` instead of `setcookie()`:
+
+```php
+setrawcookie($name, rawurlencode($value));
+```
+
+**In JavaScript**, use a custom converter.
+
+**Example**:
+
+```javascript
+var PHPCookies = Cookies.withConverter({
+    write: function (value) {
+        // Encode all characters according to the "encodeURIComponent" spec
+        return encodeURIComponent(value)
+            // Revert the characters that are unnecessarly encoded but are
+            // allowed in a cookie value, except for the plus sign (%2B)
+            .replace(/%(23|24|26|3A|3C|3E|3D|2F|3F|40|5B|5D|5E|60|7B|7D|7C)/g, decodeURIComponent);
+    },
+    read: function (value) {
+        return value
+            // Decode the plus sign to spaces first, otherwise "legit" encoded pluses
+            // will be replaced incorrectly
+            .replace(/\+/g, ' ')
+            // Decode all characters according to the "encodeURIComponent" spec
+            .replace(/(%[0-9A-Z]{2})+/g, decodeURIComponent);
+    }
+});
+```
+
+Rack seems to have [a similar problem](https://github.com/js-cookie/js-cookie/issues/70#issuecomment-132503017).
+
+## Tomcat
+
+### Version >= 7.x
+
+It seems that there is a situation where Tomcat does not [read the parens correctly](https://github.com/js-cookie/js-cookie/issues/92#issue-107743407). To fix this you need to write a custom write converter.
+
+**Example**:
+
+```javascript
+var TomcatCookies = Cookies.withConverter({
+  write: function (value) {
+      // Encode all characters according to the "encodeURIComponent" spec
+      return encodeURIComponent(value)
+          // Revert the characters that are unnecessarly encoded but are
+          // allowed in a cookie value
+          .replace(/%(23|24|26|2B|3A|3C|3E|3D|2F|3F|40|5B|5D|5E|60|7B|7D|7C)/g, decodeURIComponent)
+          // Encode the parens that are interpreted incorrectly by Tomcat
+          .replace(/[\(\)]/g, escape);
+  }
+});
+```
+
+### Version >= 8.0.15
+
+Since Tomcat 8.0.15, it is possible to configure RFC 6265 compliance by changing your `conf/context.xml` file and adding the new [CookieProcessor](https://tomcat.apache.org/tomcat-8.0-doc/config/cookie-processor.html) nested inside the Context element. It would be like this:
+
+```xml
+<Context>
+  <CookieProcessor className="org.apache.tomcat.util.http.Rfc6265CookieProcessor"/>
+</context>
+```
+And you're all done.
+
+Alternatively, you can check the [Java Cookie](https://github.com/js-cookie/java-cookie) project, which integrates nicely with JavaScript Cookie.
+
+## JBoss 7.1.1
+
+It seems that the servlet implementation of JBoss 7.1.1 [does not read some characters correctly](https://github.com/js-cookie/js-cookie/issues/70#issuecomment-148944674), even though they are allowed as per [RFC 6265](https://tools.ietf.org/html/rfc6265#section-4.1.1). To fix this you need to write a custom converter to send those characters correctly.
+
+**Example**:
+
+```javascript
+var JBossCookies = Cookies.withConverter({
+    write: function (value) {
+        // Encode all characters according to the "encodeURIComponent" spec
+        return encodeURIComponent(value)
+            // Revert the characters that are unnecessarly encoded but are
+            // allowed in a cookie value
+            .replace(/%(23|24|26|2B|3A|3C|3E|3D|2F|3F|40|5B|5D|5E|60|7B|7D|7C)/g, decodeURIComponent)
+            // Encode again the characters that are not allowed in JBoss 7.1.1, like "[" and "]":
+            .replace(/[\[\]]/g, encodeURIComponent);
+    }
+});
+```
+
+Alternatively, you can check the [Java Cookie](https://github.com/js-cookie/java-cookie) project, which integrates nicely with JavaScript Cookie.

data/node_modules/js-cookie/package.json

@@ -0,0 +1,49 @@
+{
+  "name": "js-cookie",
+  "version": "2.2.0",
+  "description": "A simple, lightweight JavaScript API for handling cookies",
+  "main": "src/js.cookie.js",
+  "directories": {
+    "test": "test"
+  },
+  "keywords": [
+    "jquery-plugin",
+    "cookie",
+    "cookies",
+    "browser",
+    "amd",
+    "commonjs",
+    "client",
+    "js-cookie",
+    "browserify"
+  ],
+  "scripts": {
+    "test": "grunt test"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git://github.com/js-cookie/js-cookie.git"
+  },
+  "files": [
+    "src/**/*.js",
+    "SERVER_SIDE.md",
+    "CONTRIBUTING.md"
+  ],
+  "author": "Klaus Hartl",
+  "license": "MIT",
+  "devDependencies": {
+    "grunt": "1.0.1",
+    "grunt-compare-size": "0.4.2",
+    "grunt-contrib-connect": "1.0.2",
+    "grunt-contrib-jshint": "1.1.0",
+    "grunt-contrib-nodeunit": "1.0.0",
+    "grunt-contrib-qunit": "2.0.0",
+    "grunt-contrib-uglify": "2.3.0",
+    "grunt-contrib-watch": "1.0.0",
+    "grunt-jscs": "3.0.1",
+    "grunt-saucelabs": "9.0.0",
+    "gzip-js": "0.3.2",
+    "qunitjs": "1.23.1",
+    "requirejs": "2.3.5"
+  }
+}

data/node_modules/js-cookie/src/js.cookie.js

@@ -0,0 +1,165 @@
+/*!
+ * JavaScript Cookie v2.2.0
+ * https://github.com/js-cookie/js-cookie
+ *
+ * Copyright 2006, 2015 Klaus Hartl & Fagner Brack
+ * Released under the MIT license
+ */
+;(function (factory) {
+	var registeredInModuleLoader = false;
+	if (typeof define === 'function' && define.amd) {
+		define(factory);
+		registeredInModuleLoader = true;
+	}
+	if (typeof exports === 'object') {
+		module.exports = factory();
+		registeredInModuleLoader = true;
+	}
+	if (!registeredInModuleLoader) {
+		var OldCookies = window.Cookies;
+		var api = window.Cookies = factory();
+		api.noConflict = function () {
+			window.Cookies = OldCookies;
+			return api;
+		};
+	}
+}(function () {
+	function extend () {
+		var i = 0;
+		var result = {};
+		for (; i < arguments.length; i++) {
+			var attributes = arguments[ i ];
+			for (var key in attributes) {
+				result[key] = attributes[key];
+			}
+		}
+		return result;
+	}
+
+	function init (converter) {
+		function api (key, value, attributes) {
+			var result;
+			if (typeof document === 'undefined') {
+				return;
+			}
+
+			// Write
+
+			if (arguments.length > 1) {
+				attributes = extend({
+					path: '/'
+				}, api.defaults, attributes);
+
+				if (typeof attributes.expires === 'number') {
+					var expires = new Date();
+					expires.setMilliseconds(expires.getMilliseconds() + attributes.expires * 864e+5);
+					attributes.expires = expires;
+				}
+
+				// We're using "expires" because "max-age" is not supported by IE
+				attributes.expires = attributes.expires ? attributes.expires.toUTCString() : '';
+
+				try {
+					result = JSON.stringify(value);
+					if (/^[\{\[]/.test(result)) {
+						value = result;
+					}
+				} catch (e) {}
+
+				if (!converter.write) {
+					value = encodeURIComponent(String(value))
+						.replace(/%(23|24|26|2B|3A|3C|3E|3D|2F|3F|40|5B|5D|5E|60|7B|7D|7C)/g, decodeURIComponent);
+				} else {
+					value = converter.write(value, key);
+				}
+
+				key = encodeURIComponent(String(key));
+				key = key.replace(/%(23|24|26|2B|5E|60|7C)/g, decodeURIComponent);
+				key = key.replace(/[\(\)]/g, escape);
+
+				var stringifiedAttributes = '';
+
+				for (var attributeName in attributes) {
+					if (!attributes[attributeName]) {
+						continue;
+					}
+					stringifiedAttributes += '; ' + attributeName;
+					if (attributes[attributeName] === true) {
+						continue;
+					}
+					stringifiedAttributes += '=' + attributes[attributeName];
+				}
+				return (document.cookie = key + '=' + value + stringifiedAttributes);
+			}
+
+			// Read
+
+			if (!key) {
+				result = {};
+			}
+
+			// To prevent the for loop in the first place assign an empty array
+			// in case there are no cookies at all. Also prevents odd result when
+			// calling "get()"
+			var cookies = document.cookie ? document.cookie.split('; ') : [];
+			var rdecode = /(%[0-9A-Z]{2})+/g;
+			var i = 0;
+
+			for (; i < cookies.length; i++) {
+				var parts = cookies[i].split('=');
+				var cookie = parts.slice(1).join('=');
+
+				if (!this.json && cookie.charAt(0) === '"') {
+					cookie = cookie.slice(1, -1);
+				}
+
+				try {
+					var name = parts[0].replace(rdecode, decodeURIComponent);
+					cookie = converter.read ?
+						converter.read(cookie, name) : converter(cookie, name) ||
+						cookie.replace(rdecode, decodeURIComponent);
+
+					if (this.json) {
+						try {
+							cookie = JSON.parse(cookie);
+						} catch (e) {}
+					}
+
+					if (key === name) {
+						result = cookie;
+						break;
+					}
+
+					if (!key) {
+						result[name] = cookie;
+					}
+				} catch (e) {}
+			}
+
+			return result;
+		}
+
+		api.set = api;
+		api.get = function (key) {
+			return api.call(api, key);
+		};
+		api.getJSON = function () {
+			return api.apply({
+				json: true
+			}, [].slice.call(arguments));
+		};
+		api.defaults = {};
+
+		api.remove = function (key, attributes) {
+			api(key, '', extend(attributes, {
+				expires: -1
+			}));
+		};
+
+		api.withConverter = init;
+
+		return api;
+	}
+
+	return init(function () {});
+}));

data/source/javascripts/gdpr/cookie_consent.js

@@ -0,0 +1,20 @@
+//= require js-cookie/src/js.cookie
+
+window.addEventListener('load', function() {
+  var gdprCookieConsent = document.querySelector('.js-gdpr__cookie_consent');
+
+  if(!gdprCookieConsent) return;
+  var COOKIE_KEY = 'gdpr.cookie_consent.ok'
+
+  var remove = function() {
+    if(gdprCookieConsent.parentNode) gdprCookieConsent.parentNode.removeChild(gdprCookieConsent);
+  }
+
+  if(Cookies.get(COOKIE_KEY) === 'true') remove()
+  else {
+    gdprCookieConsent.querySelector('.js-gdpr__cookie_consent__buttons__ok').addEventListener('click', function() {
+      Cookies.set(COOKIE_KEY, true, {path: '/', expires: 365});
+      remove()
+    });
+  }
+});

data/source/stylesheets/gdpr/cookie_consent.sass

@@ -0,0 +1,33 @@
+.gdpr__cookie_consent
+  position: fixed
+  z-index: 999
+  right: 0
+  bottom: 0
+  left: 0
+  padding: 0 20px
+  text-align: center
+  border-top: 1px solid #ccc
+  background: #fff
+
+  @media only screen and (max-width : 480px)
+    font-size: 12px
+    position: initial
+
+  &__text
+    display: inline-block
+    padding: 20px 160px
+
+    @media only screen and (max-width : 480px)
+      padding: 20px 0
+
+  &__buttons
+    position: absolute
+    right: 10px
+    top: 12px
+
+    @media only screen and (max-width : 480px)
+      position: initial
+      margin-bottom: 10px
+
+    &__ok
+      padding: 15px 21px 15px !important

metadata

@@ -0,0 +1,111 @@
+--- !ruby/object:Gem::Specification
+name: middleman-gdpr
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Arnaud Levy
+- Pierre-André Boissinot
+- Julien Dargelos
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2018-07-02 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: middleman-core
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: middleman-sprockets
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: Adds a GDPR cookie consent and provides a simple checklist
+email:
+- alevy@lespoupees.paris
+- paboissinot@lespoupees.paris
+- contact@juliendargelos.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- LICENSE
+- README.md
+- Rakefile
+- lib/middleman-gdpr.rb
+- lib/middleman-gdpr/extension.rb
+- lib/middleman-gdpr/version.rb
+- lib/middleman_extension.rb
+- locales/de.yml
+- locales/en.yml
+- locales/es.yml
+- locales/fr.yml
+- locales/it.yml
+- locales/zh.yml
+- node_modules/js-cookie/CONTRIBUTING.md
+- node_modules/js-cookie/LICENSE
+- node_modules/js-cookie/README.md
+- node_modules/js-cookie/SERVER_SIDE.md
+- node_modules/js-cookie/package.json
+- node_modules/js-cookie/src/js.cookie.js
+- source/javascripts/gdpr/cookie_consent.js
+- source/stylesheets/gdpr/cookie_consent.sass
+homepage: https://github.com/lespoupeesrusses/middleman-gdpr
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.7.6
+signing_key: 
+specification_version: 4
+summary: Helps getting your Middleman website GDPR compliant
+test_files: []