meta-tags 2.0.0 → 2.1.0

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    NmY1YmU5YTM0ZjQwYzBkODRkZmViODlmMTI1NjljYzdkMzcwMzljYg==
-  data.tar.gz: !binary |-
-    OGQ1ZjE5YzFjMjcxNzM1OTliZDNhY2MxMDU0M2ExMTkxOTMzZTkxMQ==
+SHA1:
+  metadata.gz: 31cca6e8ca34c077fb3c456043bbf68954ba74e6
+  data.tar.gz: 76a7bfab6224589500465629cd82c2148537268c
 SHA512:
-  metadata.gz: !binary |-
-    MjA0OTRkMGJjMDc1ZGE1NDk5OTExZGRmMDVhZjNiZDFmMTgzYjYxYTYzOWYw
-    N2YxYjc4YjI4ZDc3ZjIyYjBmNWJiNjBhNzI2MmY3MmRlMDliMjU2ZTQ5Y2My
-    MmM2YTJmZjUzMzFjYWFlMDQxMzJlZmYxMWVkZTdlYjFjMjAwY2U=
-  data.tar.gz: !binary |-
-    M2FmMmJlZGZhNTU0YWIwMTUzYzZhNGY5OWQxNDA4MGYyOTZlOTUzMzM4NTg4
-    YzU4MGVhZTNiNzk0NzYwNDQ5NTUwYjM2NTA5MTA3YjQxMzI1MWVhZGUwY2Vl
-    NjY5MjVlNTZhYmY1MjNhNjA1MWQ0ZjVkMTU2NjFkZWE2OTI4NWI=
+  metadata.gz: bf8d09a4550dbd500c3296845b22d017d0f7689f78b9cfe2046ee14ec7f564492cbd2a625f319527a26aabc8e0df7a0650f8b509fa451fb9c7f483f4e1d4f955
+  data.tar.gz: 093c8a4f7d2d6065d87dd9bd0a1deba9f43bc1865ef93a44216c7fea1704bcb45f60b48a3a59984ddbeb746f6080e159536ec0b42e569f2ef17ba0ddaf04eb25

data/.gitignore

@@ -2,5 +2,6 @@
 .DS_Store
 .bundle
 Gemfile.lock
+coverage
 doc
 pkg

data/.rspec

@@ -0,0 +1,3 @@
+--color
+--warnings
+--require spec_helper

data/.ruby-version

@@ -1 +1 @@
-ruby-2.1.1
+ruby-2.2

data/.travis.yml

@@ -1,27 +1,21 @@
 rvm:
-  - ree
-  - 1.8.7
-  - 1.9.3
   - 2.0.0
-  - 2.1.0
+  - 2.1.7
+  - 2.2.3
 
 env:
   - "RAILS_VERSION=3.1.0"
   - "RAILS_VERSION=3.2.0"
   - "RAILS_VERSION=4.0.0"
   - "RAILS_VERSION=4.1.0"
+  - "RAILS_VERSION=4.2.0"
 
 matrix:
-  exclude:
-    - rvm: ree
-      env: "RAILS_VERSION=4.0.0"
-    - rvm: ree
-      env: "RAILS_VERSION=4.1.0"
-    - rvm: 1.8.7
-      env: "RAILS_VERSION=4.0.0"
-    - rvm: 1.8.7
-      env: "RAILS_VERSION=4.1.0"
 
 notifications:
   recipients:
     - kpumuk@kpumuk.info
+
+addons:
+  code_climate:
+    repo_token: "8792cbc0d1780830ddd3dd7eb1c25f09f386ba8f04449ad830039469406a6ab3"

data/CHANGELOG.md

@@ -1,3 +1,21 @@
+## 2.1.0 (October 6, 2015)
+
+Changes:
+
+  - Ruby < 2.0 is not longer supported
+
+Features:
+
+  - Added charset meta tag
+  - Added ability to configure limits for title, description, keywords
+  - Added OpenSearch links support
+  - Added icon links support
+  - Alternate links can now be generated for RSS or mobile versions
+
+Bugfixes
+  - Generate `<meta name=""/>` instead of `<meta property=""/>` for custom meta tags
+  - Double HTML escaping in meta tags
+
 ## 2.0.0 (April 15, 2014)
 
 Features:

data/Gemfile

@@ -6,3 +6,8 @@ gemspec
 if ENV['RAILS_VERSION']
   gem 'actionpack', "~> #{ENV['RAILS_VERSION']}"
 end
