I'm working on a project to revamp site search on a decent-sized woocommerce site. I'm doing a proof of concept right now on my dev site to see if typesense and swiftsearch looks like a good combination to build on. So far I really like the idea of not burdening php with search requests 👍 .
If i move forward with this combo I can already see there are at least a couple things that I'd want to add to swiftsearch and I'm just wondering how open you are to PRs or whether it would be better for me to work on a private fork.
Here's the two thoughts I have so far just getting started:
- I'd like to be able to keep separate collections for my production and my development servers. I think the easiest way to do that would be to have a configurable prefix for the collections that are created in typesense so instead of
posts there could be dev_posts, prod_posts, etc. So just adding that prefix would likely be the first PR. probably wouldn't even need an admin UI for this; just a filter hook.
- the woocommerce site I'm working on has both products as well as signficant post content and I'd like to present those two collections of search results visually differently. Maybe this is just a template issue - i haven't started to dig into it yet - but i have a feeling that it might be necessary to include something in the results data labeling which collection each result came from in order to allow it to be styled differently.
I'm working on a project to revamp site search on a decent-sized woocommerce site. I'm doing a proof of concept right now on my dev site to see if typesense and swiftsearch looks like a good combination to build on. So far I really like the idea of not burdening php with search requests 👍 .
If i move forward with this combo I can already see there are at least a couple things that I'd want to add to swiftsearch and I'm just wondering how open you are to PRs or whether it would be better for me to work on a private fork.
Here's the two thoughts I have so far just getting started:
poststhere could bedev_posts,prod_posts, etc. So just adding that prefix would likely be the first PR. probably wouldn't even need an admin UI for this; just a filter hook.