-
Notifications
You must be signed in to change notification settings - Fork 11
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
Template functions to enable building client side search index #57
Comments
Maybe the "non-html-content" example cover this use case? It generates a JSON file, not for a search index but I think the concept still applies. https://github.com/glaciers-in-archives/snowman/tree/main/examples/non-html-content Since that example was added the |
Yes I was looking at that one too, and thought that if there is function to retrieve HTML from an API (as in #54) you would just need another function that strips the HTML tags from such a retrieved string, leaving only plain text. That would complete the tools to create a JSON file for each page that could be compiled into an index I believe. |
These are the additions I have locally and intend to fully implement:
Together with the unsafe-view option, and the existing A question that still stands are what options |
It be interesting to have functions that would support building an index for client side search engines like lunr.
To me it looks like everything is already more or less in place, except for a function that would format HTML into plain text perhaps.
If that would be there, it could be possible to generate the required json files which then could be compiled into the search index by an external tool.
The text was updated successfully, but these errors were encountered: