Tag Info

Underlining non-link text is a sort of usability crime. Underline is a standard way of visualizing links, especially when the default blue isn't use for links, so underline can confuse web users as to what's a link. Even in desktop applications, underlined text often means "I'm clickable". Everyone knows that text that’s underlined, or is a different ...

I built a comment moderation system for a site with 50k new posts a month where each post could have N comments. Our approach was to use flag for moderation buttons near each post and on each comment, which executed an ajax call to the moderation backend and notified the user of the action. In the backend, moderators had access to two separate lists ...

Yes, there are valid use cases, all of which probably are in a very specific field of work/study where underline has a particular meaning. An example: if your users want to write things in RuleSpeak (a notation system for SBVR documents) in the CKEditor, convention dictates they underline terms. An image of what you typically see in these documents: ...

Is there ever a valid use-case for having text underlined on a website? Yes, and your question contains the answer : the client has taken it upon themselves to emphasize text by underlining it So emphasize seems to be a valid use case to some people. I do not think either this people are doing wrong according to you (or more widely agreed ...

Assuming the "U" button puts selected text in the <u> element, there might be a very narrow use case for it. From the most recent HTML spec from the WHATWG: The u element represents a span of text with an unarticulated, though explicitly rendered, non-textual annotation, such as labeling the text as being a proper name in Chinese text (a Chinese ...

for a 40+ user group, avoid 'manage' itself. Make the links even more self-explanatory. 'Create New Page' 'Edit a Page' 'Add/Edit Categories' 'Approve/Remove Comments' non-tech savvy ppl have a tendency to get lost in the page structure, so a link called 'Pages' which has links to 'add page' and 'edit page' will add to confusion. Ofc if you have 20+ links ...

The goal of a TOS document is legal protection. A plain text / HTML document does this better than a PDF document, so there is little (if any) benefit to including a PDF version. The UX question should really be about making the TOS more human (rather than lawyer) readable, as that is an area where most sites can improve a lot.

Are you looking for an expression builder/predicate editor? I have some examples in this post, #6 build an expression: http://designingwebinterfaces.com/15-common-components The example from Wufoo allows for any or all of the conditions to be applied. What we found in testing in numerous different industries is that most non-programmer people don't ...

There are a number of factors, some of which are beyond the interface's control like the nature of the content, but one factor in your control is how to handle identity. Disqus published a blog post and infographic a few months ago looking at policies of real-names vs. pseudonyms vs. complete anonymity, and found that pseudonyms (stable but user-defined) ...

You are confusing the user interface with the information architecture of the site. Just because you have a hierarchy that shows the product in two places does not mean that you should maintain two separate pages of product information, pricing, etc. For example, on a clothing store you might list stuff under /clothing/summer/product, and you might also ...

I'm a content writer and I feel your pain about "content as after-thought" or sometimes "not important." So glad you posted this question. Sometimes it helps to show clients what their competitors are doing -- who shows up first in search results in their business categories, what those websites are saying, how user-friendly the sites are, and especially ...

There is a very nice paper for Information Architecture (which is only a module of what you're probably asking) here If you feel that, that is what you're looking for, you might want to take a deeper look into Information Architecture for the World Wide Web: Designing Large-Scale Web Sites Although IA doesn't solve the problem directly, you'll find that it ...

I'm not sure this can be 'solved' by a Pro and Con list being discussed. There are at least 3 aspects that should be considered: 1. User Experience Making sure the site is usable for both consumers as well as internal people. Very important and usually the domain of UX people. 2. Technical expertise Making sure the CMS fits into the most likely existing ...

Irith, This is how I understand your question: "How do I store information in a table so I know which widget it belongs to?" Is that correct? If so, you're describing a simple relational database. A solution would be to have three tables: Content Platform list Widget list You relate a piece of Content to a value in the Platform list and the ...

When it comes to organize stuff in meaningful chunks of information, the philosophy you are about to follow are the Principles of Grouping. In your case, making chunks of information meaningful to the end user, the similarity rule is most prominent. As this is a widget I assume that you will divide content with horizontal rules or different screens. Either ...

Spreadsheets are useful up to a point but they are unmanageable for large amounts of rich content. I've been using GatherContent recently. I've not yet used it on a multi-language project but I imagine you could either create a site structure for each language version or include a field to collect each language on each page (e.g. each product page would have ...

I've worked on a few projects recently where, for whatever reason, the decision was made to move away from integrating with an existing CMS and instead to design management interfaces and processes as part of the project. This is great in theory because you have the opportunity to design something that meets the particular needs of the project. However, you ...

If the client will be using the CMS to update the site, then UX should certainly have a hand in creating the content management system. Start with an inventory of all the content types your client will be using. From that you can write up a short list (5 or 10 items) of things that the CMS needs to do. Then do your research -- is there an existing CMS that ...

What are the pros and cons for making this the responsibility of the UX team on a project? Pros: end users end up with a CMS tailord to their needs as such the CMS is tailored to the business's needs Cons: for whatever reasons, IT execs prefer to purchase SharePoint rather than create or research decent software. Potential arguments It's usually ...

You can also have quarantine periods -- that is, autoapprove only after say, x seconds or minutes, giving you the option of sampling requests. Combined with Mechanical Turk, you can moderate items for a few cents, like http://socialmod.com does. What could scale better is you could also have triggers for quarantining such as number of links in post, ...

I have come across this only few times when I was building Annual Report websites. Unfortunately the link I was going to show is dead now but there were instances in the report that certain text had to be underlined and was not part of the header or was a link. Though text only appeared in the financial table's row header cells. So you might argue that ...