You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
Like on posthog.com/questions, it'd be nice to have a separate JS widget that could be embedded on a page like /questions that aggregates all questions.
This feels like the killer feature to make this "a repo for every question users have ever asked about your product", which sounds a lot cooler than just a Q&A widget (or Stack0verflow/D!squs competitor).
This can come before #119 since it wouldn't require handling routing for question permalink pages - it'd just be a drop-in on a new static page. Clicking a question could open the full question in a modal, directly on the /questions page.
MVP idea
Questions page
This adds a couple UI elements since questions listed here don't have the context of displaying where the question was asked.
Shows most recent reply only, and has a link to view the full thread
Unless there's an answer marked as the solution, in which case that response, even if not the latest, is the one that appears
It links to the original page where the question was posted
Clicking "Show X other replies" opens a modal (or sidebar) with the full thread expanded
Search?
Big question is... do we include search? It could be a fast follow, but seems like having it would be huge. But since Docsearch is only available to YC companies, we'd have to figure out another solution - unless we just require you to use Docsearch to use this page. Edit: after discussing with @smallbrownbike, he explained how Docsearch wouldn't work because it's designed around crawling pages, and if we don't have specific pages to crawl, that poses a problem.
For a full GA release for Cloud (where we charge users), we'd probably roll our own search (using something like Algolia's API where we can send them data without them having to crawl for it) where we pay for it, along with handling other 3rd party services behind the scenes like Mailgun, etc.
Question detail
Summary
This doesn't massively change what we've already built, and since there are only a few new UI elements, it feels like we could build this with relatively low effort.
The text was updated successfully, but these errors were encountered:
Like on posthog.com/questions, it'd be nice to have a separate JS widget that could be embedded on a page like
/questions
that aggregates all questions.This feels like the killer feature to make this "a repo for every question users have ever asked about your product", which sounds a lot cooler than just a Q&A widget (or Stack0verflow/D!squs competitor).
This can come before #119 since it wouldn't require handling routing for question permalink pages - it'd just be a drop-in on a new static page. Clicking a question could open the full question in a modal, directly on the
/questions
page.MVP idea
Questions page
This adds a couple UI elements since questions listed here don't have the context of displaying where the question was asked.
Search?
Big question is... do we include search?
It could be a fast follow, but seems like having it would be huge. But since Docsearch is only available to YC companies, we'd have to figure out another solution - unless we just require you to use Docsearch to use this page.Edit: after discussing with @smallbrownbike, he explained how Docsearch wouldn't work because it's designed around crawling pages, and if we don't have specific pages to crawl, that poses a problem.For a full GA release for Cloud (where we charge users), we'd probably roll our own search (using something like Algolia's API where we can send them data without them having to crawl for it) where we pay for it, along with handling other 3rd party services behind the scenes like Mailgun, etc.
Question detail
Summary
This doesn't massively change what we've already built, and since there are only a few new UI elements, it feels like we could build this with relatively low effort.
The text was updated successfully, but these errors were encountered: