Provide a tree visualization of all articles (MDN index)

NEW
Unassigned

Status

Mozilla Developer Network
Design
--
enhancement
5 years ago
3 years ago

People

(Reporter: fscholz, Unassigned)

Tracking

(Blocks: 1 bug)

Details

(Reporter)

Description

5 years ago
On https://developer.mozilla.org/en-US/docs/all we currently list all articles (paginated).

While it's nice to have a list of all pages, they are not arranged in a neat way.
For reorganizing work / structuring our docs, a tree view might be more helpful (and I think structuring is an ongoing process, so having a dump of all pages is okay for now, but probably doesn't help in the longer term).

How about having all top-level docs (directly under /docs/) listed on https://developer.mozilla.org/en-US/docs/all and have links to e.g. https://developer.mozilla.org/en-US/docs/all/MathML which is then a list of pages in that level. Of course list pages which have no sub pages along with the "/all/<page>" links.

So e.g. on https://developer.mozilla.org/en-US/docs/all/XUL the index list has entries like:

https://developer.mozilla.org/en-US/docs/all/XUL/PopupGuide (has sub pages)
https://developer.mozilla.org/en-US/docs/XUL/Findbar (single page in the XUL/ level)
https://developer.mozilla.org/en-US/docs/XUL/browser (single page in the XUL/ level)
...and so forth.

We need some filtering happen here as well.
* don't list redirect pages (bug 763307)
* don't list "User:", "User:Talk", "Talk:" pages
* don't list templates

I don't know if the implementation of this feature is dependent or at least should be considered when fixing bug 773304 or bug 775527.

Comments? Ideas?
(Reporter)

Updated

5 years ago
Depends on: 763307
Something like this would be good. I'd like to have some kind of browseable tree view of the site available.
Component: Dashboards → Design / user experience
Summary: Tree view of all articles (MDN index) → Provide a tree visualization of all articles (MDN index)
Did we end up doing this with KumaScript?
Flags: needinfo?(fscholz)
Flags: needinfo?(eshepherd)
(In reply to John Karahalis [:openjck] from comment #2)
> Did we end up doing this with KumaScript?

No, and doing it with KumaScript is problematic. While we could create it, the script would take an inordinately long time to run and would need to be run periodically to stay up to date. This needs to be done in-platform.
Flags: needinfo?(eshepherd)
There was some tool started by David Bruant. We likely should build on that. (it is on github)
Cancelling need info for Florian as Sheppy answered.
Severity: normal → enhancement
Flags: needinfo?(fscholz)
(Reporter)

Updated

3 years ago
Blocks: 811056
You need to log in before you can comment on or make changes to this bug.