Add global ElasticSearch based Search #1

mariuswilms · 2014-09-27T14:05:43Z

The search should be reachable via a magnifying glass icon in the upper right portion of the screen inside the main nav.

Clicking on the icon will bring up a full screen search. The search will be "as-you-type" and JS driven so we'll need an api endpoint under /api/search. AJAX requests should be queued and cancelled to save processing power if a newer request is enqueued.

The app needs a command which will refresh the search index and which will be hooked up in config/crons.default.

We'll be using the Elastica PHP library as a dependency. The dependency will need to be added to composer.json.

The index builder will add items for:

li3_bot\models\LogMessages
li3_docs\models\Symbols
the manual (full pages)
the specs (full pages)
blog items via tumblr API
Allows indexing full web pages.
- These can be manually provided. The title will extracted automatically from the title head tag.
- All pages inside the website should be provided i.e. development, community.

The text was updated successfully, but these errors were encountered:

rapzo · 2014-09-27T14:16:57Z

I'm a bit flooded but i think i can manage something. Can it be developed separately and added with composer?

I'd scratch the li3_bot part, it's been dead for years.
Could we add external sources, like a call to stackoverflow's api with a refined search with "li3" or "lithium" & "php", or even searching "li3_" in github in the same way?

mariuswilms · 2014-09-27T14:24:11Z

Thanks for offering help, definitely needed and appreciated.

As most parts are application specific I'd start with developing it inside the app. But if you see parts that can be generalized and factored in a plugin that would nice too. Maybe a combination of both. I just wouldn't make it a bigger project.

li3_bot is alive and kicking as I've reworked most parts last night/day. The logs are a viable source of information.

Yeah a GitHub search and Stackoverflow search would be nice as well! Maybe those entities can then be kept in an index named external or tagged accordingly?

Visually Design-wise I can take care of that and JS-wise if needed (done it a couple of times) just ping me once you're ready with the backend. I imagine somethine like in the attached screenshots.