SUMO community discussions

[Migration] - Design ideas: sitewide and individual pages

  1. Hi SUMO,

    The new platform migration gives us the opportunity to make some design changes to the site. While we aren't looking at big, structural changes for this phase, we are looking at decisions that make a difference in usability, readability and the overall look and feel of the site.

    I'd like to gather your ideas here so we can discuss them with the new platform developers.

    Here's an example of a real design idea that don't require any big structural changes:

    • Click to enlarge images in articles
      • User stories: As an end-user, I would like to enlarge images in articles so I can see more details. As a KB contributor, I would like to include smaller articles so I can keep the layout clean without sacrificing usability.

    Other examples would be changes to font style, size or color and wording changes.

    Please add any ideas you have to our feedback document. If you're unsure of whether or not an idea is within our scope for this year, add it anyway and we'll see if we can fit it in. Please include a user story or justification so we can come up with alternatives that fulfill the same purpose if an idea isn't technically feasible.

    If you have any questions, let us know. I look forward to your ideas.

    Joni

    Hi SUMO, The new platform migration gives us the opportunity to make some design changes to the site. While we aren't looking at big, structural changes for this phase, we are looking at decisions that make a difference in usability, readability and the overall look and feel of the site. I'd like to gather your ideas [https://docs.google.com/document/d/1ZFgR6QBxyFsQSC-I-HLPh4p0I3YIh9i5Z_f7DfaeSKQ/edit?usp=sharing here] so we can discuss them with the new platform developers. Here's an example of a real design idea that don't require any big structural changes: * Click to enlarge images in articles **User stories: As an end-user, I would like to enlarge images in articles so I can see more details. As a KB contributor, I would like to include smaller articles so I can keep the layout clean without sacrificing usability. Other examples would be changes to font style, size or color and wording changes. Please add any ideas you have to [https://docs.google.com/document/d/1ZFgR6QBxyFsQSC-I-HLPh4p0I3YIh9i5Z_f7DfaeSKQ/edit?usp=sharing our feedback document]. If you're unsure of whether or not an idea is within our scope for this year, add it anyway and we'll see if we can fit it in. Please include a user story or justification so we can come up with alternatives that fulfill the same purpose if an idea isn't technically feasible. If you have any questions, let us know. I look forward to your ideas. Joni
  2. Thanks Joni, I am always eager for news about the Lithium software, but have we jumped a large step? We seem to be talking minor & cosmetic details about articles with no overview of what any new System will be like.

    When and where will we be discussing features and use of the new KB is that here and your linked document or elsewhere ?

    I am thinking of topics like writing editing and reviewing articles, and of course the showfor which is apparently in a very early stage and not working yet.
    (link)The showfor looks broken to me. That was the only thing we were asked to test.
    Explanation { IRC 19th }
    18:28 John99 madalina_ Is this because it is never going to be implemented as detecting the FX & OS or is it just that it has not yet been implemented. 18:29 madalina_ it has not yet been implemented 18:38 madalina_ John99^^ 18:39 madalina_ so that piece will come later, this is very very early stages

    Will we even still have collectivity owned and edited community KB articles and a large range of canned responses ?

    What happens about L10n presumably that will be a separate subject again, and what about the images gallery will that still be open to all.

    Thanks Joni, I am always eager for news about the Lithium software, but '''have we jumped a large step?''' We seem to be talking minor & cosmetic details about articles with no overview of what any new System will be like. When and where will we be discussing features and use of the new KB is that here and your linked document or elsewhere ? I am thinking of topics like writing editing and reviewing articles, and of course the showfor which is apparently in a very early stage and not working yet. <blockquote>([https://support.mozilla.org/en-US/forums/contributors/712179?last=70272#post-70263 link])The showfor looks broken to me. That was the only thing we were asked to test. </blockquote> Explanation { [http://logs.glob.uno/?c=mozilla%23sumo&s=19+Sep+2016 IRC 19th] } <blockquote>18:28 John99 madalina_ Is this because it is never going to be implemented as detecting the FX & OS or is it just that it has not yet been implemented. 18:29 madalina_ it has not yet been implemented 18:38 madalina_ John99^^ 18:39 madalina_ so that piece will come later, this is very very early stages</blockquote> Will we even still have collectivity owned and edited community KB articles and a large range of canned responses ? What happens about L10n presumably that will be a separate subject again, and what about the images gallery will that still be open to all.
  3. Will individual KB articles continue to have their own discussion forums where separate threads can be posted, like we have now? Or, will that change? I'm asking because of what I see in the Lenovo KB, since John99 mentioned it in another thread. Here's an example Lenovo KB article: https://forums.lenovo.com/t5/ThinkPad-S-Series-ThinkPad-Yoga/Lenovo-Systems-That-Support-Pens/ta-p/3295823

    That KB article has "comments" right underneath the article itself but I don;t see any "Discussion" listed under Article Options, although I do see "Article History". I don't think that design works very well for KB editors who want to discuss the article background or changes to the KB article.

    John99 said

    I am thinking of topics like writing editing and reviewing articles, <snip> Will we even still have collectivity owned and edited community KB articles and a large range of canned responses ?

    I asked about that in the [Migration]Roles thread, https://support.mozilla.org/forums/contributors/712184#post-70284

    Will individual KB articles continue to have their own discussion forums where separate threads can be posted, like we have now? Or, will that change? I'm asking because of what I see in the Lenovo KB, since John99 mentioned it in [https://support.mozilla.org/en-US/forums/contributors/712179 another thread]. Here's an example Lenovo KB article: https://forums.lenovo.com/t5/ThinkPad-S-Series-ThinkPad-Yoga/Lenovo-Systems-That-Support-Pens/ta-p/3295823 That KB article has "comments" right underneath the article itself but I don;t see any "Discussion" listed under Article Options, although I do see "Article History". I don't think that design works very well for KB editors who want to discuss the article background or changes to the KB article. ''John99 [[#post-70285|said]]'' <blockquote> I am thinking of topics like writing editing and reviewing articles, <snip> Will we even still have collectivity owned and edited community KB articles and a large range of canned responses ? </blockquote> I asked about that in the [Migration]Roles thread, https://support.mozilla.org/forums/contributors/712184#post-70284
  4. Assuming we're not losing the current functionality when we switch...

    I'd like to see greater support for screencasts. Initiatives to include screencasts, and make it easy to contribute seems to have died off. Tools for adding videos, and providing sub-titles for both KB and the forum would be great. If they're short enough, turn them into GIFs?

    Assuming we're not losing the current functionality when we switch... I'd like to see greater support for screencasts. Initiatives to include screencasts, and make it easy to contribute seems to have died off. Tools for adding videos, and providing sub-titles for both KB and the forum would be great. If they're short enough, turn them into GIFs?
  5. maybe we could tweak the overall color-scheme a little bit to add more contrast (there have been user complaints about it every now and then)...

    maybe we could tweak the overall color-scheme a little bit to add more contrast (there have been user complaints about it every now and then)...
  6. Replace emoticons with smiley icons (or emojis). I know it seems small, but I've always thought that would make a significant difference in the friendliness of both the support forums and contributor forums.

    Replace emoticons with smiley icons (or emojis). I know it seems small, but I've always thought that would make a significant difference in the friendliness of both the support forums and contributor forums.
  7. philipp said

    maybe we could tweak the overall color-scheme a little bit to add more contrast (there have been user complaints about it every now and then)...

    Thanks, Philipp. I'll look into color schemes we can consider.

    Can you give an example of a specific user or contributor complaint (example "It hurts my eyes." "it's outdated", "it reminds me of..." etc.)

    Knowing specific complaints will help us avoid a new color scheme that causes the same problem.

    Adding this to the doc.

    ''philipp [[#post-70328|said]]'' <blockquote> maybe we could tweak the overall color-scheme a little bit to add more contrast (there have been user complaints about it every now and then)... </blockquote> Thanks, Philipp. I'll look into color schemes we can consider. Can you give an example of a specific user or contributor complaint (example "It hurts my eyes." "it's outdated", "it reminds me of..." etc.) Knowing specific complaints will help us avoid a new color scheme that causes the same problem. Adding this to the doc.
  8. Chris Ilias said

    Replace emoticons with smiley icons (or emojis). I know it seems small, but I've always thought that would make a significant difference in the friendliness of both the support forums and contributor forums.

    Great idea! I'll add this to the doc for discussion.

    ''Chris Ilias [[#post-70334|said]]'' <blockquote> Replace emoticons with smiley icons (or emojis). I know it seems small, but I've always thought that would make a significant difference in the friendliness of both the support forums and contributor forums. </blockquote> Great idea! I'll add this to the doc for discussion.
  9. Thanks, everyone. I'm going through your suggestions and adding it to the Google Doc. Feel free to add to the doc directly and I'll organize it myself.

    Before we continue, I'd like to address some of your concerns (Madalina also discussed this in our platform meetings). For this first wave, we are trying to keep the site the same, at least from the front end, so we don't miss our deadlines. Some things might not translate directly, and we're still trying to figure out what these things are. As soon as we know, you'll know too.

    The reason we're doing minor design changes is so that we can stick to our migration deadline, but we want to address the low-hanging fruit that can improve the user experience. There will be no other functional changes at this time, and definitely not without any discussion with the community.

    We'll get to the really exciting stuff after the first wave. :)

    Thanks, everyone. I'm going through your suggestions and adding it to the [https://docs.google.com/document/d/1ZFgR6QBxyFsQSC-I-HLPh4p0I3YIh9i5Z_f7DfaeSKQ/edit Google Doc]. Feel free to add to the doc directly and I'll organize it myself. Before we continue, I'd like to address some of your concerns (Madalina also discussed this in our platform meetings). For this first wave, we are trying to keep the site the same, at least from the front end, so we don't miss our deadlines. Some things might not translate directly, and we're still trying to figure out what these things are. As soon as we know, you'll know too. The reason we're doing minor design changes is so that we can stick to our migration deadline, but we want to address the low-hanging fruit that can improve the user experience. There will be no other functional changes at this time, and definitely not without any discussion with the community. We'll get to the really exciting stuff after the first wave. :)
  10. Hi

    Are we going to use Firefox branding, Mozilla branding (which may be about to change), or the SUMO logo?

    Hi Are we going to use Firefox branding, Mozilla branding (which may be about to change), or the SUMO logo?
  11. (I've edited the title to include ideas for specific types of pages):

    Hello,

    Thanks for your feedback on sitewide design improvements last week. We are now getting into the nitty gritty and gathering feedback for specific types of pages. Here’s a list of the types of pages that can be found on SUMO (are we missing anything? Add them to the doc.)

    Let’s try this approach so we can stay focused: in place of suggestions, let’s identify problems with the pages.

    Examples of this can be “I can’t tell that the editing tools menu can be collapsed or expanded” or “users have complained that the page is hard to read.” This will help us think of ideas that make an impact.

    Please make your changes to this document by Monday morning (Pacific time) so we can discuss them with the Lithium folks.

    Thanks for all your feedback! Joni

    (I've edited the title to include ideas for specific types of pages): Hello, Thanks for your feedback on sitewide design improvements last week. We are now getting into the nitty gritty and gathering feedback for specific types of pages. Here’s a [https://docs.google.com/spreadsheets/d/1XkaWROr7M-nmYuWPvsOxmeZwgcMJIEG9zd2uilHSjDM/edit#gid=0 list of the types of pages] that can be found on SUMO (are we missing anything? Add them to the doc.) Let’s try this approach so we can stay focused: in place of suggestions, let’s identify problems with the pages. Examples of this can be “I can’t tell that the editing tools menu can be collapsed or expanded” or “users have complained that the page is hard to read.” This will help us think of ideas that make an impact. Please make your changes to [https://docs.google.com/spreadsheets/d/1XkaWROr7M-nmYuWPvsOxmeZwgcMJIEG9zd2uilHSjDM/edit#gid=0 this document] by Monday morning (Pacific time) so we can discuss them with the Lithium folks. Thanks for all your feedback! Joni
  12. Seburo said

    Hi Are we going to use Firefox branding, Mozilla branding (which may be about to change), or the SUMO logo?
    HI Seburo,
    

    As of now, we're planning to use the same branding we're using on kitsune, although the color scheme might change if we determine that it will help readability/usability. This will be up for discussion next week, so please join in if you'd like to.

    ''Seburo [[#post-70451|said]]'' <blockquote> Hi Are we going to use Firefox branding, Mozilla branding (which may be about to change), or the SUMO logo? </blockquote> HI Seburo, As of now, we're planning to use the same branding we're using on kitsune, although the color scheme might change if we determine that it will help readability/usability. This will be up for discussion next week, so please join in if you'd like to.
  13. Hi Joni

    Okay, no problem with the branding, just interested.

    I am unable to join the calls next week due to work, but I guess the only user interface issue I have noticed from the staging site is that it is tricky trying to figure out how to ask (or answer) a question on the forum element.

    I tried the other day and found it to be almost hidden.It makes sense to focus people towards the KB first of all, but we also need to make sure people can easily ask questions and that contributors can easily reply.

    Hi Joni Okay, no problem with the branding, just interested. I am unable to join the calls next week due to work, but I guess the only user interface issue I have noticed from the staging site is that it is tricky trying to figure out how to ask (or answer) a question on the forum element. I tried the other day and found it to be almost hidden.It makes sense to focus people towards the KB first of all, but we also need to make sure people can easily ask questions and that contributors can easily reply.
  14. Ok, I just hope we will see the end of having two page headers, scroll to one point you get the sumo one, scroll further and you get the Mozilla one.

    Oh and my screen is 23 inches wide. Perhaps some of that can be used for something other than dead space, like as if I am reading SUMO on a palm pilot 20 years ago.

    When reading this forum, more than 50% of my screen is a dull pinkish colour with Zero content, but wow I do a lot of scrolling to get to the bottom of threads. It is little wonder the wheel in my mice just gives up after a few months.

    Ok, I just hope we will see the end of having two page headers, scroll to one point you get the sumo one, scroll further and you get the Mozilla one. Oh and my screen is 23 inches wide. Perhaps some of that can be used for something other than dead space, like as if I am reading SUMO on a palm pilot 20 years ago. When reading this forum, more than 50% of my screen is a dull pinkish colour with Zero content, but wow I do a lot of scrolling to get to the bottom of threads. It is little wonder the wheel in my mice just gives up after a few months.