MDN/Archives/Development/Redesign/Testing: Difference between revisions

From MozillaWiki
< MDN‎ | Archives
Jump to navigation Jump to search
No edit summary
 
(34 intermediate revisions by 6 users not shown)
Line 1: Line 1:
MDN is undergoing a major redesign with improved design, layout, page customization options and navigation. To ensure that the redesign is the best it can be, we have made the design available to anyone who would like to help with beta testing.
<div class="toclimit-2">__TOC__</div>


== How you can help ==
The MDN redesign launched on December 9, 2013. While the beta testing phase is over, we are welcoming feedback on the live redesign site.


Remember that even though you will see our new design, you will be working with the same documentation. Any changes you make will be seen by all users, whether they are seeing the new design or not.
MDN is undergoing a major redesign with improved visual style, layout, page customization options, navigation, and platform features. To ensure that the redesign is the best it can be, we have made it available to anyone who would like to help with beta testing. Remember that this is a beta, so while we are correcting issues quickly, you may discover some bumps along the way.


Once the redesign is enabled, we would love you to go around the site and have a look at everything, as well as editing some pages and making some other site contributions. Please let us what you think of the redesign, what is not working, and what could use improvement.
== How to become an MDN beta tester ==


=== Testing suggestions ===
* Login into [http://developer.mozilla.org MDN].
* [http://developer.mozilla.org/profile/edit Edit your profile].
* Check the beta user checkbox.


Looking for some ideas? Try testing out the following. Bug reports, change requests and other feedback is welcome.
== Change overview ==


* Read documentation and follow links. Pay attention to code samples, images and videos. Act just as you normally would if you were reading documentation.
The most obvious differences include the new visual style and the new layout. Updates have also been made to the homepage, to site navigation, and to major features like site search. Additionally, some topics like ''Firefox OS'' and ''Web Apps'' are now represented as '''Zones''', documentation sections with improved landing pages and a new secondary navigation sidebar.
* Try our improved search. Pay attention to both the experience of searching and the quality of the search results.
* Edit a page (remember that your edits will be seen by everyone, whether they are testing the beta or not)
* Edit a template, if your account has this privilege (again, remember that these edits will be seen by everyone)


=== Sharing feedback ===
== Testing ==


Let us know what you think! Bug reports, change requests and general feedback are all welcome. There are many ways to get in touch with us.
We would love for you to go around the site and take a look at everything. Try reading documentation, editing pages and making other site contributions. Remember that even though you will see our new design, you will be working with the same documentation everyone else sees. Any changes you make will be seen by all users, whether they are testing the beta or not. So as part of your testing, please don't randomly change or delete content!


* Before anything else, please [http://mzl.la/mdn-redesign-feedback file a bug]. We would love to hear from you on IRC and through our mailing lists, but if a bug is not already filed we will probably ask you to do so. Remember to use this form for all redesign feedback, as it will group feedback appropriately and ensure that the team sees it.
=== Suggestions ===
* Join the conversation in [[/IRC|IRC]]. You can meet us in #mdn for general discussion, #devmo for discussion about documentation and #mdndev for discussion about development progress.
* Join our mailing lists. Staff documentation writers can be reached on [https://lists.mozilla.org/listinfo/dev-mdc dev-mdc@mozilla.org] and platform developers can be reached on [https://lists.mozilla.org/listinfo/dev-mdn dev-mdn@mozilla.org].


What kind of feedback we are looking for? We are interested in:
Looking for some ideas of things to do? Try testing out the following:
* ''Your overall feeling'': keep in mind it is an early beta and is a work in progress. It isn't a beta, we won't change anything until the launch.
* ''Navigational problems'': the first goal is to be able to reach all the information. We know that it was difficult with the old design, we hope it is better, but we may forgotten something.
* ''Visual problems and glitches'':
** on the home page: Does the positioning of the element suit your needs? Some elements are emphasized by the color scheme or the position on the page: are these the right ones?
** on the zone landing pages
** in articles: we have in-content element that may not fit well, we are interested in a list. Especially if you use a lesser known part of the MDN that is not the Open Web document where we probably have missed it. We have added quick links, but these are experimental: feel free to tell us if they help you or not.
** at different sizes. Keep in mind that even if we aim to support small screens, we are not done there yet. But anything 10" or greater shouldn't show major problem.
* ''Speed'': we don't have performed any specific optimization here, but there shouldn't be less good now than before. If you noticed strange things, be sure to tell us.
* ''Search'': we have a new search engine, that does not use Google anymore, so we are specifically interested in the quality of the results. We have added the ability to set filters. Try using them, tell us if they work, if the quality of results is good and so on. Also is it easy to get to the search? Is there specific problems you encounter when typing your search query?


== Final word ==
* Documentation: Read our documentation just as you normally would. Pay attention to code samples, images, and videos. Some documentation, especially lesser-known documentation, has not yet been updated to fit with this new design. Let us know if you come across anything that doesn't look right.
* Homepage: Is the content of the homepage valuable to you? How about the positioning, size and style of this content?
* Navigation: Try getting around using only major site navigation. Can you find the information you need?
* Search: Try out the improved search system. Consider both the experience of searching and the quality of search results.
* Performance: How is performance? Is it better or worse than it was with the old design?
* Editing: How is the experience of editing? (Remember, your edits will be seen by everyone, whether they are testing the beta or not.)
* Template editing: Assuming you have account privileges, how is the experience of editing templates? (Again, remember that your edits affect all users.)
* Responsive Design: The new design supports many different screen resolutions. How is the experience of using MDN on a tablet, phone, or other device?


Really don't hesitate to give us information. The more feedback of good quality we get the more we will be able to consider in the next cycle beginning now.
== Sharing feedback / Reporting Bugs ==


Try to be precise and specific, it helps us. If you are using bugzilla, one problem per bug please, if you are using dev-mdc, you can of course put several points in your e-mail. But try to use different paragraphs, maybe numbered, so that it can be more easily referenced and evaluated.
Let us know what you think! Bug reports, change requests and general feedback are all welcome. The more feedback you share, the better the design will be.


We are very excited with this redesign and we want to improve it a lot in the next few months: your feedback is a very important element in achieving this.
'''Before anything else, please [http://mzl.la/mdn-redesign-feedback file one bug for each piece of feedback you want to share]. We would love to hear from you on IRC and through our mailing lists, but if you have not already filed a bug we will politely ask you to do so. Remember to always use this form, as it will group feedback appropriately and ensure that the team sees it.'''


'''The whole MDN team thank you in advance! And let's test!'''


==Notes and information==
== Follow up on Bugs / Feedback ==


New features — look out for them:
A couple times each week, we'll send out the list of bugs that are new and need to be categorized (blocks launch or does not) to the [https://lists.mozilla.org/listinfo/mdn mdn@lists.mozilla.org] mailing list (which is used to prioritize work on MDN and is open for anyone to participate). Bugs will be discussed there and the team can, collectively,  decide what needs to be fixed before the redesign launches to the general public. We also will have a weekly, open meeting to make calls on anything that is stalled. Meetings are held every Tuesday at 17:00 UTC (10am PST) on IRC in #devmo. 


* The main difference you'll notice is that the new theme. It is aimed at being more easily red and to look more professional. Among the differences you'll notice:
*[https://bugzilla.mozilla.org/showdependencytree.cgi?id=925144&hide_resolved=1 Launch blocking bugs]
** The consistent usage of the same font (Open Sans) instead of the mix of fonts we had before. Only code, and therefore interfaces, methods, and properties, are using a fixed-width font.
*[https://bugzilla.mozilla.org/showdependencytree.cgi?id=910513&hide_resolved=1 New/to be processed bugs]
** Numerous pages have now a quick links columns aimed at simplifying the navigation.
*Bugs that can be [https://bugzilla.mozilla.org/showdependencytree.cgi?id=925145&hide_resolved=1 addressed after launch]
* Certain pages have been converted into Zones, which are basically landing pages for specific focus topics like projects or tasks (Firefox, Firefox OS, Building Apps.) These have a distinct look and feel, and an integrated zone menu that persists between all the pages that under the zone in the document hierarchy. Examples:
 
** https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS
=== Following development in real time ===
** https://developer.mozilla.org/en-US/Apps
 
* We have a new internal search engine:
If you want to stay in the loop on a bug or a set of bugs, be sure to '''add yourself to the "cc" list'''. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are automatically pushed to the dev server every 5 minutes:
** It should be more precise than the previous one.
 
** It allows to filter the search on specific subject.
https://developer-dev.allizom.org/
 
The dev team pushes commits to stage and production servers when the code is ready. You can see which commits are on the stage & production servers here:
 
http://mzl.la/mdn_whats_deployed
 
Commits also often include numbers of bugs that you can visit to see relevant discussions.
 
===Weekly Meeting Notes===
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/03DecMeeting 03 December, 2013]
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/26NovMeeting 26 November, 2013]
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/19NovMeeting 19 November, 2013]
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/12NovMeeting 12 November, 2013]
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/05NovMeeting 05 November, 2013]
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/29OctMeeting 29 October, 2013]
*[https://wiki.mozilla.org/MDN/Development/Redesign/Testing/15OctMeeting 15 October, 2013]
 
== General Questions ==
You can join the conversation in [[IRC|IRC]].
* #mdn for general discussion
* #devmo for docs & content
* #mdndev for platform coding
 
You can also join our mailing lists.  
* [https://lists.mozilla.org/listinfo/dev-mdc dev-mdc@mozilla.org] for docs & content
* [https://lists.mozilla.org/listinfo/dev-mdn dev-mdn@mozilla.org] for platform coding
 
== Thanks! ==
 
We are very excited to be launching the beta of this new design, and are even more excited to be working with you to make it better. Thank you for all of your feedback.

Latest revision as of 20:48, 19 June 2017

The MDN redesign launched on December 9, 2013. While the beta testing phase is over, we are welcoming feedback on the live redesign site.

MDN is undergoing a major redesign with improved visual style, layout, page customization options, navigation, and platform features. To ensure that the redesign is the best it can be, we have made it available to anyone who would like to help with beta testing. Remember that this is a beta, so while we are correcting issues quickly, you may discover some bumps along the way.

How to become an MDN beta tester

Change overview

The most obvious differences include the new visual style and the new layout. Updates have also been made to the homepage, to site navigation, and to major features like site search. Additionally, some topics like Firefox OS and Web Apps are now represented as Zones, documentation sections with improved landing pages and a new secondary navigation sidebar.

Testing

We would love for you to go around the site and take a look at everything. Try reading documentation, editing pages and making other site contributions. Remember that even though you will see our new design, you will be working with the same documentation everyone else sees. Any changes you make will be seen by all users, whether they are testing the beta or not. So as part of your testing, please don't randomly change or delete content!

Suggestions

Looking for some ideas of things to do? Try testing out the following:

  • Documentation: Read our documentation just as you normally would. Pay attention to code samples, images, and videos. Some documentation, especially lesser-known documentation, has not yet been updated to fit with this new design. Let us know if you come across anything that doesn't look right.
  • Homepage: Is the content of the homepage valuable to you? How about the positioning, size and style of this content?
  • Navigation: Try getting around using only major site navigation. Can you find the information you need?
  • Search: Try out the improved search system. Consider both the experience of searching and the quality of search results.
  • Performance: How is performance? Is it better or worse than it was with the old design?
  • Editing: How is the experience of editing? (Remember, your edits will be seen by everyone, whether they are testing the beta or not.)
  • Template editing: Assuming you have account privileges, how is the experience of editing templates? (Again, remember that your edits affect all users.)
  • Responsive Design: The new design supports many different screen resolutions. How is the experience of using MDN on a tablet, phone, or other device?

Sharing feedback / Reporting Bugs

Let us know what you think! Bug reports, change requests and general feedback are all welcome. The more feedback you share, the better the design will be.

Before anything else, please file one bug for each piece of feedback you want to share. We would love to hear from you on IRC and through our mailing lists, but if you have not already filed a bug we will politely ask you to do so. Remember to always use this form, as it will group feedback appropriately and ensure that the team sees it.


Follow up on Bugs / Feedback

A couple times each week, we'll send out the list of bugs that are new and need to be categorized (blocks launch or does not) to the mdn@lists.mozilla.org mailing list (which is used to prioritize work on MDN and is open for anyone to participate). Bugs will be discussed there and the team can, collectively, decide what needs to be fixed before the redesign launches to the general public. We also will have a weekly, open meeting to make calls on anything that is stalled. Meetings are held every Tuesday at 17:00 UTC (10am PST) on IRC in #devmo.

Following development in real time

If you want to stay in the loop on a bug or a set of bugs, be sure to add yourself to the "cc" list. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are automatically pushed to the dev server every 5 minutes:

https://developer-dev.allizom.org/

The dev team pushes commits to stage and production servers when the code is ready. You can see which commits are on the stage & production servers here:

http://mzl.la/mdn_whats_deployed

Commits also often include numbers of bugs that you can visit to see relevant discussions.

Weekly Meeting Notes

General Questions

You can join the conversation in IRC.

  • #mdn for general discussion
  • #devmo for docs & content
  • #mdndev for platform coding

You can also join our mailing lists.

Thanks!

We are very excited to be launching the beta of this new design, and are even more excited to be working with you to make it better. Thank you for all of your feedback.

Retrieved from "https://wiki.allizom.org/index.php?title=MDN/Archives/Development/Redesign/Testing&oldid=1173981"