Tag Info

Hot answers tagged

6

What about GitHub-flavored Markdown? It leaves embedded newlines as line breaks, with no need to insert two spaces. See https://help.github.com/articles/github-flavored-markdown#newlines.


5

In a forum thread, users are likely to want to go to the start, or end of the thread fairly often, as well as possibly a particular point in the thread. That makes forum threads a poor candidate for infinite scrolling, as to get to the beginning (or end depending on how you set up your forum), someone will have to scroll through the entire thread. And some ...


4

Will your team have a presence in discussions and responding to questions from your users? If yes, I would say that a forum on your own site is much better. Most forum packages will let you configure roles or groups so that users who are from your team can have a beacon of some sort next to their avatar or name, which makes it easier for users to identify ...


3

My understanding of this is that the original uppermost content becomes the anchor of the interaction. Everything below it is a reply. To reply to a reply, you'd need to set that as an anchor (in many UX cases). Tweets in reply, for example, unfold the whole conversation in this manner with a "More" option if there's more than X-number of Tweets threaded. ...


3

Tree like forums Best to use when you are likely to have or need multiple conversations at once in separate threads. Possible to have side conversation threads without derailing any other point. Easy to ignore conversation threads that you aren't interested in. Difficult to follow the overall chronological flow of a conversation Tends to be messy with many ...


2

They are applicable in different types of circumstances. The tree structure is good for when the subject is of a discussion nature. There is no clear end to the main subject and it doesn't aspire to be. The topic is expected to evolve and go on until it dies out on its own. The flat structure is best for when there's no interest in letting a subject carry ...


2

I strongly recommend reading this excellent article on best practices for community specific design. From a design perspective and to ensure you allow for easy collaboration and contribution, To quote the article : Browsing Community sites, like any other website, need to facilitate browsing using design tactics > that immediately tell the user ...


2

If you have a solid handling of security in your assumed database driven website, a WYSIWYG editor is probably the best choice. By that I mean you need to handle all edits through stored procedures and never ever use "INSERT INTO..." in managed compiled or (worse) scripted code. Say yes to the question "I use stored procedures everywhere" and you're most ...


2

If there are other systems / information out there that are already performing the function that you need then there's no need to reinvent the wheel. That just causes fragmentation throughout the web; something that doesn't benefit the user in the grand scheme of things. For example, take a site about film reviews. If they're discussing the film and want to ...


2

Doesn't necessary, but could be very useful I find it useful for customer support. Indeed, discussion is needed when site support is weak and there is a chance to get help from the community. Also community could be more trusted source than internal support. Hovewer, context, type of goods, and overal experience should be considered. For technical goods ...


1

I would suggest you starting from simple ready-to-go solution: Uservoice or GetSatisfactions. They both have different modules which you can enable/disable. The main modules are: forums, support tickets, ideas, feedback. Look at their demos to think about how they can be integrated into your shop. The main pro's here installation - some minutes slick ...


1

I can see why you wouldn't want to use "Ask a Question" since the user may not have a question. I'd be hesitant to use the terms "thread" and "post" since they are jargon words for online forums. While they are the correct words for this context, your non-technical users may not be familiar with them. I would vote for Create a New Topic Start a New Topic ...


1

Tree-like Forum - Best way a forum can be with repetitive conversations sprung from one question but emerges to look at side conversations. Its organic, allows conversation in a humanely form (since you discuss lots of things simultaneously).But sometimes takes so much of side conversations, that filters your main context, and can be tough to track,people ...


1

The smaller the amount of topics/threads you expect the smaller the initial amount of boards/categories. For example, you can start with "Technical Problems" and later divide into "Technical Problems Product A" and "Technical Problems Product B". To find a good solution I would a: google for "information architecture" b: look at/search for comparable ...


1

I suggest to split this into two points: a) Page loading speed and data traffic b) Information context Page Loading Speed From a loading speed of view, it doesn't make sense to load all data. Is the user only interested in the latest response (or the few latest added messages), he has no advantage of having all the data on the site. Information Context ...


1

Here is an interesting article that generated some interesting ideas on this: http://blogs.msdn.com/b/jledgard/archive/2005/07/28/444531.aspx In response to your specific questions - You could run a small sample usability test with a simple prototype on some users (as you've suggested) and take down your own findings. I haven't come across any specific data ...


1

I think the answer is not about having precise stats on suggested questions, but about providing the best exit points to your users in that context in general (known UX patterns). Suggested questions only being one of them. You can still ask "yeah but are suggested questions effective?". It still comes down to what your users are doing on a case by case ...



Only top voted, non community-wiki answers of a minimum length are eligible