kontent-delivery-sdk-ruby 2.0.16 → 2.0.22

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 96b761a2d404fbb7f7d4277dc11777b5518f89091243cf5a2c3a24974e554270
-  data.tar.gz: 0f5404b57090c5d827576d9e4a84a71a24e151a7fa848847509c6f7134f006c8
+  metadata.gz: b93d8bae053c876e19256fc6695fa2dd593dc9479f89da1ede61ec166316a0cb
+  data.tar.gz: 21721f7c4105cc9c07e62009b01b5d380f485082d807a1337002d44eaebc52fc
 SHA512:
-  metadata.gz: 83c79acbeabffaaa8002414f5dc28d90a310e66085382922fcc9d03bc416afa0113a9a6836c2be44f92073e534ef601982e2363d647e32c75f4a04c0e2ae7e38
-  data.tar.gz: a3e94e33ab180278b446f76275e2f6e51716caca29f87fd7c7d49545807fd6d0f584133f85d646e56feeb824d4952fd6c1be35d54dfe81036619b614dc0ef757
+  metadata.gz: 8df410c1f68405b40824f82fe7ac866de358e8df90042419bc52406807bd89610adabdbd5dcaf8c4a9bf751bc56882ff670c2d4c704bd1bc5e21ee49bea8927a
+  data.tar.gz: 15b2ebbe2e3a98b5a4f5e66e6d7af39c04c6db4d8652cd061f9bf9c0824c4dda87e522f4e7d4b812d2e84a378e9348e2a62c132018ad8032fb6b01b1801be750

data/README.md

