Author Archives: Kadir Topal

The quest to solve all the issues. Part 1.

Last fall we did a report on the SUMO support forum to assess the current situation, so we could make informed decisions about what to work on next. In particular, we wanted to know  what was keeping us from solving all issues that were brought up in the forums. After analyzing several thousand support forum threads, we came up with a number of suggestions and decided to implement the low hanging fruits right away. Among those low hanging fruits were:

  • We were dropping the ball on users, not getting back to them.
  • We were telling users that we didn’t know how to solve their problem.
  • There were off-topic issues that we didn’t know what to do with.
  • People often didn’t tell us when a solution didn’t help, because it was hard to do so.

We knew that we had to address these issues, if we wanted to increase the “solution” rate. So, we came up with a number of programs and platform changes late last year to eliminate those issues. Specifically, we had the following planned:

  • Make it easy for contributors to tell what needs their attention, so we can drop the rate of cases where we leave them hanging to zero.
  • Extend the reach of the helpdesk to cover those cases where our community doesn’t know how to move forward, and by marking such threads as “hard” allow for specially motivated contributors to become focused on hard issues.
  • Mark things that are off-topic as such, so we can hide them from the general audience and can take special care of them.
  • Users can mark an issues as solved from their email, but telling us that the solution didn’t work required them to log-in. A big an unnecessary hurdle. People should not need to log-in. They should just click on the link in the email and start telling us it didn’t work.

I’m happy to say that we were able to follow through with our plans and those solutions are active on our production systems already. We are now seeing the first results of those changes and I’d like to share them with you. However, I need to preface this with a warning: Unfortunately the timing for the roll-out of those changes was as bad as it gets. First we had the release of a Firefox version that coincided with the launch, then we had the Christmas holidays and then new year. Each of these events leads to highly irregular usage patterns on SUMO, so we need to take the data with a pinch of salt. However, without any further ado, here are two charts, that show the first results:

Questions states on a higher level

Questions states on a higher level

Questions states on a higher level as a stacked area chart

Questions states on a higher level as a stacked area chart

You can see very clearly that we have significantly reduced the number of cases where we left people hanging, the cases that needed our attention. That was one of the primary goals of our efforts and it seems like we’ve achieved that part with great success. Unfortunately this didn’t translate directly into an increase in the “solution” rate yet, but as I mentioned before, the previous few weeks were highly irregular in terms of usage patterns, so we’ll need to wait a little longer, before we can say reliably how our changes affected the overall goal of increasing the “solution” rate.

In the mean time, we are coming up with ideas on how to challenge the bigger issues, now that we have taken care of the low-hanging fruits. I’m incredibly excited about the opportunities in front of us and the new ways we’ll try to address them with. If you are interested in taking part in that discussion, head over to the community discussion forums, and join us in our quest to solve all the issues.

[Your Feedback Needed] A simplified and focused L10n dashboard

The localization dashboard is going to see major changes soon to make sure that it is as simple and focused on the tasks at hand as possible. We need your feedback to make sure we are making the right decisions. If you are using the L10n dashboard and want to take part in the discussion, please had over to the following bug, have a look at the attached mockup, and leave your comment: https://bugzilla.mozilla.org/show_bug.cgi?id=939832

The following is a quick summary of what changes we are making and why.

One of the biggest strength of the platform that SUMO is built on is the fact that localization has been one of the key design components. We created several localizer personas when we designed Kitsune and had them in mind when we made decisions early on. One of those decisions was to create an L10n dashboard that would present all the data that localizers might need to get their job done.

Since the early SUMO was rather small and focused on a single product, the L10n dashboard worked pretty well. Since then however, we have increased the scope of SUMO and added several more products and more functionality. The L10n dashboard grew organically during those times to cover more products and functionality.

Now seems like a good time to take a look at the tasks that localizers are faced with today and bring the the L10n dashboard into shape again. Rosana and I started that discussion with one thought: The L10n dashboard should answer one question and should do that as good as possible: “What should I be working on next”.

