Use lunr.js to provide simple full-text search, using JavaScript in your browser, for your Jekyll static website.
Inspired by Pascal Widdershoven's Jekyll + indextank and Michael Levin's Sitemap.xml Generator plugins.
This Jekyll plugin handles the generation of a lunr.js
compatible .json
index file. Runtime search configuration is provided by a simple jQuery plugin.
It allows full-text search of all your Jekyll pages and posts. Executed by the client without any server-side processing (outside of serving static files).
Write to Jekyll's Gemfile:
gem 'jekyll-lunr-js-search-multilingual', git: 'https://github.com/fortran-team/jekyll-lunr-js-search-multilingual'
to install from this git repo or
gem 'jekyll-lunr-js-search-multilingual'
to install from 'https://rubygems.org'
Modify your Jekyll _config.yml
file to include the Gem:
plugins:
- jekyll-lunr-js-search-multilingual
The content from all Jekyll posts and pages will be indexed to a _site/js/index.json
file ready for lunr.js to consume.
This happens each time the site is generated.
A JavaScript code is provided in _site/js/search.min.js
to handle
the configuration of lunr.js with the search index JSON data generated by this plugin.
To use it, you must add a script reference to the bottom of your nominated search page
<script src="{{ site.baseurl }}/js/search.min.js" type="text/javascript" charset="utf-8"></script>
<form action="{{ site.baseurl }}/search" method="get">
<div class="form-group">
<input class="form-control" type="text" name="q" placeholder="Search" id="search-query">
</div>
</form>
Search happens as you type, once at least three characters have been entered.
Providing the form action and specifying the get
method allows the user to hit return/enter to also submit the search.
Amend the form's action URL as necessary for the search page on your own site.
<section id="search-results" style="display: none;"></section>
This may be initially hidden as the plugin will show the element when searching.
{% raw %}
<script id="search-results-template" type="text/mustache">
{{#entries}}
<article>
<h3>
{{#date}}<small><time datetime="{{pubdate}}" pubdate>{{displaydate}}</time></small>{{/date}}
<a href="{{url}}">{{title}}</a>
</h3>
{{#is_post}}
<ul>
{{#tags}}<li>{{.}} </li>{{/tags}}
</ul>
{{/is_post}}
</article>
{{/entries}}
</script>
{% endraw %}
Note the use of {% raw %}
and {% endraw %}
to ensure the Mustache tags are not stripped out by Jekyll.
The fields available to display are as follows:
List of search result entries (mandatory).
Raw published date for posts, or null for pages. Can be used to toggle display of the following dates in the template {{#date}}has a date{{/date}} {{#!date}}no date{{/date}}
.
Post published date, formatted as 'yyyy-mm-dd', to be used in a html5 <time datetime="{{pubdate}}">
element (posts only).
Post published date, formatted as 'mmm dd, yyyy', such as Oct 12, 2012 (posts only)
Title of the Jekyll page or post.
URL of the Jekyll page or post that can be used to create a hyperlink <a href="{{url}}">{{title}}</a>
.
Categories (array) of the Jekyll page or post, can be used in a loop {{#categories}}{{.}} {{/categories}}
to list them.
Tags (array) of the Jekyll page or post, can be used in a loop {{#tags}}{{.}} {{/tags}}
to list them.
Boolean value, true if current result element is a post. Can be used to toggle display of specific elements in the template {{#is_post}}is a post{{/is_post}}
<script type="text/javascript">
$(function() {
$('#search-query').lunrSearch({
indexUrl : '{{ site.baseurl }}/js/index.json', // url for the .json file containing search index data
results : '#search-results', // selector for containing search results element
template : '#search-results-template', // selector for Mustache.js template
titleMsg : '<h1>Search results<h1>', // message attached in front of results (can be empty)
emptyMsg : '<p>Nothing found.</p>' // shown message if search returns no results
});
});
</script>
Add the following exclude_from_search
setting to any page's YAML config.
exclude_from_search: true
Or add an array of exclusions (as individual regular expressions) to the site's _config.yml
file.
lunr_search:
excludes: [rss.xml, atom.xml]
You can also configure a stopwords file, and a minimum length of word to be included in the index file. This can be done by adding a search block to _config.yml
. The default values are:
lunr_search:
stopwords: "stopwords.txt"
min_length: 3
The stopwords file must consist of one word per line, in lowercase, without punctuation.
You can choose to store index.json
, search.min.js
and lunr.min.js
in a different directory like this:
lunr_search:
js_dir: "javascript"
Search plugin is deployed to 10consulting.com/search. Some example search queries are /search/?q=git, /search/?q=cqrs.
It also features on-demand loading of the search plugin .js
when focusing into the search field on the homepage. Look at the browser network requests clicking into the search input.
I write below how to code and build Jekyll plugin jekyll-lunr-js-search-multilingual
on Windows
but you can do it everywhere, because instruction is universal, excepting hyperlinks on software.
If you want to code and build the plugin, you need:
Ruby
code:<repo_root>/lib
JavaScript
code:<repo_root>/js
Ruby Bundler
by executing command:gem install bundler
bundle install
NodeJS Bower
by executing command:npm install -g bower
rake build
<repo_root>/lib/jekyll_lunr_js_search/version.rb
rake build_gem
<repo_root>/lib/jekyll_lunr_js_search/version.rb
rake publish_gem
If you include the .js
and .js.map
files your browser developer console will link to the unminified code.