Replace default search plugins with search-plus - #675
Merged
Conversation
✅ Deploy Preview for fluentd-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
What about honkit-plugin-search-plus? |
Watson1978
changed the title
Contributor
Author
|
Replaced to honkit-plugin-search-plus |
kenhys
reviewed
Aug 10, 2026
The default search stack (search + lunr plugins) had two practical problems on docs.fluentd.org: * The generated search_index.json is about 6.7 MB (837 KB gzipped) and is fetched and parsed eagerly on every page view. Queries typed before loading completes throw "Search has not been initialized" with no visible error, and the typed query is never re-executed once the index becomes ready. As a result the search box appears broken right after page load. Since the length of this window depends on network and cache timing, the behavior also looks inconsistent across browsers. * lunr applies an English stopword filter, so common words such as "for" always return "No results matching" even though they clearly appear in the documentation. Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
kenhys
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default search stack (search + lunr plugins) had two practical
problems on docs.fluentd.org:
The generated search_index.json is about 6.7 MB (837 KB gzipped)
and is fetched and parsed eagerly on every page view. Queries typed
before loading completes throw "Search has not been initialized"
with no visible error, and the typed query is never re-executed
once the index becomes ready. As a result the search box appears
broken right after page load. Since the length of this window
depends on network and cache timing, the behavior also looks
inconsistent across browsers.
lunr applies an English stopword filter, so common words such as
"for" always return "No results matching" even though they clearly
appear in the documentation.