+
+group :test do
+  gem 'codeclimate-test-reporter', require: false
+  gem 'rspec-html-matchers'
+end

data/README.md

@@ -1,8 +1,9 @@
 # MetaTags: a gem to make your Rails application SEO-friendly
 
-[![Travis-CI build status](https://secure.travis-ci.org/kpumuk/meta-tags.png)](http://travis-ci.org/kpumuk/meta-tags)
+[![Travis-CI build status](https://secure.travis-ci.org/kpumuk/meta-tags.svg)](http://travis-ci.org/kpumuk/meta-tags)
 [![Gem Version](https://badge.fury.io/rb/meta-tags.svg)](http://badge.fury.io/rb/meta-tags)
 [![Code Climate](https://codeclimate.com/github/kpumuk/meta-tags.png)](https://codeclimate.com/github/kpumuk/meta-tags)
+[![Coverage](https://codeclimate.com/github/kpumuk/meta-tags/coverage.png)](https://codeclimate.com/github/kpumuk/meta-tags)
 
 Search Engine Optimization (SEO) plugin for Ruby on Rails applications.
 
@@ -11,6 +12,8 @@ Search Engine Optimization (SEO) plugin for Ruby on Rails applications.
 MetaTags master branch now fully supports Rails 3.0+ and is not backward
 compatible. Latest version fully compatible with 2.x is 1.2.3.
 
+Ruby versions older than 2.0.0 are no longer officially supported.
+
 ## Installation
 
 Add the "meta-tags" gem to your `Gemfile`.
@@ -19,6 +22,20 @@ Add the "meta-tags" gem to your `Gemfile`.
 
 And run `bundle install` command.
 
+## Configuration
+
+MetaTags follows best-practices for meta tags. Although default limits for
+truncation have recommended values, you can change them to reflect your own
+preferences. In order to do that, you can create an initializer
+`config/initializers/meta_tags.rb`, with following code:
+
+    MetaTags.configure do |c|
+      c.title_limit        = 70
+      c.description_limit  = 160
+      c.keywords_limit     = 255
+      c.keywords_separator = ', '
+    end
+
 ## SEO Basics and MetaTags
 
 ### Titles
@@ -27,11 +44,11 @@ Page titles are very important for Search engines. The titles in the
 browser are displayed in the title bar. The search engines would look at
 the this title bar to determine what the page is all about.
 
-    set_meta_tags :title => 'Member Login'
+    set_meta_tags title: 'Member Login'
     # <title>Some Page Title</title>
-    set_meta_tags :site => 'Site Title', :title => 'Member Login'
+    set_meta_tags site: 'Site Title', title: 'Member Login'
     # <title>Site Title | Page Title</title>
-    set_meta_tags :site => 'Site Title', :title => 'Member Login', :reverse => true
+    set_meta_tags site: 'Site Title', title: 'Member Login', reverse: true
     # <title>Page Title | Site Title</title>
 
 Recommended title tag length: up to <b>70 characters</b>, <b>10 words</b>.
@@ -43,7 +60,7 @@ browsers as that of titles. But these descriptions may be displayed by
 some search engines. They are used to describe the contents of a page in
 2 or 3 sentences.
 
-    set_meta_tags :description => "All text about keywords, other keywords"
+    set_meta_tags description: "All text about keywords, other keywords"
     # <meta name="description" content="All text about keywords, other keywords" />
 
 Recommended description tag length: up to <b>160 characters</b>.
@@ -54,7 +71,7 @@ Meta keywords tag are used to place your keywords that you think a
 surfer would search in Search engines. Repeating keywords unnecessarily
 would be considered spam and you may get permanently banned from SERP's
 
-    set_meta_tags :keywords => %w[keyword1 Keyword2 KeyWord3]
+    set_meta_tags keywords: %w[keyword1 Keyword2 KeyWord3]
     # <meta name="keywords" content="keyword1, keyword2, keyword3" />
 
 Recommended keywords tag length: up to <b>255 characters</b>, <b>20 words</b>.
@@ -64,9 +81,9 @@ Recommended keywords tag length: up to <b>255 characters</b>, <b>20 words</b>.
 By using the noindex meta tag, you can signal to search engines to not
 include specific pages in their indexes.
 
-    set_meta_tags :noindex => true
+    set_meta_tags noindex: true
     # <meta name="robots" content="noindex" />
-    set_meta_tags :noindex => 'googlebot'
+    set_meta_tags noindex: 'googlebot'
     # <meta name="googlebot" content="noindex" />
 
 This is useful for pages like login, password reset, privacy policy, etc.
@@ -83,9 +100,9 @@ page. It's entirely likely that a robot might find the same links on some
 other page without a nofollow (perhaps on some other site), and so
 still arrives at your undesired page.
 
-    set_meta_tags :nofollow => true
+    set_meta_tags nofollow: true
     # <meta name="robots" content="nofollow" />
-    set_meta_tags :nofollow => 'googlebot'
+    set_meta_tags nofollow: 'googlebot'
     # <meta name="googlebot" content="nofollow" />
 
 Further reading:
@@ -99,7 +116,7 @@ Canonical link element tells a search engine what is the canonical or main URL
 for a content which have multiple URLs. The search engine will always return
 that URL, and link popularity and authority will be applied to that URL.
 
-    set_meta_tags :canonical => "http://yoursite.com/canonical/url"
+    set_meta_tags canonical: "http://yoursite.com/canonical/url"
     # <link rel="canonical" href="http://yoursite.com/canonical/url" />
 
 Further reading:
@@ -107,11 +124,33 @@ Further reading:
 * [About rel="canonical"](http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139394)
 * [Canonicalization](http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066)
 
+### Icon
+
+A favicon (short for Favorite icon), also known as a shortcut icon, Web site
+icon, tab icon or bookmark icon, is a file containing one or more small icons,
+most commonly 16×16 pixels, associated with a particular website or web page.
+
+    set_meta_tags icon: '/favicon.ico'
+    # <link rel="icon" href="/favicon.ico" type="image/x-icon" />
+    set_meta_tags icon: '/favicon.png', type: 'image/png'
+    # <link rel="icon" href="/favicon.png" type="image/png" />
+    set_meta_tags icon: [
+      { href: '/images/icons/icon_96.png', sizes: '32x32 96x96', type: 'image/png' },
+      { href: '/images/icons/icon_itouch_precomp_32.png', rel: 'apple-touch-icon-precomposed', sizes: '32x32', type: 'image/png' },
+    ]
+    # <link rel="icon" href="/images/icons/icon_96.png" type="image/png" sizes="32x32 96x96" />
+    # <link rel="apple-touch-icon-precomposed" href="/images/icons/icon_itouch_precomp_32.png" type="image/png" sizes="32x32" />
+
+Further reading:
+
+* [Favicon](https://www.wikiwand.com/en/Favicon)
+* [Touch Icons](https://mathiasbynens.be/notes/touch-icons)
+
 ### Author links
 
 Link to your Google+ profile using rel="author"
 
-    set_meta_tags :author => "http://yourgplusprofile.com/profile/url"
+    set_meta_tags author: "http://yourgplusprofile.com/profile/url"
     # <link rel="author" href="http://yourgplusprofile.com/profile/url" />
 
 Further reading:
@@ -122,29 +161,38 @@ Further reading:
 
 Link to your Google+ profile using rel="publisher"
 
-    set_meta_tags :publisher => "http://yourgplusprofile.com/profile/url"
+    set_meta_tags publisher: "http://yourgplusprofile.com/profile/url"
     # <link rel="publisher" href="http://yourgplusprofile.com/profile/url" />
 
 * [Link to your website](https://support.google.com/plus/answer/1713826?hl=en)
 * [The Difference Between rel=author & rel=publisher](http://www.websitemagazine.com/content/blogs/posts/archive/2013/02/05/the-difference-between-rel-author-amp-rel-publisher.aspx)
 
-### Multi-regional and multilingual URLs
+### Multi-regional and multilingual URLs, RSS and mobile links
 
-Alternate link elements tell a search engine when there is content that's translated or targeted to
-users in a certain region.
+Alternate link elements tell a search engine when there is content that's
+translated or targeted to users in a certain region.
 
-    set_meta_tags :alternate => { "fr" => "http://yoursite.fr/alternate/url" }
+    set_meta_tags alternate: { "fr" => "http://yoursite.fr/alternate/url" }
     # <link rel="alternate" href="http://yoursite.fr/alternate/url" hreflang="fr" />
 
-    set_meta_tags :alternate => { "fr" => "http://yoursite.fr/alternate/url",
-                                  "de" => "http://yoursite.de/alternate/url" }
+    set_meta_tags alternate: { "fr" => "http://yoursite.fr/alternate/url",
+                               "de" => "http://yoursite.de/alternate/url" }
     # <link rel="alternate" href="http://yoursite.fr/alternate/url" hreflang="en" />
     # <link rel="alternate" href="http://yoursite.de/alternate/url" hreflang="de" />
 
+If you need more than just multi-lingual links, you can use an alternative syntax:
+
+    set_meta_tags alternate: [
+        { href: 'http://example.fr/base/url', hreflang: 'fr' },
+        { href: 'http://example.com/feed.rss', type: 'application/rss+xml', title: 'RSS' },
+        { href: 'http://m.example.com/page-1', media: 'only screen and (max-width: 640px)'},
+      ]
+
 Further reading:
 
 * [Multi-regional and multilingual sites](https://support.google.com/webmasters/answer/182192)
 * [About rel="alternate" hreflang="x"](http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=189077)
+* [Separate URLs](https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/separate-urls#annotation-in-the-html)
 
 ### Pagination links
 
@@ -152,9 +200,9 @@ Previous and next links indicate indicate the relationship between individual
 URLs. Using these attributes is a strong hint to Google that you want us to
 treat these pages as a logical sequence.
 
-    set_meta_tags :prev => "http://yoursite.com/url?page=1"
+    set_meta_tags prev: "http://yoursite.com/url?page=1"
     # <link rel="prev" href="http://yoursite.com/url?page=1" />
-    set_meta_tags :next => "http://yoursite.com/url?page=3"
+    set_meta_tags next: "http://yoursite.com/url?page=3"
     # <link rel="next" href="http://yoursite.com/url?page=3" />
 
 Further reading:
@@ -171,9 +219,9 @@ refreshed, by including the alternative URL in the content parameter. By
 setting the refresh time interval to zero (or a very low value), this allows
 meta refresh to be used as a method of URL redirection.
 
-    set_meta_tags :refresh => 5
+    set_meta_tags refresh: 5
     # <meta content="5" http-equiv="refresh" />
-    set_meta_tags :refresh => '5;url=http://example.com'
+    set_meta_tags refresh: '5;url=http://example.com'
     # <meta content="5;url=http://example.com" http-equiv="refresh" />
 
 Further reading:
@@ -181,14 +229,30 @@ Further reading:
 * [Meta refresh](http://en.wikipedia.org/wiki/Meta_refresh)
 * [What is the Meta Refresh Tag](http://webdesign.about.com/od/metataglibraries/a/aa080300a.htm)
 
+
+### Open Search
+
+Open Search link element to describe a search engine in a standard and accessible format.
+
+    set_meta_tags open_search: {
+      title: "Open Search",
+      href:  "/opensearch.xml"
+    }
+    # <link href="/opensearch.xml" rel="search" title="Open Search" type="application/opensearchdescription+xml" />
+
+Further reading:
+
+* [OpenSearch specs](http://www.opensearch.org/Specifications/OpenSearch/1.1)
+* [OpenSearch wiki](http://en.wikipedia.org/wiki/OpenSearch)
+
 ### Hashes
 
 Any namespace can be built just passing any symbol name and a Hash. For example:
 
-    set_meta_tags :foo => {
-      :bar => "lorem",
-      :baz => {
-        :qux => "ipsum"
+    set_meta_tags foo: {
+      bar: "lorem",
+      baz: {
+        qux: "ipsum"
       }
     }
     # <meta property="foo:bar" content="lorem"/>
@@ -198,8 +262,8 @@ Any namespace can be built just passing any symbol name and a Hash. For example:
 
 Repeated meta tags can be built just using an Array inside a Hash. For example:
 
-    set_meta_tags :og => {
-        :image = ["http://example.com/rock.jpg", "http://example.com/rock2.jpg"]
+    set_meta_tags og: {
+        image: ["http://example.com/rock.jpg", "http://example.com/rock2.jpg"]
     }
     #<meta property="og:image" content="http://example.com/rock.jpg" />
     #<meta property="og:image" content="http://example.com/rock2.jpg" />
@@ -211,14 +275,14 @@ protocol `<meta>` tags to your webpages. The tags allow you to specify
 structured information about your web pages. The more information you provide, the more opportunities your web pages can be surfaced within Facebook today
 and in the future. Here's an example for a movie page:
 
-    set_meta_tags :og => {
-      :title    => 'The Rock',
-      :type     => 'video.movie',
-      :url      => 'http://www.imdb.com/title/tt0117500/',
-      :image    => 'http://ia.media-imdb.com/rock.jpg',
-      :video    => {
-        :director => 'http://www.imdb.com/name/nm0000881/',
-        :writer   => ['http://www.imdb.com/name/nm0918711/', 'http://www.imdb.com/name/nm0177018/']
+    set_meta_tags og: {
+      title:    'The Rock',
+      type:     'video.movie',
+      url:      'http://www.imdb.com/title/tt0117500/',
+      image:    'http://ia.media-imdb.com/rock.jpg',
+      video:    {
+        director: 'http://www.imdb.com/name/nm0000881/',
+        writer:   ['http://www.imdb.com/name/nm0918711/', 'http://www.imdb.com/name/nm0177018/']
       }
     }
     # <meta property="og:title" content="The Rock"/>
@@ -229,6 +293,33 @@ and in the future. Here's an example for a movie page:
     # <meta property="og:video:writer" content="http://www.imdb.com/name/nm0918711/"/>
     # <meta property="og:video:writer" content="http://www.imdb.com/name/nm0177018/"/>
 
+Multiple images declared as an **array** (look at the `_` character):
+
+    set_meta_tags og: {
+      title:    'Two structured image properties',
+      type:     'website',
+      url:      'view-source:http://examples.opengraphprotocol.us/image-array.html',
+      image:    [{
+        _: 'http://examples.opengraphprotocol.us/media/images/75.png',
+        width: 75,
+        height: 75,
+      },
+      {
+        _: 'http://examples.opengraphprotocol.us/media/images/50.png',
+        width: 50,
+        height: 50,
+      }]
+    }
+    # <meta property="og:title" content="Two structured image properties">
+    # <meta property="og:type" content="website">
+    # <meta property="og:url" content="http://examples.opengraphprotocol.us/image-array.html">
+    # <meta property="og:image" content="http://examples.opengraphprotocol.us/media/images/75.png">
+    # <meta property="og:image:width" content="75">
+    # <meta property="og:image:height" content="75">
+    # <meta property="og:image" content="http://examples.opengraphprotocol.us/media/images/50.png">
+    # <meta property="og:image:width" content="50">
+    # <meta property="og:image:height" content="50">
+
 Further reading:
 
 * [Open Graph protocol](http://developers.facebook.com/docs/opengraph/)
@@ -238,9 +329,9 @@ Further reading:
 Twitter cards make it possible for you to attach media experiences to Tweets that link to your content.
 There are 3 card types (summary, photo and player). Here's an example for summary:
 
-    set_meta_tags :twitter => {
-      :card => "summary",
-      :site => "@username"
+    set_meta_tags twitter: {
+      card: "summary",
+      site: "@username"
     }
     # <meta name="twitter:card" content="summary"/>
     # <meta name="twitter:site" content="@username"/>
@@ -249,12 +340,12 @@ Take in consideration that if you're already using OpenGraph to describe data on
 
 When you need to generate a [Twitter Photo card](https://dev.twitter.com/docs/cards/types/photo-card), `twitter:image` property is a string, while image dimensions are specified using `twitter:image:width` and `twitter:image:height`, or a `Hash` objects in terms of MetaTags gems. There is a special syntax to make this work:
 
-    set_meta_tags :twitter => {
-      :card  => "photo",
-      :image => {
-        :_      => "http://example.com/1.png",
-        :width  => 100,
-        :height => 100,
+    set_meta_tags twitter: {
+      card:  "photo",
+      image: {
+        _:      "http://example.com/1.png",
+        width:  100,
+        height: 100,
       }
     }
     # <meta name="twitter:card" content="photo"/>
@@ -273,13 +364,13 @@ be rendered on the page, even if meta-tags gem does not know about them.
 
 Example:
 
-    set_meta_tags :author => "Dmytro Shteflyuk"
+    set_meta_tags author: "Dmytro Shteflyuk"
     # <meta name="author" content="Dmytro Shteflyuk"/>
 
 You can also specify value as an Array, and values will be displayed as a list
 of `meta` tags:
 
-    set_meta_tags :author => [ "Dmytro Shteflyuk", "John Doe" ]
+    set_meta_tags author: [ "Dmytro Shteflyuk", "John Doe" ]
     # <meta name="author" content="Dmytro Shteflyuk"/>
     # <meta name="author" content="John Doe"/>
 
@@ -288,7 +379,7 @@ of `meta` tags:
 First, add this code to your main layout:
 
     <head>
-      <%= display_meta_tags :site => 'My website' %>
+      <%= display_meta_tags site: 'My website' %>
     </head>
 
 Then, to set the page title, add this to each of your views (see below for other options):
@@ -316,9 +407,9 @@ You can define following instance variables:
 
 Also you could use `set_meta_tags` method to define all meta tags simultaneously:
 
-    set_meta_tags :title => 'Member Login',
-                  :description => 'Member login page.',
-                  :keywords => 'Site, Login, Members'
+    set_meta_tags title: 'Member Login',
+                  description: 'Member login page.',
+                  keywords: 'Site, Login, Members'
 
 You can find allowed options for `set_meta_tags` method below.
 
@@ -335,9 +426,9 @@ To set meta tags you can use following methods:
 
 Also there is `set_meta_tags` method exists:
 
-    <% set_meta_tags :title => 'Member Login',
-                     :description => 'Member login page.',
-                     :keywords => 'Site, Login, Members' %>
+    <% set_meta_tags title: 'Member Login',
+                     description: 'Member login page.',
+                     keywords: 'Site, Login, Members' %>
 
 The `title` method returns title itself, so you can use it to show the title
 somewhere on the page:
@@ -356,6 +447,7 @@ Use these options to customize the title format:
 * `:title` — page title;
 * `:description` — page description;
 * `:keywords` — page keywords;
+* `:charset` — page character set;
 * `:prefix` — text between site name and separator;
 * `:separator` — text used to separate website name from page title;
 * `:suffix` — text between separator and page title;
@@ -374,25 +466,25 @@ Use these options to customize the title format:
 
 And here are a few examples to give you ideas.
 
-    <%= display_meta_tags :separator => "&mdash;".html_safe %>
-    <%= display_meta_tags :prefix => false, :separator => ":" %>
-    <%= display_meta_tags :lowercase => true %>
-    <%= display_meta_tags :reverse => true, :prefix => false %>
-    <%= display_meta_tags :og => { :title => 'The Rock', :type => 'video.movie' } %>
-    <%= display_meta_tags :alternate => { 'zh-Hant' => 'http://example.com.tw/base/url' } %>
+    <%= display_meta_tags separator: "&mdash;".html_safe %>
+    <%= display_meta_tags prefix: false, separator: ":" %>
+    <%= display_meta_tags lowercase: true %>
+    <%= display_meta_tags reverse: true, prefix: false %>
+    <%= display_meta_tags og: { title: 'The Rock', type: 'video.movie' } %>
+    <%= display_meta_tags alternate: { 'zh-Hant' => 'http://example.com.tw/base/url' } %>
 
 ### Allowed values
 
 You can specify `:title` as a string or array:
 
-    set_meta_tags :title => ['part1', 'part2'], :site => 'site'
+    set_meta_tags title: ['part1', 'part2'], site: 'site'
     # site | part1 | part2
-    set_meta_tags :title => ['part1', 'part2'], :reverse => true, :site => 'site'
+    set_meta_tags title: ['part1', 'part2'], reverse: true, site: 'site'
     # part2 | part1 | site
 
 Keywords can be passed as string of comma-separated values, or as an array:
 
-    set_meta_tags :keywords => ['tag1', 'tag2']
+    set_meta_tags keywords: ['tag1', 'tag2']
     # tag1, tag2
 
 Description is a string (HTML will be stripped from output string).
@@ -405,8 +497,8 @@ the `title`.
 
 Say, you have the following in your application layout:
 
-    display_meta_tags :og => {
-      :title => :title
+    display_meta_tags og: {
+      title: :title
     }
 
 The value of `og[:title]` is a symbol and therefore references the value of the
@@ -432,10 +524,10 @@ code duplication, you can define a helper in `application_helper.rb`:
 
     def default_meta_tags
       {
-        :title       => 'Member Login',
-        :description => 'Member login page.',
-        :keywords    => 'Site, Login, Members',
-        :separator   => "&mdash;".html_safe,
+        title:       'Member Login',
+        description: 'Member login page.',
+        keywords:    'Site, Login, Members',
+        separator:   "&mdash;".html_safe,
       }
     end
 
@@ -447,7 +539,7 @@ And in your pjax templates:
 
     <!-- set title here, so we can use it both in "display_title" and in "title" %>
     <% title "My Page title" %>
-    <%= content_tag :div, :data => { :title => display_title(default_meta_tags) } do %>
+    <%= content_tag :div, data: { title: display_title(default_meta_tags) } do %>
         <h1><%= title %></h1>
         <!-- HTML goes here -->
     <% end %>