Closed
Bug 774383
Opened 13 years ago
Closed 11 years ago
In template editor, indicate how many pages use that template and list some examples
Categories
(developer.mozilla.org Graveyard :: Wiki pages, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: openjck, Unassigned)
References
Details
Jean-Yves made a very interesting point in this comment:
https://bugzilla.mozilla.org/show_bug.cgi?id=773855#c1
We should help template writers realize how much their changes can impact the rest of the MDN. It would be great to indicate, somewhere on a template's editing page, how many pages use that template.
Some design ideas:
1. Provide a message that lists the exact number.
2. Provide a message like "This templates is used on {dozens,hundreds,thousands} of pages."
3. Highlight the message if it is used on more than N pages?
Reporter | ||
Comment 1•13 years ago
|
||
Sheppy: Any thoughts on this?
Comment 2•13 years ago
|
||
I think this would be useful, although I think a bonus atop seeing a list of the actual pages (since that would help find samples of the usage).
Reporter | ||
Updated•13 years ago
|
Summary: In template editor, highlight how many pages use that template → In template editor, indicate how many pages use that template and list some examples
Comment 3•13 years ago
|
||
Basically, the hurdle to implementing something like this is that there is no index of templates-per-page or pages-per-template - and there's no easy or simple way to build one.
:davidwalsh has an initial stab at this, but it's a bit inaccurate and demanding on the database & browser:
https://github.com/mozilla/kuma/pull/414
I also have bug 767176 to build a system that records templates used in the course of building a page. That info could be used to build an inverse index - ie. pages per template. But, that tracking demands some additional IT infrastructure, along with hooks into kumascript itself to record the templates - so, not a thing to expect done soon.
Reporter | ||
Updated•13 years ago
|
Priority: -- → P3
Comment 4•13 years ago
|
||
FWIW, here's an interesting template use case that makes this even more challenging:
https://developer-new.mozilla.org/en-US/docs/Template:InterfaceEntry
That template uses the value of a parameter to decide the name of another template to call at run time.
Assignee | ||
Updated•12 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Website → Landing pages
Reporter | ||
Updated•12 years ago
|
Priority: P3 → P2
Reporter | ||
Updated•12 years ago
|
Whiteboard: u= c= s= p=
Reporter | ||
Comment 5•11 years ago
|
||
We have this, albeit in a slightly different form. Every template has a link to a search of that template, which in turn lists the number of documents found.
E.g. https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=DevProgramListSOTopics
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•