.gitignore

@@ -7,8 +7,6 @@ gemfiles/*.lock
 spec/site/_site
 spec/integration/site/_site
 
-spec/site/.jekyll-cache/
-.jekyll-cache/
 
 .DS_Store
 .*.sw[a-z]

.travis.yml

@@ -3,9 +3,9 @@ cache: bundler
 before_script: bundle update
 script: bundle exec rake test
 rvm:
- - 2.6.2
  - 2.4.2
  - 2.3.5
+ - 2.3.0
 notifications:
   email:
     on_success: never

CONTRIBUTING.md

@@ -38,16 +38,6 @@ group :jekyll_plugins do
 end
 ```
 
-## Running integration tests
-
-Integration tests will do a full jekyll run, and push data to an Algolia index,
-checking that records and settings are correctly saved. It is the slowest
-possible kind of tests, but also the one closest to a real implementation.
-
-Running those tests requires a real Algolia plan. You need to define
-`ALGOLIA_APPLICATION_ID`, `ALGOLIA_API_KEY` and `ALGOLIA_INDEX_NAME` (we suggest
-using `direnv` for that), and then run `./scripts/test_integration`.
-
 ## Linting
 
 Run `rake lint` to check the style of all ruby files. Run `rake

README.md

@@ -1,16 +1,15 @@
 # Jekyll Algolia Plugin
 
-[![gem version][1]][16]
+[![gem version][1]](https://rubygems.org/gems/jekyll-algolia)
 ![ruby][2]
 ![jekyll][3]
-[![build master][4]][17]
-[![build develop][6]][17]
-[![coverage master][5]][18]
+[![build master][4]](https://travis-ci.org/algolia/jekyll-algolia)
+[![coverage master][5]](https://coveralls.io/github/algolia/jekyll-algolia?branch=master)
+[![build develop][6]](https://travis-ci.org/algolia/jekyll-algolia)
+[![coverage develop][7]](https://coveralls.io/github/algolia/jekyll-algolia?branch=develop)
 
 Add fast and relevant search to your Jekyll site.
 
-> While this plugin was created by Algolia, it is not an officially supported API client. It is possible that future major versions of Jekyll break compatibility, or require changes.
-
 ## Usage
 
 ```shell
@@ -22,7 +21,7 @@ This will push the content of your Jekyll website to your Algolia index.
 ## Documentation
 
 Full documentation can be found on
-[https://community.algolia.com/jekyll-algolia/][20]
+[https://community.algolia.com/jekyll-algolia/](https://community.algolia.com/jekyll-algolia/getting-started.html)
 
 ## Installation
 
@@ -43,12 +42,12 @@ Once this is done, download all dependencies with `bundle install`.
 
 ## Basic configuration
 
-You need to provide certain Algolia credentials for this plugin to _index_ your
+You need to provide certain Algolia credentials for this plugin to *index* your
 site.
 
-_If you don't yet have an Algolia account, we suggest that you open a free
+*If you don't yet have an Algolia account, we suggest that you open a free
 [Community plan here][8]. You can find more information about the Algolia plans
-[in our FAQ][10]._
+[in our FAQ][10].*
 
 Once signed in, you should get your application ID from [your dashboard][9] and
 define it inside your `_config.yml` file like this:
@@ -90,42 +89,19 @@ FAQ][10].
 Thanks to [Anatoliy Yastreb][14] for a [great tutorial][15] on creating Jekyll
 plugins.
 
+
 [1]: https://badge.fury.io/rb/jekyll-algolia.svg
-
 [2]: https://img.shields.io/badge/ruby-%3E%3D%202.3.0-green.svg
-
 [3]: https://img.shields.io/badge/jekyll-%3E%3D%203.6.0-green.svg
-
 [4]: https://img.shields.io/badge/dynamic/json.svg?label=build%3Amaster&query=value&uri=https%3A%2F%2Fimg.shields.io%2Ftravis%2Falgolia%2Fjekyll-algolia.json%3Fbranch%3Dmaster
-
-[5]: https://coveralls.io/repos/github/algolia/jekyll-algolia/badge.svg?branch=master
-
+[5]: https://img.shields.io/badge/dynamic/json.svg?label=coverage%3Amaster&colorB=&prefix=&suffix=%25&query=$.coverage_change&uri=https%3A%2F%2Fcoveralls.io%2Fgithub%2Falgolia%2Fjekyll-algolia.json%3Fbranch%3Dmaster
 [6]: https://img.shields.io/badge/dynamic/json.svg?label=build%3Adevelop&query=value&uri=https%3A%2F%2Fimg.shields.io%2Ftravis%2Falgolia%2Fjekyll-algolia.json%3Fbranch%3Ddevelop
-
-[7]: https://coveralls.io/repos/github/algolia/jekyll-algolia/badge.svg?branch=develop
-
+[7]: https://img.shields.io/badge/dynamic/json.svg?label=coverage%3Adevelop&colorB=&prefix=&suffix=%25&query=$.coverage_change&uri=https%3A%2F%2Fcoveralls.io%2Fgithub%2Falgolia%2Fjekyll-algolia.json%3Fbranch%3Ddevelop
 [8]: #more-about-the-community-plan
-
 [9]: https://www.algolia.com/api-keys
-
 [10]: https://community.algolia.com/jekyll-algolia/faq.html#how-many-records-will-the-plugin-need
-
 [11]: https://www.algolia.com/users/sign_up/hacker
-
 [12]: https://community.algolia.com/instantsearch.js/
-
-[13]: https://www.algolia.com/press/?section=brand-guidelines
-
+[13]: https://www.algolia.com/press#resources
 [14]: https://github.com/ayastreb/
-
 [15]: https://ayastreb.me/writing-a-jekyll-plugin/
-
-[16]: https://rubygems.org/gems/jekyll-algolia
-
-[17]: https://travis-ci.org/algolia/jekyll-algolia
-
-[18]: https://coveralls.io/github/algolia/jekyll-algolia?branch=master
-
-[19]: https://coveralls.io/github/algolia/jekyll-algolia?branch=develop
-
-[20]: https://community.algolia.com/jekyll-algolia/getting-started.html

docs-src/package.json

@@ -35,7 +35,7 @@
     "hasha": "3.0.0",
     "http-server": "0.10.0",
     "jstransformer-markdown-it": "2.0.0",
-    "lodash": "4.17.5",
+    "lodash": "4.17.4",
     "markdown-it": "8.4.0",
     "markdown-it-anchor": "4.0.0",
     "metalsmith": "2.3.0",
@@ -45,7 +45,7 @@
     "metalsmith-sass": "1.4.0",
     "ms-webpack": "2.0.0",
     "node-sass": "4.7.2",
-    "nodemon": "1.18.7",
+    "nodemon": "1.12.5",
     "postcss": "6.0.14",
     "postcss-loader": "2.0.9",
     "postcss-scss": "1.0.2",
@@ -66,8 +66,8 @@
     "webpack-hot-middleware": "2.21.0"
   },
   "engines": {
-    "node": ">=9.2.0",
-    "yarn": ">=1.3.2"
+    "node": "^9.2.0",
+    "yarn": "^1.3.2"
   },
   "renovate": {
     "extends": [

docs-src/src/faq.md

@@ -8,35 +8,35 @@ layout: content-with-menu.pug
 ## How many records will the plugin need?
 
 The plugin will not create an exact mapping of `1 page = 1 record`. Instead, it
-will split all pages into smaller chunks, and each chunk will be saved as a
-record. Splitting into small chunks is key to offer the best relevance of
+will split all pages into smaller chunks, and each chunk will be saved as
+a record. Splitting in small chunks is key to offer the best relevance of
 results.
 
-The default chunking mechanism is to create one chunk per paragraph of content.
-So, for a blog post that is made up of 10 paragraphs of text, it will create 10
+The default chunking mechanism is to create one chunk per paragraphof content.
+So, for a blog post that is made of 10 paragraphs of text, it will create 10
 records.
 
-Estimating the number of records you will need can be tricky as it depends on
-both the number of pages you have, and on the average length of them. Some
+Estimating the number of records you will need can be tricky as it depends both
+on the number of pages you have, but also on the average length of them.  Some
 configuration options (such as [nodes_to_index][1]) can also influence the final
 result.
 
 The following table should give you a ballpark estimate of what to expect. All
-calculations were done with an average of **15 paragraphs per page**, on a
-timeline of **one year**.
+calculations were done with an average of **15 paragraphs per page**, on
+a timeline of **one year**.
 
-| update frequency            | # of new pages | # of records | Algolia plan   |
-| --------------------------- | -------------- | ------------ | -------------- |
-| ~1 new page per week        | ~50            | ~750         | [Community][2] |
-| ~1 new page per day         | ~400           | ~6.000       | [Community][3] |
-| ~2 new pages per day        | ~700           | ~10.500      | [Essential][4] |
-| ~1 new page per hour        | ~8800          | ~132.000     | [Essential][5] |
-| ~1 new page every 5 minutes | ~105.000       | ~1.575.000   | [Plus][6]      |
-| More?                       | More?          | More?        | [Business][7]  |
+| update frequency               | # of new pages | # of records | Algolia plan |
+| ------------------------------ | -------------- | ------------ | ------------ |
+| ~1 new page per week           | ~50            | ~750         | [Community][2] |
+| ~1 new page per day            | ~400           | ~6.000       | [Community][3] |
+| ~2 new pages per day           | ~700           | ~10.500      | [Essential][4] |
+| ~1 new page per hour           | ~8800          | ~132.000     | [Essential][5] |
+| ~1 new page every 5 minutes    | ~105.000       | ~1.575.000   | [Plus][6]      |
+| More?                          | More?          | More?        | [Business][7]  |
 
 ## One of my records is too big. What can I do?
 
-If you get an error about one of your records being too big, be sure to update
+If you get an error about one of your record being too big, be sure to update
 the plugin to the latest version. We keep improving the plugin with ways of
 making the records smaller.
 
@@ -44,47 +44,15 @@ If you're still having an error, you should check the `.json` log file that has
 been created in your source directory. This will contain the content of the
 record that has been rejected. It might give you hints about what went wrong.
 
-A common cause for this issue often lies in the page HTML. Maybe the HTML is
+A common cause for this issue often liens in the page HTML. Maybe the HTML is
 malformed (a tag is not closed for example), or instead of several small
 paragraphs there is only one large paragraph. This can cause the parser to take
-the whole page content (instead of small chunks of it) to create the records.
+the whole page content (instead of small chunks of it) to create the
+records.
 
 If you don't find where the issue is coming from, feel free to open a [GitHub
 issue][8] with a copy of the log file and we'll be happy to help you.
 
-## How can I tweak the relevance ranking?
-
-The plugin default configuration will rank results based on their textual
-relevance. You can adapt the ranking to fit your needs by using a
-combination of front-matter and Algolia index settings.
-
-For example, if you know some of your blog posts are popular, you might want to
-give them a boost in their ranking. To do so, add a `popular: true` entry to the
-front-matter of such posts. Any custom key added to a front-matter is
-automatically pushed to their corresponding records.
-
-Then, you would have to edit your `_config.yml` file to pass a custom
-`settings.customRanking` value. The `customRanking` is one of the way ranking
-can be configured in an Algolia index and follows a tie-breaking algorithm. You
-can find more information about the way it works either in the [official
-documentation][9] or in [this video][10].
-
-The default `customRanking` used by the plugin is [defined here][11] and use the
-date, weight of the header and position in the page by default. You can
-overwrite it to also take the `popular` flag into account like:
-
-```yml
-algolia:
-  settings:
-    customRanking:
-      - desc(popular)
-      - desc(date)
-      - desc(custom_ranking.heading)
-      - asc(custom_ranking.position)
-```
-
-This will rank popular posts matching your keywords before other posts. You can
-use either boolean or numeric values for the `customRanking`.
 
 [1]: options.html#nodes-to-index
 [2]: https://www.algolia.com/pricing
@@ -94,7 +62,3 @@ use either boolean or numeric values for the `customRanking`.
 [6]: https://www.algolia.com/pricing
 [7]: https://www.algolia.com/pricing
 [8]: https://github.com/algolia/jekyll-algolia/issues
-[9]: https://community.algolia.com/jekyll-algolia/options.html#settings
-[10]: https://www.youtube.com/watch?v=H6crAohtUBw
-[11]:
-  https://github.com/algolia/jekyll-algolia/blob/develop/lib/jekyll/algolia/configurator.rb#L27-L30

docs-src/src/getting-started.md

@@ -10,8 +10,6 @@ layout: content-with-menu.pug
 `jekyll-algolia` is a Jekyll plugin that lets you push all your content in an
 Algolia index.
 
-> While this plugin was created by Algolia, it is not an officially supported API client. It is possible that future major versions of Jekyll break compatibility, or require changes.
-
 ## Requirements
 
 You'll need:

docs-src/src/github-pages.md

@@ -70,16 +70,6 @@ You might have to edit the `branches.only` value to either `master` or
 `gh-pages`, depending on which branch is configured to be deployed in your
 GitHub Pages configuration.
 
-### Ignoring vendors
-
-Travis bundles all gems in the `vendor` directory on its servers, which Jekyll
-will mistakenly read. This will likely make the process fail. To avoid this,
-add `vendor` to the `exclude` list in your `_config.yml` file.
-
-```yml
-exclude: [vendor]
-```
-
 ## Adding the API Key
 
 The plugin will need your Admin API key to push data. Because you don't want to

docs-src/src/options.md

@@ -106,17 +106,7 @@ algolia:
 ```
 
 Settings defined here will take precedence over any setting you manually defined
-through the [Algolia dashboard][5] UI, though. If you'd like this not to happen
-at all, and only take the dashboard settings in account, pass `false` to the
-settings configuration.
-
-```yml
-algolia:
-  settings: false
-```
-
-We suggest users to at least run with the default settings once, so that the default
-relevance settings are set, which you can override via the dashboard after.
+through the [Algolia dashboard][5] UI, though.
 
 ## `indexing_batch_size`
 

docs-src/src/themes.md

@@ -13,12 +13,11 @@ Some themes already have `jekyll-algolia` embedded by default:
 
 - [Minimal Mistakes][3], by [@mmistakes][4]
 - [GaeBlogx][5], by [@SeraphRoy][6]
-- [Sakura][7] ([live demo][8]), by [@kimfucious][9]
 
 ## Add your own
 
 If you're maintaining a theme using `jekyll-algolia`, feel free to [edit this
-page][10] to add your theme to the list.
+page][7] to add your theme to the list.
 
 
 [1]: ./blog.html
@@ -27,7 +26,4 @@ page][10] to add your theme to the list.
 [4]: https://github.com/mmistakes
 [5]: https://github.com/SeraphRoy/GaeBlogx
 [6]: https://www.gaeblogx.com/
-[7]: https://github.com/kimfucious/sakura
-[8]: https://sakura.abts.io/
-[9]: https://github.com/kimfucious
-[10]: https://github.com/algolia/jekyll-algolia/edit/develop/docs-src/src/themes.md
+[7]: https://github.com/algolia/jekyll-algolia/edit/develop/docs-src/src/themes.md