The current L10n dashboard present a lot of data, but unfortunately not all of it is relevant or actionable. While that data should still be accessible, it doesn’t make sense to present it as prominently as we are doing today. Having the one question in mind we cut back a lot of unnecessary information and came up with a streamlined, simple interface that bundles information and presents only things that localizers need at any moment. When we printed the current L10n dashboard out, it took covered 4 full pages, the current proposal can fit onto a single page.

Here you can see a mockup of our proposed L10n dashboard:
localization dashboard

To summarize the changes we made:

  • The product picker that is currently a drop down becomes a visual product picker. The product icons should be rather small though, to make sure people can see as much of the L10n dashboard above the fold as possible.
  •  The overview section is slimmed down by removing the “administration” articles and the explanatory text. We oversize the progress bar for the top 20 articles, so that updated articles lead to visible changes. The logic of orange -> green stays the same. We then remove the explanatory text and add it to the overview section items as tooltips. The now free space is used for bigger progress bars.
  • The actual content section is separated into Localization and Review
  • The Localization tab has a list of articles that need attention, where need attention is defined as “needs translation, needs update, and needs immediate update”. The list is ordered by most views in the last 30 days. Thus we are doing away with all other lists on the L10n dashboard.
  • Each article in the “needs attention” list shows below it the templates that are included in the article that need attention. Same rules for “need attention” as before.
  • The review tab has a list of top 20 articles needing review with a link to all articles needing review. The templates are listed the same way as on the localization tab, only templates that need review or “need attention” are listed.

If you want to take part in the discussion, please had over to this bug and leave your comment there: https://bugzilla.mozilla.org/show_bug.cgi?id=939832

We need your feedback to make sure we are making the right decisions with these big changes.

Thanks!
Kadir

Your feedback for the new SUMO support forum needed

Hi,

We need your help in designing the presentation of the support forum statuses. If you have been following the contributor or the platform meeting, this is probably old news for you, but for everyone else: Big improvements to the support forums are coming.

A few month ago we set out to evaluate the support forum. The insights were partially surprising and partially confirmed our suspicions. The good news is: We are helping a huge number of people with their Firefox questions. However, the report also showed that we have two big issues:

  1. In too many cases people don’t come back, so we don’t know whether we are really helping them
  2. In too many cases we leave people hanging when they come back, either because we forget to get back to them, we’re out of our depth, or the question is not completely about using Firefox.

This quarter we set out to address these issues one by one:

  • We are looking into ways to let people easily reply in the forums when they receive a message from us, ideally they won’t need to even log in. This should increase the number of forum threads where we do get feedback on the solution we provided.
  • We have enlisted the help of the SUMO helpdesk to take care of issues we can’t solve alone. We can now escalate questions and have them spend time with us and the users to find the solution.
  • The heldpesk will also cover questions that are not completely about using Firefox.
  • We have introduced a new model for questions, specifically “states”. A question either “needs attention”, is “responded” to or is “done”. This way we can very easily tell which threads we haven’t responded yet, needing our attention the most.

Now, the challenge is to find a way to present all of this information in a way that is useful for as many contributors as possible. That includes current and future contributors. We have created a first mock-up, that you can see here: http://note.io/182uu9X The discussion around that has already started and you can follow along here: https://bugzilla.mozilla.org/show_bug.cgi?id=928901

We urgently need feedback on this, because it will be a large scale change, that will affect every contributor using the support forums today. In particular we are interested in answering the following questions:

  • What in particular are you looking for when using the support forums? Open questions, questions with lot’s of replies? Questions where you have replied?
  • Are their certain combinations of filters that make sense to you and that should be the default?

Please leave your replies in the forum. We will use this thread to develop this mock-up further.

Thanks!
Kadir

Gravatar for Avatar

For a long time we have had small avatars on SUMO, but with the shiny new profile pages they look out of place. So we are going to support bigger avatars soon. But there is a twist: We won’t just increase the size of the avatars, we are switching to Gravatar instead. Gravatar is used by large number of online services including mozillians.org. This means that you don’t have to manage your avatar on SUMO separately unless you really want to. You can just upload an image once on Gravatar and have it show up on all kinds of webservices you are using.

Now, what does this change mean for you?

  1. If you are a new user and have a Gravatar account already, we’ll automatically use that when you create a new account on SUMO
  2. If you are a new user and don’t have a Gravatar account yet, you’ll get the default avatar as always and you can change your Avatar by going to the Gravatar page (linked from your profile on SUMO)
  3. If you are an existing user with a Gravatar account, we’ll replace the avatar you have here with the one in your Gravatar account.
  4. If you are an existing user without a Gravatar account nothing is changing for you. But if you want to change your Avatar later on, you’ll be linked to Gravatar.

If you don’t want your standard Gravatar image to be shown on SUMO, you can change your email address on SUMO. You don’t have to actually use a different email account. Just append “+SUMO” to it. So if my mail address is atopal@example.com it would become atopal+SUMO@example.com. This way you still get your email to atopal@example.com, but Gravatar won’t show the image here that you have set for atopal@example.com

This is now live on our staging server: http://support.allizom.org Please give it a try and let me know what you think. You can also comment directly in the bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=918854

SUMO now helping an additional 7.3 million visitors

About 3 weeks ago we made the switch to a new information architecture and new design. The goal was to improve the browsability of the site and help people find the articles that they were looking for. 3 Weeks later we can now take a look at our key performance indicators to determine whether the whole project was worth the effort

Methodology

Since this project was primarily concerned with the Knowledge Base, we can focus on the helpfulness rating in this channel. Also, we know from our exit surveys that about 80% of our visitors use the KB.  The KB helpfulness rating is based on the survey that accompanies each article in each language. We ask the question “Was this article helpful?”, which can be answered with yes or no. Of course this metric is not perfect, articles that describe features have higher ratings than articles explaining how to fix a problem, English articles are generally higher rated than localized articles, despite having the same content, and the rating is also influenced by the path people took to get to the page. However, in this case we are not interested in the absolute ratings, we are particularly interested in the change since we moved to the new iA and design.

So, what happened?

We knew from previous tests that making the site browsable would be beneficial for that segment of our users who would rather browse than search for their article. People rate an article down, when it’s not the one that they were looking for. We know so much from our article surveys, and assuming we did our homework we should help more people find the right article. That being the case we expected the helpfulness of articles to rise, but it was hard to tell by how much it would rise. Considering that we have over 500,000 visitors per day and 80% use the KB, even a change by one percentage point would help an additional 1.46 million visitors per year. Without further ado, here are the results:

The results are phenomenal, we raised the helpfulness by 10 percent on average. That’s an increase by 5 percentage points and means an additional 7.3 million visitors per year stating that they found a SUMO article helpful. This is across all languages and across all incoming channels. It means that in 7.3 million cases where people might have decided to drop Firefox or be miserable because they couldn’t get Firefox to do what they wanted, they will now leave SUMO satisfied with their browser.

It’s hard to overstate the significance of this, and we are extremely happy with the results. The improvements to the site were the result of month of hard work by many people on the SUMO team, from SUMOdev, our creative team, and UX designers. We knew we were able to offer our users a better service, and the work has finally paid off. Continually thinking about how to serve our users better is what’s driving this team, and we will take these results as motivation to work even harder on improving our services.

Today, I’m very proud of what this team made possible, and I’d like to extend my thanks to each and everyone involved in the process: You made these results possible!

The all new SUMO

Today we are going to make one of the biggest changes yet to SUMO, the Mozilla Support site, and this blog post is about what changes we are making. The changes will effect you the most as a user, but there are a number of changes for contributors as well.

First, a little history, what’s the SUMO team been up to this year?