@@ -1,36 +1,42 @@
-[![Build Status](https://api.travis-ci.com/Kentico/kontent-delivery-sdk-ruby.svg?branch=master)](https://travis-ci.com/Kentico/kontent-delivery-sdk-ruby)
+![build](https://github.com/Kentico/kontent-delivery-sdk-ruby/actions/workflows/build.yml/badge.svg)
 [![Join the chat at https://kentico-community.slack.com](https://img.shields.io/badge/join-slack-E6186D.svg)](https://kentico-community.slack.com)
 [![Stack Overflow](https://img.shields.io/badge/Stack%20Overflow-ASK%20NOW-FE7A16.svg?logo=stackoverflow&logoColor=white)](https://stackoverflow.com/tags/kentico-kontent)
  [![Version](https://img.shields.io/gem/v/kontent-delivery-sdk-ruby.svg?style=flat)](https://rubygems.org/gems/kontent-delivery-sdk-ruby)
-[![Maintainability](https://api.codeclimate.com/v1/badges/c83f2067f9cae9bde737/maintainability)](https://codeclimate.com/github/Kentico/kontent-delivery-sdk-ruby/maintainability)
-[![Test Coverage](https://api.codeclimate.com/v1/badges/c83f2067f9cae9bde737/test_coverage)](https://codeclimate.com/github/Kentico/kontent-delivery-sdk-ruby/test_coverage)
 
 # Delivery Ruby SDK
 
-![Banner](https://github.com/Kentico/kontent-delivery-sdk-ruby/blob/master/banner.png)
+![Banner](/banner.png)
 
 The Delivery Ruby SDK can be used in Ruby/Rails projects to retrieve content from Kentico Kontent. This is a community project and not an official Kentico SDK. If you find a bug in the SDK or have a feature request, please submit a GitHub issue.
 
-See [How to setup a development environment on Windows](https://github.com/Kentico/kontent-delivery-sdk-ruby/wiki/How-to-setup-development-environment-on-Windows) for local development.
-
-
-## Demo Rails application
-
-This repository contains a very basic Rails application that you can run locally to see how the SDK can be used. To run the Dancing Goat demo application, clone this repository and open `/dancing_goat/app/controllers/application_controller.rb`. Add your project ID to the file here:
-
-```ruby
-class ApplicationController < ActionController::Base
-  PROJECT_ID = '<your-project-id>'.freeze
-```
-
-If you don't have the sample project installed in Kentico Kontent, you can generate a new project [here](https://app.kontent.ai/sample-project-generator). Save the file, then open a terminal in the `/dancing_goat` directory and run the following commands:
-
-```
-bundle install
-rails server
-```
-
-The site should be accessible at localhost:3000. You can also follow a step-by-step guide to creating a basic Rails application on the [Kentico Kontent Blog](https://kontent.ai/blog/creating-a-kentico-cloud-ruby-on-rails-application).
+See [How to setup a development environment on Windows](https://github.com/Kentico/kontent-delivery-sdk-ruby/wiki/How-to-setup-development-environment-on-Windows) for local development, and check out the [Kentico Kontent Blog](https://kontent.ai/blog/creating-a-kentico-cloud-ruby-on-rails-application) for a tutorial on creating a Rails application.
+
+## Table of contents
+
+- [Installation](#installation)
+- [Creating a client](#creating-a-client)
+  - [Previewing unpublished content](#previewing-unpublished-content)
+  - [Making secure requests](#making-secure-requests)
+  - [Retry policy](#retry-policy)
+  - [Custom URLs](#custom-urls)
+- [Listing items](#listing-items)
+  - [Filtering](#filtering)
+  - [Parameters](#parameters)
+  - [Responses](#responses)
+  - [Requesting the latest content](#requesting-the-latest-content)
+  - [Providing custom headers](#providing-custom-headers)
+  - [Pagination](#pagination)
+- [Working with content items](#working-with-content-items)
+  - [Assets](#assets)
+  - [Linked items](#linked-items)
+  - [Resolving inline content](#resolving-inline-content)
+  - [Resolving links](#resolving-links)
+- [Items feed](#items-feed)
+- [Retrieving content types](#retrieving-content-types)
+- [Retrieving taxonomy](#retrieving-taxonomy)
+- [Retrieving content type elements](#retrieving-content-type-elements)
+- [Retrieving languages](#retrieving-languages)
+- [Image transformation](#image-transformation)
 
 ## Installation
 
@@ -40,7 +46,7 @@ To use the SDK in your own project, add the gem to your Gemfile:
 gem 'kontent-delivery-sdk-ruby'
 ```
 
-Then run `bundle install`. You can also download the gem from [RubyGems.org](https://rubygems.org/gems/delivery-sdk-ruby). To use the SDK in an `.rb` file, you need to require it:
+Then run `bundle install`. You can also download the gem from [RubyGems.org](https://rubygems.org/gems/kontent-delivery-sdk-ruby). To use the SDK in an `.rb` file, you need to require it:
 
 ```ruby
 require 'kontent-delivery-sdk-ruby'
@@ -63,14 +69,14 @@ delivery_client = KK::DeliveryClient.new project_id: '<your-project-id>'
 
 ### Previewing unpublished content
 
-To enable [preview](https://developer.kenticocloud.com/docs/previewing-content-in-a-separate-environment "preview"), pass the Preview API Key to the constructor:
+To [enable preview](https://docs.kontent.ai/tutorials/develop-apps/get-content/configuring-preview-for-content-items "See how to configure your app and Kontent project to enable content preview"), pass the Preview API Key to the constructor:
 
 ```ruby
 delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
                                                                  preview_key: '<your-preview-key>'
 ```
 
-This enables preview, but you can toggle preview at any time by setting the `use_preview` attribute of DeliveryClient which is propogated to all queries created by the client, _or_ per-query by setting it's `use_preview` attribute:
+This enables preview, but you can toggle preview at any time by setting the `use_preview` attribute of `DeliveryClient` which is propagated to all queries created by the client, _or_ per-query by setting its `use_preview` attribute:
 
 ```ruby
 # For all queries created by client
@@ -86,14 +92,14 @@ end
 
 ### Making secure requests
 
-If you've [secured access](https://developer.kenticocloud.com/docs/securing-public-access "Securing public access") to your project, you need to provide the DeliveryClient with the primary or secondary key:
+If you've [secured access](https://docs.kontent.ai/tutorials/develop-apps/get-content/securing-public-access "See how to enable secured access for your Kontent project") to your project, you need to provide the `DeliveryClient` with either the primary or secondary key:
 
 ```ruby
 Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
                                            secure_key: '<your-secure-key>'
 ```
 
-You can then request the secure published content in your project. Be sure to not expose the key if the file(s) it appears in are publicly-available.
+You can then securely request published content in your project. Be sure to not expose the key if the file(s) it appears in are publicly available.
 
 ### Retry policy
 
@@ -116,6 +122,18 @@ Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
                                            with_retry_policy: false
 ```
 
+### Custom URLs
+
+When you have a URL (i.e. `next_page` for paging, for testing purposes, or if you prefer to build it on your own) and still want to leverage SDK functionality such as rich text resolving, use the .url method:
+
+```ruby
+delivery_client.items
+  .url('https://deliver.kontent.ai/<your-project-id>/items?system.type=grinder')
+  .execute do |response|
+    # Do something
+  end
+```
+
 ## Listing items
 
 
@@ -137,7 +155,7 @@ response = delivery_client.items.execute
 
 ### Filtering
 
-You can use [filtering](https://developer.kenticocloud.com/v1/reference#content-filtering "filtering") to retrieve particular items. The filtering methods are applied directly to a string and the available methods are:
+You can use [filtering](https://docs.kontent.ai/reference/delivery-api#tag/Filtering-content "See content filtering options in Delivery API") to retrieve particular items. The filtering methods are applied directly to a string and the available methods are:
 
 |Method|Example|REST equivalent|
 |--|--|--|
@@ -145,12 +163,16 @@ You can use [filtering](https://developer.kenticocloud.com/v1/reference#content-
 |any|`'elements.processing'.any %w[dry__natural_ semi_dry]`|?elements.processing[any]=dry__natural_,semi_dry|
 |contains|`'elements.related_articles'.contains 'on_roasts'`|?elements.related_articles[contains]=on_roasts|
 |eq|`'system.type'.eq 'grinder'`|?system.type=grinder|
+|not_eq|`'elements.region'.not_eq  'USA'`|?elements.region[neq]=USA|
 |gt|`'elements.price'.gt 20`|?elements.price[gt]=20|
 |gt_or_eq|`'elements.price'.gt_or_eq 20`|?elements.price[gte]=20|
 |in|`'system.type'.in %w[coffee brewer]`|?system.type[in]=coffee,brewer|
+|not_in|`'elements.author'.not_in %w[mberry ericd anthonym]`|?elements.author[nin]=mberry,ericd,anthonym|
 |lt|`'elements.price'.lt 20`|?elements.price[lt]=20|
 |lt_or_eq|`'elements.price'.lt_or_eq 20`|?elements.price[lte]=20|
 |range|`'system.last_modified'.range %w[2018-02-01 2018-03-31]`|?system.last_modified[range]=2018-02-01,2018-03-31|
+|empty|`'elements.banned_reason'.empty`|?elements.banned_reason[empty]|
+|not_empty|`'elements.status'.not_empty`|?elements.status[nempty]|
 
 You can pass a single filter or multiple filters in the DeliveryClient methods. For example:
 
@@ -171,12 +193,12 @@ The `.item` and `.items` methods return a `Kentico::Kontent::Delivery::DeliveryQ
 
 |Method|Example|REST equivalent
 |--|--|--|
-|[order_by](https://developer.kenticocloud.com/v1/reference#content-ordering "order_by")|`order_by 'system.last_modified' '[desc]'`|?order=system.last_modified[desc]
-|[skip](https://developer.kenticocloud.com/v1/reference#listing-response-paging "skip")|`skip 5`|?skip=5
-|[limit](https://developer.kenticocloud.com/v1/reference#listing-response-paging "limit")|`limit 5`|?limit=5
-|[elements](https://developer.kenticocloud.com/v1/reference#projection "elements")|`elements %w[price product_name image]`|?elements=price,product_name,image
-|[depth](https://developer.kenticocloud.com/v1/reference#linked-content "depth")|`depth 0`|?depth=0
-|[language](https://developer.kenticocloud.com/docs/understanding-language-fallbacks "language")|`language 'en'`|?language=en
+|[order_by](https://docs.kontent.ai/reference/delivery-api#operation/list-content-items "order_by")|`order_by 'system.last_modified' '[desc]'`|?order=system.last_modified[desc]
+|[skip](https://docs.kontent.ai/reference/delivery-api#operation/list-content-items "skip")|`skip 5`|?skip=5
+|[limit](https://docs.kontent.ai/reference/delivery-api#operation/list-content-items "limit")|`limit 5`|?limit=5
+|[elements](https://docs.kontent.ai/reference/delivery-api#tag/Projection "elements")|`elements %w[price product_name image]`|?elements=price,product_name,image
+|[depth](https://docs.kontent.ai/reference/delivery-api#tag/Linked-content-and-components/linked-content-depth "depth")|`depth 0`|?depth=0
+|[language](https://docs.kontent.ai/tutorials/set-up-projects/set-up-languages/localization-in-kentico-kontent#a-understanding-language-fallbacks "language")|`language 'en'`|?language=en
 
 For example:
 
@@ -224,7 +246,7 @@ price = response.item.elements.price.value
 
 ### Requesting the latest content
 
-Kentico caches content using Fastly, so requests made to Kentico Kontent may not be up-to-date. In some cases, such as when reacting to [webhook](https://developer.kenticocloud.com/docs/webhooks) notifications, you might want to request the latest content from your Kentico Kontent project.
+Kentico caches content using Fastly, so requests made to Kentico Kontent may not be up-to-date. In some cases, such as when reacting to [webhook](https://docs.kontent.ai/tutorials/develop-apps/integrate/using-webhooks-for-automatic-updates) notifications, you might want to request the latest content from your Kentico Kontent project.
 
 You can check the headers of the response for the **X-Stale-Content** header to check if the response was served from cache:
 
@@ -256,18 +278,32 @@ delivery_client.items
   .execute
 ```
 
-### Custom URLs
+### Pagination
 
-When you have a URL (i.e. `next_page` for paging, for testing purposes, or if you prefer to build it on your own) and still want to leverage SDK functionality such as rich text resolving, use the .url method:
+Most responses also contain a `pagination` attribute to access the [paging](https://docs.kontent.ai/reference/delivery-api#operation/list-content-items "paging") data for the Delivery query. This object contains the following attributes:
+
+- **skip**
+- **limit**
+- **count**
+- **next_page**
+- **total_count** (only if `include_total_count` is called)
+
+For example, to access the next page URL you can use:
 
 ```ruby
 delivery_client.items
-  .url('https://deliver.kontent.ai/<your-project-id>/items?system.type=grinder')
-  .execute do |response|
-    # Do something
-  end
+    .skip(0)
+    .limit(5)
+    .include_total_count
+    .execute do |response|
+      next_page_url = response.pagination.next_page
+    end
 ```
 
+:warning: Note that using the `include_total_count` method may increase the response time and should only be used if necessary.
+
+## Working with content items
+
 ### Assets
 
 You can use `.get_assets(code_name)` to get one or more assets from the specified element. This method will always return an array, so use `.first` to get the first asset:
@@ -291,36 +327,126 @@ response.item.get_links('facts').each do |link|
   title = link.elements.title.value
 end
 ```
+### Resolving inline content
 
-### Pagination
+Existing content items can be inserted into a rich text element, or you can create new content items as components. You need to resolve these in your application just as with content links. You can register a resolver when you instantiate the client by passing it with the hash key `inline_content_item_resolver`:
 
-The `DeliveryItemListingResponse` also contains a `pagination` attribute to access the [paging](https://developer.kenticocloud.com/v1/reference#listing-response-paging "paging") data for the Delivery query. This object contains the following attributes:
+```ruby
+item_resolver = Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver.new(lambda do |item|
+      return "<h1>#{item.elements.zip_code.value}</h1>" if item.system.type.eql? 'cafe'
+      return "<div>$#{item.elements.price.value}</div>" if item.system.type.eql? 'brewer'
+    end)
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
+                                                             inline_content_item_resolver: item_resolver
+```
 
-- **skip**
-- **limit**
-- **count**
-- **next_page**
-- **total_count** (only if `include_total_count` is called)
+The object passed to the resolving method is a complete ContentItem. Similar to content link resolvers, you can create your own class which extends `Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver` and implements the `resolve_item` method:
 
-For example, to access the next page URL you can use:
+```ruby
+class MyItemResolver < Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver
+  def resolve_item(item)
+    return "<h1>#{item.elements.zip_code.value}</h1>" if item.system.type.eql? 'cafe'
+    return "<div>$#{item.elements.price.value}</div>" if item.system.type.eql? 'brewer'
+  end
+end
+```
+
+You can also set the inline content resolver per-query:
 
 ```ruby
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>'
+# Client doesn't use InlineContentItemResolver, but query below will
 delivery_client.items
-    .skip(0)
-    .limit(5)
-    .include_total_count
-    .execute do |response|
-      next_page_url = response.pagination.next_page
-    end
+               .with_inline_content_item_resolver MyItemResolver.new
 ```
 
-:warning: Note that using the `include_total_count` method may increase the response time and should only be used if necessary.
+To resolve inline content in elements, you must call `get_string` similar to content item links:
+
+```ruby
+item_resolver = Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver.new(lambda do |item|
+  return "<div>$#{item.elements.price.value}</div>" if item.system.type.eql? 'brewer'
+end)
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: PROJECT_ID,
+                                                    inline_content_item_resolver: item_resolver
+delivery_client.item('our_brewers').execute do |response|
+  text = response.item.get_string 'body_copy'
+end
+```
+
+### Resolving links
+
+If a rich text element contains links to other content items, you will need to generate the URLs to those items. You can do this by registering a `Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver` when you instantiate the DeliveryClient. When you create a ContentLinkResolver, you must pass a method that will return the URL, and you may pass another method that will be called if the content contains a link, but the content item is not present in the response:
+
+```ruby
+link_resolver = Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver.new(lambda do |link|
+        # Link valid
+        return "/coffees/#{link.url_slug}" if link.type.eql? 'coffee'
+        return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
+      end, lambda do |id|
+        # Link broken
+        return "/notfound?id=#{id}"
+      end)
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
+                                                             content_link_url_resolver: link_resolver
+```
+
+You can also build the logic for your resolver in a separate class and register an instance of that class in the DeliveryClient. The class must extend `Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver` and contain a `resolve_link(link)` method, as well as the `resolve_404(id)` method for broken links. For example, you can create `MyLinkResolver.rb`:
+
+```ruby
+class MyLinkResolver < Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver
+  def resolve_link(link)
+    return "/coffees/#{link.url_slug}" if link.type.eql? 'coffee'
+    return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
+  end
+
+  def resolve_404(id)
+    "/notfound?id=#{id}"
+  end
+end
+```
+
+Then create an object of this class when instantiating the DeliveryClient:
+
+```ruby
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
+                                                             content_link_url_resolver: MyLinkResolver.new
+```
+
+You can pass a `ContentLinkResolver` to the DeliveryQuery instead of the client if you only want to resolve links for that query, or they should be resolved differently:
+
+```ruby
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>'
+# Client doesn't use ContentLinkResolver, but query below will
+delivery_client.items
+               .with_link_resolver MyLinkResolver.new
+```
+
+The `ContentLink` object that is passed to your resolver contains the following attributes:
+
+- **id**: the system.id of the linked content item
+- **code_name**: the system.codename of the linked content item
+- **type**: the content type of the linked content item
+- **url_slug**: the URL slug of the linked content item, or nil if there is none
+
+To resolve links in rich text elements, you must retrieve the text using `get_string`:
+
+```ruby
+item_resolver = Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver.new(lambda do |link|
+  return "/coffees/#{link.url_slug}" if link.type.eql? 'coffee'
+  return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
+end)
+delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
+                                                             content_link_url_resolver: item_resolver
+delivery_client.item('coffee_processing_techniques').execute do |response|
+  text = response.item.get_string 'body_copy'
+end
+```
 
 ## Items feed
 
 Use the `items_feed` method to retrieve a dynamically paginated list of content items in your project. The result will have a `more_results?` method which indicates that more items can be retrieved from the feed, using the `next_result` method.
 
-This method accepts all [filtering](https://github.com/Kentico/kontent-delivery-sdk-ruby#filtering) and [parameters](https://github.com/Kentico/kontent-delivery-sdk-ruby#parameters) except _depth_, _skip_, and _limit_. You can read more about the /items-feed endpoint in the [Kontent documentation](https://docs.kontent.ai/reference/delivery-api#operation/enumerate-content-items)
+This method accepts all [filtering](#filtering) and [parameters](https://github.com/Kentico/kontent-delivery-sdk-ruby#parameters) except _depth_, _skip_, and _limit_. You can read more about the /items-feed endpoint in the [Kontent documentation](https://docs.kontent.ai/reference/delivery-api#operation/enumerate-content-items)
 
 Below is an example that will load all content items of a project into a single array:
 
@@ -349,8 +475,6 @@ delivery_client.type('coffee').execute do |response|
 end
 ```
 
-### Responses
-
 As with content item queries, all content type queries will return a `Kentico::Kontent::Delivery::Responses::ResponseBase` of the class `DeliveryTypeResponse` or `DeliveryTypeListingResponse` for single and multiple type queries, respectively.
 
 For multiple type queries, you can access the array of `ContentType` objects at `.types`, and at `.type` for singe type queries. You can access information about the type(s) dynamically:
@@ -362,7 +486,7 @@ end
 ```
 The DeliveryTypeListingResponse also contains pagination data, similar to DeliveryItemListingResponse.
 
-## Taxonomy
+## Retrieving taxonomy
 
 Use the `.taxonomies` and `.taxonomy(code_name)` endpoints to get information about the taxonomy in your project:
 
@@ -407,7 +531,7 @@ end
 
 ## Retrieving content type elements
 
-Kentico Kontent provides an [endpoint](https://developer.kenticocloud.com/v1/reference#view-a-content-type-element) for obtaining details about a specific element of a content type. In the Ruby SDK, you can use the `.element` method:
+Kentico Kontent provides an [endpoint](https://docs.kontent.ai/reference/delivery-api#operation/retrieve-a-content-element) for obtaining details about a specific element of a content type. In the Ruby SDK, you can use the `.element` method:
 
 ```ruby
 delivery_client.element('brewer', 'product_status').execute do |response|
@@ -417,113 +541,29 @@ end
 
 This returns a `Kentico::Kontent::Delivery::Responses::DeliveryElementResponse` where the `element` attribute is a dynamic OStruct representation of the JSON response. This means that you can access any property of the element by simply typing the name as in the above example.
 
-The element will always contain __codename__, __type__, and __name__, but multiple choice elements will also contain __options__ and taxonomy elements will contain __taxonomy_group__. The Ruby SDK fully supports obtaining [custom elements](https://developer.kenticocloud.com/v1/reference#custom-elements-api) using this approach and any other methods.
+The element will always contain __codename__, __type__, and __name__, but multiple choice elements will also contain __options__ and taxonomy elements will contain __taxonomy_group__. The Ruby SDK fully supports obtaining [custom elements](https://docs.kontent.ai/reference/custom-elements-js-api) using this approach and any other methods.
 
-## Resolving links
+## Retrieving languages
 
-If a rich text element contains links to other content items, you will need to generate the URLs to those items. You can do this by registering a `Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver` when you instantiate the DeliveryClient. When you create a ContentLinkResolver, you must pass a method that will return the URL, and you may pass another method that will be called if the content contains a link, but the content item is not present in the response:
+Use the `.languages` method to list all of the languages in the project:
 
 ```ruby
-link_resolver = Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver.new(lambda do |link|
-        # Link valid
-        return "/coffees/#{link.url_slug}" if link.type.eql? 'coffee'
-        return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
-      end, lambda do |id|
-        # Link broken
-        return "/notfound?id=#{id}"
-      end)
-delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                                             content_link_url_resolver: link_resolver
-```
-
-You can also build the logic for your resolver in a separate class and register an instance of that class in the DeliveryClient. The class must extend `Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver` and contain a `resolve_link(link)` method, as well as the `resolve_404(id)` method for broken links. For example, you can create `MyLinkResolver.rb`:
-
-```ruby
-class MyLinkResolver < Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver
-  def resolve_link(link)
-    return "/coffees/#{link.url_slug}" if link.type.eql? 'coffee'
-    return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
-  end
-
-  def resolve_404(id)
-    "/notfound?id=#{id}"
-  end
+delivery_client.languages.execute do |response|
+  puts response.languages.length # number of languages
 end
 ```
 
-Then create an object of this class when instantiating the DeliveryClient:
+The response is a `Kentico::Kontent::Delivery::Responses::DeliveryLanguageListingResponse` where `languages` is an array of all langauges. You can access the system properties of each language as they are returned by Kontent:
 
 ```ruby
-delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                                             content_link_url_resolver: MyLinkResolver.new
-```
-
-You can pass a `ContentLinkResolver` to the DeliveryQuery instead of the client if you only want to resolve links for that query, or they should be resolved differently:
-
-```ruby
-delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>'
-# Client doesn't use ContentLinkResolver, but query below will
-delivery_client.items
-               .with_link_resolver MyLinkResolver.new
-```
-
-The `ContentLink` object that is passed to your resolver contains the following attributes:
-
-- **id**: the system.id of the linked content item
-- **code_name**: the system.codename of the linked content item
-- **type**: the content type of the linked content item
-- **url_slug**: the URL slug of the linked content item, or nil if there is none
-
-To resolve links in rich text elements, you must retrieve the text using `get_string`:
-
-```ruby
-item_resolver = Kentico::Kontent::Delivery::Resolvers::ContentLinkResolver.new(lambda do |link|
-  return "/coffees/#{link.url_slug}" if link.type.eql? 'coffee'
-  return "/brewers/#{link.url_slug}" if link.type.eql? 'brewer'
-end)
-delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                                             content_link_url_resolver: item_resolver
-delivery_client.item('coffee_processing_techniques').execute do |response|
-  text = response.item.get_string 'body_copy'
-end
-```
-
-## Resolving inline content
-
-Existing content items can be inserted into a rich text element, or you can create new content items as components. You need to resolve these in your application just as with content links. You can register a resolver when you instantiate the client by passing it with the hash key `inline_content_item_resolver`:
-
-```ruby
-item_resolver = Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver.new(lambda do |item|
-      return "<h1>#{item.elements.zip_code.value}</h1>" if item.system.type.eql? 'cafe'
-      return "<div>$#{item.elements.price.value}</div>" if item.system.type.eql? 'brewer'
-    end)
-delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>',
-                                                             inline_content_item_resolver: item_resolver
-```
-
-The object passed to the resolving method is a complete ContentItem. Similar to content link resolvers, you can create your own class which extends `Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver` and implements the `resolve_item` method:
-
-```ruby
-class MyItemResolver < Kentico::Kontent::Delivery::Resolvers::InlineContentItemResolver
-  def resolve_item(item)
-    return "<h1>#{item.elements.zip_code.value}</h1>" if item.system.type.eql? 'cafe'
-    return "<div>$#{item.elements.price.value}</div>" if item.system.type.eql? 'brewer'
-  end
+delivery_client.languages.execute do |response|
+  puts response.languages[0].system.codename # en-us
 end
 ```
 
-You can also set the inline content resolver per-query:
-
-```ruby
-delivery_client = Kentico::Kontent::Delivery::DeliveryClient.new project_id: '<your-project-id>'
-# Client doesn't use InlineContentItemResolver, but query below will
-delivery_client.items
-               .with_inline_content_item_resolver MyItemResolver.new
-```
-
 ## Image transformation
 
-When you've obtained the URL for an asset, you can use our [Image Transformation API](https://developer.kenticocloud.com/v1/reference#image-transformation) to make on-the-fly modifications to the image. To do this, use the static `.transform` method of `Kentico::Kontent::Delivery::Builders::ImageTransformationBuilder`, then call the transformation methods. When you're done, call the `.url` method to get the new URL:
+When you've obtained the URL for an asset, you can use our [Image Transformation API](https://docs.kontent.ai/reference/image-transformation) to make on-the-fly modifications to the image. To do this, use the static `.transform` method of `Kentico::Kontent::Delivery::Builders::ImageTransformationBuilder`, then call the transformation methods. When you're done, call the `.url` method to get the new URL:
 
 ```ruby
 url = response.item.get_assets('teaser_image').first.url
@@ -560,4 +600,3 @@ The gem is available as open source under the terms of the [MIT License](https:/
 
 Everyone interacting in the Delivery project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/Kentico/kontent-delivery-sdk-net/blob/master/CODE_OF_CONDUCT.md).
 
-![Analytics](https://kentico-ga-beacon.azurewebsites.net/api/UA-69014260-4/Kentico/kontent-delivery-sdk-ruby?pixel)