Skip to content
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

Open
n8han opened this issue Jul 17, 2011 · 5 comments
Open

Search engine #11

n8han opened this issue Jul 17, 2011 · 5 comments

Comments

@n8han
Copy link

n8han commented Jul 17, 2011

Implemented in JS, with a generated token index in json. (Seriously!)

@mads-hartmann
Copy link

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 ;)

@n8han
Copy link
Author

n8han commented Feb 8, 2012

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.

@mads-hartmann
Copy link

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 :)

@n8han
Copy link
Author

n8han commented Feb 8, 2012

We can display a search box and button on every page. When you click
search, we load the combined pages and initiate a search-in-page with a
prettier version of this: http://www.seabreezecomputers.com/tips/find.htm

When people figure out what it's doing they'll probably use the
in-browser search, but either way, mission accomplished!

@mads-hartmann
Copy link

Sounds acceptable to me ;)

Between this and the TOC it should be enough for people to find what they're looking for IMO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants