Closed
Bug 665721
Opened 14 years ago
Closed 7 years ago
Allow editors to mark documentation as applying to specific products or versions of products
Categories
(developer.mozilla.org Graveyard :: Editing, enhancement, P3)
developer.mozilla.org Graveyard
Editing
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: openjck, Unassigned)
Details
(Whiteboard: [type:feature][triaged][pm-wanted])
No description provided.
![]() |
Reporter | |
Updated•14 years ago
|
Version: unspecified → Kuma
Updated•14 years ago
|
Assignee: lcrouch → nobody
![]() |
Reporter | |
Updated•14 years ago
|
Target Milestone: 1.0 alpha → ---
![]() |
||
Updated•14 years ago
|
Priority: -- → P2
Comment 1•13 years ago
|
||
What the heck is this bug about? :)
Comment 2•13 years ago
|
||
Sounds like tagging docs with, e.g., "Firefox 15" and "Webkit 534" - stuff like that?
Comment 3•13 years ago
|
||
Oh yes. This is about being able to mark content (articles or blocks within them) as applying to specific products or versions (or sets thereof). Right.
![]() |
||
Updated•13 years ago
|
Priority: P2 → P3
Assignee | ||
Updated•13 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•13 years ago
|
Component: Website → Landing pages
![]() |
Reporter | |
Comment 4•13 years ago
|
||
Sheppy: Is this still something you see yourself using?
Component: Landing pages → Editing
Summary: Kuma: Doc versioning and tagging for releases, vendors, versions, etc. → Allow editors to mark documentation as applying to specific products or versions of products
Whiteboard: [u: user] [c: wiki]
![]() |
Reporter | |
Updated•13 years ago
|
Flags: needinfo?(eshepherd)
Comment 5•13 years ago
|
||
(In reply to John Karahalis [:openjck] from comment #4)
> Sheppy: Is this still something you see yourself using?
Yes, frequently. It would also be used for content curation and to let users specify what compatibility needs they have and only see relevant content.
Flags: needinfo?(eshepherd)
![]() |
||
Comment 6•12 years ago
|
||
Isn't this something you would do with Template:CustomCSS? What is needed from the dev team?
Whiteboard: [type:feature][triaged]
Comment 7•12 years ago
|
||
(In reply to David Walsh :davidwalsh from comment #6)
> Isn't this something you would do with Template:CustomCSS? What is needed
> from the dev team?
We need UI for this, to make it easy for people to flag content as specific for given versions of browsers and the like. Using CSS under the hood makes sense, but there needs to be a button for "Mark content compatibility" (or whatever) that pops up UI for selecting product(s) and a version range for compatibility.
![]() |
||
Updated•11 years ago
|
Severity: normal → enhancement
Whiteboard: [type:feature][triaged] → [type:feature][triaged][pm-wanted]
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
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
•