For the last 9 month the SUMO team has been working on a new way to let users access our site content. Until recently the only way to reach most of our articles was by search, or by following links in articles. This is how wikis traditionally work. Of course that way of accessing content only works for a part of our visitors, some people want to search and some people want to browse to the solution, drilling down with ever finer topics to reduce the number of article that are related to the issue.

To come up with a new information architecture that would let people drill down like that, we first researched the mental model of our site users, how they think about issues and in what categories they would look for them. Based on that we created a small number of base categories and assigned our articles to those categories.

The next step was figuring out how to make this information architecture visible. We started to lay out a number of alternatives on paper and tested with real people in a lab. This paper prototyping gave us a way to test a number of ways to lay out the information very quickly. After a number of iterations we settled on the final designs and workflows.

Now we had everything to start adapting our site, but since this would be a big redesign, and we’d soon switch to the new unified One Mozilla design anyway, the decision was made to use this opportunity to rebuild the site based on the new theme, and that’s why the changes today not only affect the KB, but every part of our site.

So, what is changing? What does it look like?

The main change is, that we now support several products from one start page and all articles can be accessed by browsing. Let’s start with the start page:

We have the main topics on top, they allow you to start browsing by selecting your issue first, and then the product you have issue with.

One step below you can see the hot topics. Those are actually articles, things that came up recently and affect a large number of people. By providing them upfront we save a large number of people the hassle of searching or browsing for their solution.

Below that we have the product picker, this is a way to navigate our content by choosing the product first and then narrowing down the topics.

No matter what way you select, topic first or product first, you’ll end up narrowing down the number of articles to a scanable few and proceed to read one of the articles.

The important thing for localizers to note is: all of this is automated, there is no need anymore to create navigation pages and all the confusion that brought with it.

So, how did the article view change? On the surface not much has changed, but because we keep track of topics, we can now offer you a way to move to related topics, which is particularly interesting for people landing on articles from external searches:

Much, much more has changed, but this is the gist for the KB part of the site.

So, what has changed for forum contributors?

While the new iA did not touch the support forum per se, we took the redesign as an opportunity to improve a number of factors in the listing of questions for our contributors.

The new design is more friendly and clean, but at the same time gives more information about the thread content at the same time. This is especially helpful when contributors scan the thread listing page deciding which thread to pick next.

We already started rolling the design out to our contributor base over the last week and will start rolling it out to 1% of the general audience today. If everything goes to plan we’ll make it available to the general audience on Monday. If you want to try it out now, just register an account, and if you have any feedback, please use the comment section below.

The new information architecture will open up our content to a whole new group of users and make it much more accessible, while our new design is more coherent, taking into account all of the features we added since our first release while also being consistent with the Mozilla sites in general. All of this makes us very excited and hopeful that we’ll get that much closer to our number one goal: Happy users!

SUMO development in 2012

We are more than halfway through 2012 and this seems like a good time to stop and take a look back at the year so far. In particular I’d like to provide insights into how we used the available development time and what we were able to achieve for the community this year.

Search and Browsing on SUMO

Late in 2011 we had found out that our site needed some serious improvement in it’s search and information architecture. We tackled our search issues right away, and with the help of our UX designers and Susan, our information architecture expert, we spent the first 3 month of this year to come up with a site structure that would not only speak to our current users, but would also be flexible enough for future products. And while we implemented some of the resulting suggestions right away, we then took another quarter to test the new information architecture rigorously in the real world, before we wrote the first line of code. I’ll have more to say about that in a future blog post, but I wanted to take the time today to look at our development efforts for this year.

In very broad strokes, we spend the biggest part of our development time on moving to a new search engine and tuning that engine to return much better results than before. We also spent a large chunk of our time on measuring and displaying our key performance indicators (KPI), the metrics we take to measure our success as SUMO. More recently we have focused the majority of our effort on implementing the proposed new information architecture and a new “One Mozilla” design that will bring us visually closer to the existing Mozilla ecosystem.

Where did all the time go?

For the first time this year, we also tracked what user roles we served with the development time we had. The following table charts the number of points we spent, each point stands roughly for one day of development. As you can see the total number of points varies throughout the year as the constellation of the development team changes. We separated the user roles into “contributor”, “user”, “sumo-team”, and “dev”, which is used for infrastructure work. That is not to say that the classification was always clear cut. For example a lot of the development time  spend on contributors was also beneficial for the sumo team and the other way around. You can see all individual sprints on Scrumbugs, if you want to have a closer look.

 

Legend:

  • Contributor: Code changes that affected contributor of the site the most
  • User: Code changes that affected visitors of the site the most
  • SUMO Team: Code changes that affected SUMO staff the most
  • Development: Infrastructure work that didn’t benefit any one role in particular.

Community Focus

As is clear from the data we put our focus on the user experience this year. However we also invested heavily into the experience for the most important aspect of SUMO: contributors. I don’t want to list the dozens of individual bugs that were fixed and smaller feature that were added as you can quite easily see each of our sprints on Srumbugs. but I wanted to take the time to mention some of them as a reminder of what we worked on for individual contributors this year.

Forum contributors

  • Forum contributors can now add links to KB articles easily by searching for them in the “add link” overlay, which removes the need to open a new window, doing the search and linking manually.
  • We are now hiding questions that are older than 90 days and don’t have any answers from most parts of the site, as well as hiding all threads that are older than 180 days, so that we can focus on the threads in the forum that need our attention the most
  • We added a feedback indicator to the forum, that now tells us how far we are away from our goal to answer all incoming questions within 72 hours.
  • Forum contributors can now use the magic hat, that will offer them various small snippets that they can use to ask for more information, or answer recurring questions with 3 simple clicks.
  • Also, we are now only bumping questions to the top when there is a reply and ignoring other activity, to make sure we can focus on the most important questions.

KB contributors:

  • KB contributors can now send messages to all recent contributors of an article, even if they approve their own edit.
  • We added a remaining characters counter to the search summary. Google only shows the first 160 characters of a site as the preview, and after deciding to make that the search results summary we also added a counter to make sure we stay within the limits.

Localizers

  • The “approved” mail notification now mentions the approver and the changes in the body, so that people can save a round trip to SUMO.
  • In the same way, the “ready for localization” email now features a diff, so contributors can tell from their inbox how much effort a new update would take.
  • We are now showing messages above English articles, if the visitor is coming from a localized article, and we ask people to help us with the translation of that article into the language of the visitor.
  • Localizers can now see all navigation articles on their L10n dashboard, which saves us searching for it on various documentation pages.

Army of Awesome:

  • The Army of Awesome snippets can now be easily edited on SUMO, since they are KB articles now, instead of being in code.
  • The Army of Awesome has now statistics that more accurately display the effort of our community and our goals.
  • SUMO members can now stayed signed in on the Army of Awesome and answer tweets without having to log-in to Twitter each time.

All:

  • We have added a simple quoting feature for private messages, that now makes it possible to cite text in a reply and giving context to a reply.
  • We have adjusted several time frames on the KB dashboards to be able to react to changes more quickly
  • Most parts of SUMO now feature time stamps that consider the time zone of the user instead of being fixed to Pacific Time
  • Support forum and discussion forum posts of users are now displayed on the profile pages of all users for quick reference.

What’s next?

All in all I’m very proud of what we all have done so far and I can’t wait to see in production the many changes that are planned for this year, the most important of which is currently under development: The new information architecture and redesign. The new iA has been on our minds for most of this year already offers tremendous wins for users and contributors alike, and I’ll soon blog about the project and its expected effect on our site. For now, a big thank you goes out to all sumo developers, contributors and members. You are what makes SUMO so awesome!

The new magic SUMO tool for frequent questions, and an interview with its developer, Tobias Markus

For a few weeks now we have been replying to almost every single question that is asked in the Mozilla support forums. That is up from about 50% last year and it shows the dedication of our community. Also over the last few month we have made a number of changes to SUMO to reduce the flow of simple questions that have answers in the KB already. That has been quite succesful, not only are we getting really hard questions now, but they are solved at a higher rate than before too.

The challenge now is that we have to ask for more information before we can solve an issue. Repeating those questions is quite tiring, so we decided to build a tool to help out our community and gather all the important questions to ask in one place.

We had actually planned to work on it later this year, but one of our great community members, Tobbi, saw an opportunity and offered to try his hand on it.

The result went online a few days ago, and is amazing. Sign into SUMO, and check it out for yourself:

  1. Chose a question
  2. Click on the response tool (the magic hat symbol)
  3. Select an answer or a request for specific information
  4. Customize as necessary and send!

Over time this tool will hopefully gather all the shared wisdom of our community and help us solve issues in as few steps as possible.

Interview with the developer, Tobias Markus.

This is not the first time a community member has been helpful in the development of Kitsune, the software that powers SUMO, but it’s the first major feature. We’d love to see much more of this, and I asked Tobbi for an interview to ask him how he got involved for anyone who wants to follow in his footsteps.

Tobbi, you have been a SUMO community member for quite a long time. Where did you start and how was your SUMO journey so far?

It was late 2008 when I started contributing to SUMO. My portal to the SUMO world was the Firefox LiveChat, which I joined as I really liked the personal touch that the chat had. Later on, I found out that there was a German localization group for SUMO articles, so I started translating articles into German and helped reaching the goal of then 100% localization coverage. I even gave forum support, although I preferred LiveChat because it was more personal than the forums.

How did you get the idea to help with the development of SUMO?

The idea for development started when I was working on a Firefox add-on together with Propeng. We implemented various features for the old forums to make them more contributor-friendly and add some tools that aimed at making life for contributors easier. However, due to the amount of unfinished code and the switch to Kitsune, the project was stalled. That’s when we decided to split the big project into smaller chunks to make them compatible again with the new forums. One of these smaller projects was the Knowledge Base article autocomplete that was landed a few months ago. I think it was Rosana who suggested integrating the Knowledge Base autocomplete into the Firefox support website directly. That’s when I started contributing to the development of SUMO.

Did you get any help with your project?

The SUMO team and other contributors really helped me a lot. At first I was posting an early draft to the contributors forum to gather suggestions from other contributors and the team. The feedback I got was huge. I spent the next couple of weeks reacting on it and making a lot of improvements to the code to enable things like instant preview, edit mode, and even flags that can limit certain responses to certain groups of contributors. The SUMOdev team also answered some implementation questions.

Once this was done, the next thing was to make the experience perfect for contributors. I brainstormed a lot with Bram [the SUMO UX designer] about best practices in order to get a good user experience design and spent some more weeks making the necessary changes.

The fourth step was a final code review by Ricky Rosario. That went smoothly as well, the necessary changes I had to do were minimal and most of them were about simple code style fixes. Once these were fixed, the code was ready to land.

The final step was to create the canned responses. I asked the community again to get back to me with some frequently used responses and the amount of responses I got was overwhelming. I chose around 10 of the most frequently used ones (based on my own judgement) and rewrote them a little. Kadir then helped me put each response in its own article and create a main article for the category structure that has links to all the individual responses.

What is your advise for people who want to get involved with SUMO development?

Drop by in #sumodev on irc.mozilla.org and say hello. The SUMOdev people answered any questions I had so that canned responses could become a success. Also, there is good documentation available online about setting up a local copy of SUMO. So, if you have a great feature in mind for the support website and want to start developing, give it a go!

Tobi, thank you for this interview, and in the name of the SUMO community: thanks for making everyone’s live so much easier!

The 8th SUMO sprint

Last Tuesday we finished the 8th SUMO sprint of this year. I’s been a short sprint, because for half of it Mozilla web developers met for a work week in California. Nevertheless we were able to land some great improvements to SUMO.

  1. One of our top priorities right now is improving our search results. To that end we started an initiative to rate KB and forum results as equals, based solely on the content instead of showing KB articles on top and forum posts at the bottom. We hope that this step will result in better search results by higher click through rates. This is a project that will take more than one sprint to be implemented. We completed the first of 3 phases in this sprint and are planning to implement the rest over the next sprints. You can read Will’s bug comment about it, if you want to know more about the gory details of the unification work.
  2. We were also able to implement a feature in the forums that gives our community an indicator for how we are doing and shows everyones impact on the forum: We call it the forum feedback indicator. It shows you how many questions were asked in the last 3 days and how many have a reply. It also links to the questions that haven’t been answered yet. The progress bar is orange, for any values below 100% and turns green when all questions are taken care of.

As with every sprint we also fixed a number of annoying bugs, and you can always follow along on the excellent scrumbugs. Here is the list for the 8th sprint.

However I’d like to point out one specific issue, that was bugging us in the forums for quite a while, creeping back when we thought we had squashed it: In some cases, a question displayed “No replies”, even though it already had replies. That bug is now hopefully fixed for good.

SUMO sprint 2012.4

This is a quick update on what we are currently working on in the 4th SUMO sprint of this year, the results of this sprint will go live between February 28th and March 6th.

Our dev goals for this quarter were to get the SUMO KPI dashboard up and running, and to switch to a new search engine that would allow us to implement all the improvements suggested by the ongoing taxonomy/ux research and the usability research before that.

We have recently turned our new search engine (Elastic Search) on for 50% of our site’s users, and the early results are very promising. The Click Through Rate, our main success metric at this point, of the new engine is already better than that of the old one. Currently we are gathering more data to get reliable results, but if the final results agree with our preliminary findings, we’ll switch to Elastic Search 100% in early March and start improving our results. One big issue we’ll tackle soon is the performance of Elastic Search, currently it is much slower than our old search engine. However Will already has ideas that will hopefully give us significant improvements in this area, starting with sprint 5.

Our KPI dashboard is nearing completion, thanks to Ricky. We already have many of the metrics we set out to present and few are left. This sprint will give us the Army of Awesome numbers, the number of unique visitors we have at SUMO and our localization coverage.

One change that seems small, but will hopefully have a big effect, is the change of our font, colors and sizes. We had numerous complaints that our text was hard to read and links were easily overlooked. Bram, our UX designer, and font expert extraordinaire, came up with a new style that uses stronger colors for links, changes the gray on white of our body text to a darker black, and moves us from serif to sans-serif. The latter change is significant, there is a large body of research on what is better for readability serif, or sans-serif, and amid a lot of myths there are arguments for both sides. However it seems clear that there is only one factor that reliably affects readability: familiarity. Of the top 100 websites today only 4 use a serif font for body text. Since users today are so much more familiar with sans-serif our hope is that this change will contribute to the overall readability of SUMO.

Another thing we have been working on is several customizations of our contributor forums, so they could be used by the Firefox Aurora and Beta communities. Expect more activity in those forums very soon.

As always, there is a good number of new features and fixes for smaller bugs:

ID Summary
730065 Allow sort by original post date
718813 let people add screenshots when asking a question
726037 Combine some of the KPI dashboard graphs
645546 How to contribute articles overview in the dashboard
724833 Change AoA signposts
625841 Reword email notifications for Questions
720226 We need reviewing rights for en-US and other locales
724483 remove en-US part from link in ‘ready for localization’ emails
725287 Use One Mozilla breadcrumb style (revert bug 716018)
726112 Allow entering a message for recent contributors, even if you approve your own revision.
722697 Show contributor sidebar in the questions app
726856
706948 In some cases, a question displays “No replies” with a reply below
722509 notification about private message has localized URL
728307 Please add {for} support for fx12, m12 and add Firefox 12 to the dropdown UI, remove Firefox 9 from the UI