New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document what LSI is actually doing #5033
Comments
@cfjedimaster FYI the |
@cfjedimaster Would it work to link out to docs of latent semantic indexing? Essentially it's finding a similarity between content on a word-by-word basis using a linear algebraic method. |
@parkr Sure. Ideally - a simple sentence ("This feature does X") with a link would be great. You can't go too deep on this page as it is a reference for a lot of stuff already. |
@cfjedimaster Sounds good to me! Would you mind submitting a pull request to add this to the docs? That content lives on the /cc @jekyll/documentation |
Would be glad to - at a conference this week - so it may be a few days. |
Thank you @DirtyF - I'm sorry I never got a chance to do this! |
github-pages
On the Variables page (https://jekyllrb.com/docs/variables/), the related_posts feature has this to say about it:
"If the page being processed is a Post, this contains a list of up to ten related Posts. By default, these are the ten most recent posts. For high quality but slow to compute results, run the jekyll command with the --lsi (latent semantic indexing) option. Also note GitHub Pages does not support the lsi option when generating sites."
So, my read of this is that --lsi does something fancy ("semantic indexing" sounds cool!), but the docs don't seem to actually say what this means. Is it parsing my content and attempting to find other posts that are similar to it? Is there any way to configure this? For example, what if I want it to just find similar content within the same category?
I guess my request is - it seems like this is a powerfully cool feature, but there seems to be literally no information about it. (If there is, maybe it could be linked to from here?)
The text was updated successfully, but these errors were encountered: