Open balessan opened 8 years ago
sylvainlb
commented
8 years ago I'm wondering if it wouldn't make more sense to focus on server side search engine first. Don't you think the client side search would be very limited in terms of scalability and performance?
balessan
commented
8 years ago My point here is to include basic search capability to move from a static to the beginning of a user-oriented application, to make it useful. Client side SE will be limited yes, but we do not have the infrastructure to deploy a server-side one yet, and the goal is only to make a point.
So, my opinion here:
Prototyping :p
sylvainlb
commented
8 years ago ok, makes sense. I'll work on server side SE and will keep you posted.
2016-04-10 20:19 GMT+02:00 Benoît Alessandroni notifications@github.com:
My point here is to include basic search capability to move from a static to the beginning of a user-oriented application, to make it useful. Client side SE will be limited yes, but we do not have the infrastructure to deploy a server-side one yet, and the goal is only to make a point.
So, my opinion here:
- First client side with limited capability
- Then move forward to something else
Prototyping :p
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/assemblee-virtuelle/AV-POC/issues/3#issuecomment-208035325
On the Proof-of-concept, it would be nice to be able to execute full-text search in both projects, individuals, ideas and related posts.
A solution would be to add a search bar driven by a combination of lunr.js (equivalent of solr) or fullproof and the IndexedDB for storing the indexed data.
0 - Add a hardcoded list of knowns hostname to the config object so that anything will be empty 1 - Get the hostname lists from the localStorage 2 - Request ideas, projects and individuals containers for indexing 3 - For each individuals, request its blog posts lists 4 - Store that in IndexedDB 5 - Index everything using lunr.js 6 - Enjoy the search feature.