Skip to content
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.

Evaluate Algolia Search #150

Open
bhaskarmelkani opened this issue Jan 29, 2019 · 5 comments
Open

Evaluate Algolia Search #150

bhaskarmelkani opened this issue Jan 29, 2019 · 5 comments
Labels

Comments

@bhaskarmelkani
Copy link
Contributor

Evaluate Algolia Search

Currently, the theme uses lunr for searching inside the documentation. There are some pitfalls for using lunr [the generated index file(lunar.json) can grow super big with the data in the documentation, support for multiple languages like Chinese, etc].

This ticket is to discuss the pros and cons of this implementation in the theme and decide if its worth while to do this change and replace lunr with Algolia.

@miaojf
Copy link

miaojf commented Jan 31, 2019

@bhaskarmelkani
Copy link
Contributor Author

bhaskarmelkani commented Jan 31, 2019

hexo.io also uses Algolia for in-site search.

Here's the issue for it. hexojs/site#129

@rbarilani
Copy link
Contributor

@miaojf @bhaskarmelkani Seems cool but if I understood correctly, algolia is a service as Google Search that requires to have your site crawled, which is fine for public sites but not for private sites.

So I say that we should support both (lunr.json) and algolia, up to the user to decide which one to use.

WDYT?

@miaojf
Copy link

miaojf commented Feb 1, 2019

It's nice to be configurable ,
Do not generate related imports without configuration

@bhaskarmelkani
Copy link
Contributor Author

bhaskarmelkani commented Feb 1, 2019

Yes, Algolia will provide both searches inside the document using the already generated index and also providing other functionalities like crawling.
There are some plugins to enable Algolia for Hexo.

These plugins can be used in the theme with little customization if there is a need.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants