-
Notifications
You must be signed in to change notification settings - Fork 27
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
Search engine #11
Comments
In a discussion on the Lift ML about using Pamflet for our documentation the issue of lack of searchable content came up :) It's not a deal breaker as we can just embed a google search bar for now I just wanted to let you know to give you some extra motivation ;) Haven't convinced the entire Lift community to switch to Pamflet yet but I'm still trying ;) |
I lost some motivation to do this when I finished the combined pages feature (e.g. http://pamflet.databinder.net/Combined+Pages.html) The use case is handled at least as well by the browser text searching features as it would be by any javascript based search index. But there's a big question of how that should be presented so that users think to use it that way. |
Oh yeah - I hadn't thought about that. But you're right, I don't know how to make this option apparent quickly to the users either :) |
We can display a search box and button on every page. When you click When people figure out what it's doing they'll probably use the |
Sounds acceptable to me ;) Between this and the TOC it should be enough for people to find what they're looking for IMO |
Implemented in JS, with a generated token index in json. (Seriously!)
The text was updated successfully, but these errors were encountered: