Request for Site Search Feature on Companion Site to Improve Resource Access

Andy C. · 2024-11-13T16:40:37.570Z

Would love to have a site search feature on the companion site. I have members trying to find a resource that was shared a while ago. It's past the Slack retention period, but it should be captured by Tightknit.

Request for Site Search Feature on Companion Site to Improve Resource Access | Tightknit Community

15 comments

· Sorted by Oldest

Zach H.
·
·
Ugh yes—we want to get this one built so bad. Just so we can help prioritize, which do you want first:
1.
keyword search
2.
semantic search (little bit of AI power here)
In the meantime, Andy C. have you seen our Related Discussions AI? Super powerful example of what’s possible.
Andy C.
·
·
Can't recall, you might've shown me, but I could use a refresher. 😛 Re: search -- whichever is easier to implement. I'm fine going based on keyword. E.g. the member asked for a resource posted by another specific member, so I'd start by searching for keywords (topic, member name).
👍1
Scott B.
·
·
💯 this one is really important. Especially needs to work for those with and without a companion site. The value for many in a community is the richness of content and being able to get back to it and suface that value, working around Slack’s retention policies, would be huge.
💯1
Zach H.
·
·
🙂 We actually have this working, but it requires a painful UX choice, which I think I need your help with. Let me make a quick Loom and get your opinions Scott B. Andy C.
Zach H.
·
·
Sneak peak of some new features: https://www.loom.com/share/e72d33e05bfb4e94b62527efca2dd548
Scott B.
·
·
I’m not quite clear on the search experience from the video. I was imagining the end user— a member of the community— doing a search on the companion site. So a traditional search box showing search results from all the content on the companion site. Not a chat query in Slack. Keyword search would be the start and you could expand and improve the accuracy from there. I don’t recall that end users have access to the app. Just admins or other users/groups with permissions.
Zach H.
·
·
Good to note. I needed to explain a bit better as an end user:
1.
Tightknit’s app is available to end users (we hide virtually all of App Home except for Events + Badges)
2.
But we do plan on making the app more relevant for end users in the future. In this case, it would be to enable a chat-based search inside of Slack.
3.
We would also have search on the companion site, but it seemed relevant to have it in Slack as well since it’s quicker and easier to get to from inside Slack.
I guess overall, that’s us saying we were planning on both options.
Andy C.
·
·
Yes, I think this is good enough for getting search live, versus having to install another app. (App installs are a limited resource on the Free plan, right?) My gut check says:
1.
Start with Slack chat since it's a) easy and b) functional and c) users aren't really using the Tightknit app today
2.
Figure out a fix for the chat bug while you make the app more functional for end users
3.
Fast follow on search in the companion site
➕1
Andy C.
·
·
My assumption is that most end users won't interact with the Tightknit app anytime soon, but rather with what Tightknit makes available in the channels they're using, and via the companion site and/or embeds. So I might flip 2 and 3 depending on effort/cost of implementing the companion site search.
👍1
Andy C.
·
·
++ For companion site search, it helps a ton with content discovery. Imagine someone comes into the companion site via search or referral. Right know they can browse, but that's about it. Adding search increases site stickiness and utility.
1
Zach H.
·
·
Thank you both for the deep-dive into your brains. I’ll see if Stephen C. and I can whip up a POC for this soon.
✌️2
Zach H.
·
·
Saturdays amirite? Scott B. Andy C. ++ Joel P. Gareth W. since I know you’ve both asked me for this before as well.
Disclaimer: All of this will change before final launch—especially the UX and the API. But this is community-built so feel free to throw in your asks now!
Scott B.
·
·
Good start. Maybe a few filtering options like which feed/channel to search in or include results from (could be pre or post to narrow search results); dates; people; etc. take some inspiration from Slack’s search variables?
🫡1
Joel P.
·
·
Filter — channels too!
🫡1
Andy C.
·
·
Zach H. - Killer! Exactly what I envisioned re: search. 🙏 Looking forward to playing with the Tightknit API more when our partner cohort wraps up.
1

Zach H.
·
·
Ugh yes—we want to get this one built so bad. Just so we can help prioritize, which do you want first:
1.
keyword search
2.
semantic search (little bit of AI power here)
In the meantime, Andy C. have you seen our Related Discussions AI? Super powerful example of what’s possible.
Andy C.
·
·
Can't recall, you might've shown me, but I could use a refresher. 😛 Re: search -- whichever is easier to implement. I'm fine going based on keyword. E.g. the member asked for a resource posted by another specific member, so I'd start by searching for keywords (topic, member name).
👍1
Scott B.
·
·
💯 this one is really important. Especially needs to work for those with and without a companion site. The value for many in a community is the richness of content and being able to get back to it and suface that value, working around Slack’s retention policies, would be huge.
💯1
Zach H.
·
·
🙂 We actually have this working, but it requires a painful UX choice, which I think I need your help with. Let me make a quick Loom and get your opinions Scott B. Andy C.
Zach H.
·
·
Sneak peak of some new features: https://www.loom.com/share/e72d33e05bfb4e94b62527efca2dd548
Scott B.
·
·
I’m not quite clear on the search experience from the video. I was imagining the end user— a member of the community— doing a search on the companion site. So a traditional search box showing search results from all the content on the companion site. Not a chat query in Slack. Keyword search would be the start and you could expand and improve the accuracy from there. I don’t recall that end users have access to the app. Just admins or other users/groups with permissions.
Zach H.
·
·
Good to note. I needed to explain a bit better as an end user:
1.
Tightknit’s app is available to end users (we hide virtually all of App Home except for Events + Badges)
2.
But we do plan on making the app more relevant for end users in the future. In this case, it would be to enable a chat-based search inside of Slack.
3.
We would also have search on the companion site, but it seemed relevant to have it in Slack as well since it’s quicker and easier to get to from inside Slack.
I guess overall, that’s us saying we were planning on both options.
Andy C.
·
·
Yes, I think this is good enough for getting search live, versus having to install another app. (App installs are a limited resource on the Free plan, right?) My gut check says:
1.
Start with Slack chat since it's a) easy and b) functional and c) users aren't really using the Tightknit app today
2.
Figure out a fix for the chat bug while you make the app more functional for end users
3.
Fast follow on search in the companion site
➕1
Andy C.
·
·
My assumption is that most end users won't interact with the Tightknit app anytime soon, but rather with what Tightknit makes available in the channels they're using, and via the companion site and/or embeds. So I might flip 2 and 3 depending on effort/cost of implementing the companion site search.
👍1
Andy C.
·
·
++ For companion site search, it helps a ton with content discovery. Imagine someone comes into the companion site via search or referral. Right know they can browse, but that's about it. Adding search increases site stickiness and utility.
1
Zach H.
·
·
Thank you both for the deep-dive into your brains. I’ll see if Stephen C. and I can whip up a POC for this soon.
✌️2
Zach H.
·
·
Saturdays amirite? Scott B. Andy C. ++ Joel P. Gareth W. since I know you’ve both asked me for this before as well.
Disclaimer: All of this will change before final launch—especially the UX and the API. But this is community-built so feel free to throw in your asks now!
Scott B.
·
·
Good start. Maybe a few filtering options like which feed/channel to search in or include results from (could be pre or post to narrow search results); dates; people; etc. take some inspiration from Slack’s search variables?
🫡1
Joel P.
·
·
Filter — channels too!
🫡1
Andy C.
·
·
Zach H. - Killer! Exactly what I envisioned re: search. 🙏 Looking forward to playing with the Tightknit API more when our partner cohort wraps up.
1