Phase 1 Redesign: Demo Page update

RESOLVED INVALID

Status

Mozilla Developer Network
Design
RESOLVED INVALID
5 years ago
4 years ago

People

(Reporter: Habber, Assigned: Habber)

Tracking

Details

(Whiteboard: [specification][type:feature])

(Assignee)

Description

5 years ago
What problems would this solve?
===============================
Demo page currently displays content across ~588 pages with filtering and search options. With the high volume of content, we can better facilitate users in finding demos that pertain to them. 

We need a more direct route to narrowing the list of demos we display to the user since there is a high volume of demos that will only grow.

We should explore both alternate ways to filter and display the content, as well as ways we can promote our community members who continually contribute to MDN. 


Who would use this?
===================
Users that are looking for a particular type of demo.

Users who are looking for a tangible example in order to solve their problem or learn more about a technology. 

Community members that contribute by submitting demos.

What would users see?
=====================
Updated organization of demos and methods available to navigate them.

What would users do? What would happen as a result?
===================================================
When arriving to the demo section, the user would have a better overall understanding of the types of demos we offer. They would also have a more direct path to a selection of demos that relate to what they are looking for.

A reorganization here could also benefit and promote our demo content appearing in non-MDN search results. 

Is there anything else we should know?
======================================
This bug also exists to solve any additional improvements we can make based on our improvements to elastic search. More details to come.
(Assignee)

Updated

5 years ago
Component: General → Design / user experience
(Assignee)

Comment 1

5 years ago
This bug solution is a little less defined than the others being filed for Phase 1. After discussions with the MDN team, we can further define what will be done here.
Assignee: nobody → hhabstritt.bugzilla
(Assignee)

Updated

5 years ago
Blocks: 844971
(In reply to Holly Habstritt [:Habber] from comment #1)
> This bug solution is a little less defined than the others being filed for
> Phase 1. After discussions with the MDN team, we can further define what
> will be done here.

Totally. Bringing the team into the discussion. We might need to break this one down depending on how big the goal becomes, but for now I will leave it as-is.
The ideas I've heard that I like the most are:

* Cross-link between docs and demos by technology - the most direct to relevant demos.
* Visually display docs and demos in the search results page, facet/filter by technology
We have bug 839345 for the former. Lots of good UX-y discussion in there.
Is this the place to bring up the notion that we should attempt to devise an automated mechanism by which terms used in non-wiki content automatically get linked to the documentation in the wiki (similar to what the PromoteMDN WordPress add-on does)?
(Assignee)

Comment 6

5 years ago
There is a lot of valuable discussion in this bug. However, I am going to close it since the MDN redesign goals have changed a bit. I don't want anyone being confused with the out-dated problem statement or goals that are being proposed here. We will create a new UX bug in the future for this if necessary.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
(Assignee)

Updated

5 years ago
No longer blocks: 844971
You need to log in before you can comment on or make changes to this bug.