Tag Info

New answers tagged

1

Litmus has some good recommendations on this that I've been following: Use a good base font (web safe) Enhance for the clients that support it Beware of Outlook As long as you are prepared for the worst case scenario (with a web safe font), I think it's OK to offer a better experience for those who can support it. The more similar the typefaces are ...


0

If you're using JIRA, you can use SourceTree to document projects and track changes for Git and Mercurial. I think this is a very good question and probably something that hits us most of the time, because we need to work with systems we're comfortable with, then we need to work with systems the client is comfortable using. Personally, I like to use a ...


0

Some thoughts and ideas here (not sure if it constitutes and answer): Self-evident documentation - this can be achieved by putting it together with the design framework that you use and/or modify. Lots of work upfront but much less work later down the track. Document-as-you-go - this requires some effort spread across the project, and can be detached from ...


0

Have you considered the Atlassian marketplace? They've got some plugins and there might be one for your e-mail software to quickly upload e-mails to Confluence: https://marketplace.atlassian.com/ My team experimented with Bootcamp for awhile also. I really liked it, the interface is simple and easy for anyone on our team to learn. Lets you upload ...


0

Well, everything is almost right and wrong, and especially in www you can decide if something is right or wrong, based on user's needs and goals (although this could be a general life approach:) By the way, keep in mind implementation complexity and time. But let me give you an example based on your resources. You have a "company-thing" like Frank Chimero's ...


0

I don't think it should be the norm, it feels rushed or forgotten. I've noticed users prefer simply clicking hyperlinked emails over filling out basic email forms containing first name, last name, email. This is based on usability tests I've conducted on contact pages ranging from websites with 500-100k users. This led me to believe that most users prefer ...


4

It is not a pattern - it is an error and poor usability. You have shown a pathological examples. Both elements looks like menu item, not an e-mail address. In this two cases what should happen is opening contact page, not e-mail. Affordance tels us that - this elements are percieved as items in menu which open some pages. If they do not do that, user has ...


1

I spent a lot of time on cart abandonment in a large ecomm setting. I can tell you what we found and what I've experienced in the wild while investigating. Don't re/pre-populate the cart.* I've heard of this idea, but never seen it used in any real world setting. There are too many complications from a UX perspective. Ultimately, those problems will result ...


1

Your con for email authentication by URL is that the URL is longer and scarier looking than the shorter URL to the location where people can enter a code. But you can simply hide the long and scary URL behind a bright and inviting button. True, you would have to display the entire URL for people to copy and paste in their browser, because some email clients ...



Top 50 recent answers are included