|
|
| Line 1: |
Line 1: |
| This is just a rough collection of things that we might want to consider when we start the MDN redesign. This is by no means a final list, and by no means well organized. Just a collection of ideas.
| | #REDIRECT [[MDN/Development/Brainstorming/Redesign]] |
| | |
| == Editing==
| |
| * When we added the "Report a Bug" button, many people filed bug reports about minor content problems. Why didn't these people realize that they could have edited the MDN themselves?
| |
| * We might want to take a look at what editors are trying to accomplish with templates, and look at supporting those things natively. Firefox sometimes does the same thing, pulling in features that started out as extensions and gained popularity (bookmark sync, highlighting the domain in the address bar, etc.).
| |
| | |
| === Structure ===
| |
| * People are trying to build high level structure into the MDN (for example, the JavaScript guide is basically a book) but we don't support that kind of structure natively. What if we did?
| |
| * Same thing with page order. We don't have any inherent concept of page order, forcing people to use templates to accomplish it.
| |
| | |
| === Moving pages ===
| |
| * This feature was sometimes abused on Mindtouch (for example, a user moving the entire DOM tree).
| |
| * What do users really <em>need</em> from this feature? What does it help them accomplish?
| |
| * What about administrators? What do they need from this? What does it help them do?
| |
| | |
| == Localization ==
| |
| * When a user reaches a page that hasn't been translated yet, they get a message explaining the situation and asking them to help with localization. But this message itself needs to be localized, defeating the purpose [https://developer.mozilla.org/ca/docs/HTML/HTML5 in some cases].
| |
| * Localizers should be warned (or better yet, prevented) from localizing variable names. Doing so can cause an internal server error.
| |
| | |
| == Information architecture ==
| |
| * Do we really need to keep the Community > Discussions menu item around?
| |
| | |
| == Demo Studio / Dev Derby ==
| |
| * The link between the Demo Studio and the Dev Derby is not especially obvious. Some people (even some people in Engagement) don't realize that they are complementary sister sites.
| |
| * It would be great to keep the long contest descriptions around even after the contest has ended. I spend a lot of time on these, and they usually provide pretty good guidance in getting started with the technology.
| |
| | |
| == Getting help ==
| |
| * When we used UserVoice, dozens of people reported issues with Firefox and Thunderbird. Ali mentioned that we could have a "Help" link on the MDN, with a few options: I want to report an issue with documentation, I want to report an issue with the underlying software, I want to report an issue with Firefox. In the latter case, we could just bump people over to SUMO, saving us frustration and helping those users get the help they need more quickly.
| |
| | |
| == Some features that could use thoughts from the user experience team ==
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=773054
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=770965#c3
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=773502
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=780224
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=770739
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=784564
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=784719
| |
| * https://bugzilla.mozilla.org/show_bug.cgi?id=784758
| |