3 votes
Use same architecture to create community FAQ
As a start up, I want to hear new ideas, but I also want to build a repository of use case FAQ.
We launched, and feedback is coming in three categories:
1) bugs -
2) where is / how do I? (where it's there, it's just too complicated or not obvious enough)
3) it would be great if it . . . [feature additions]
The architecture you currently have would be awesome for all three if we could categorize them as admin (or community, with admin override) and have #2 types build a search able FAQ section.
vineet
[Part 2 of 2] Beyond suggestions and bugs, there are two other popular categories that forums are used for and could benefit from such a lightweight interface: Questions and Tips. In both of these cases, votes can be just used in ranking the questions/tips, and possibly be good just implicitly by the number of user visits. Another feature could be for more karma to providers of tips rated highly.
6 months ago
vineet
[Part 1 of 2] One nice thing about the uservoice is that it feels very lightweight. A user just needs to start typing and not need to do an exhaustive search. This part is really independent of voting. Voting is a nice add-on (IMO) - which actually makes users feel like they need to prioritize what they are asking for.
6 months ago
cainlevy
Interesting - how do you think voting might play a part in the searchable FAQ?
6 months ago