Closed
Bug 800497
Opened 13 years ago
Closed 11 years ago
Rework Dev Derby to use a more sane date-based content interface
Categories
(developer.mozilla.org Graveyard :: Demo Studio / Dev Derby, defect)
developer.mozilla.org Graveyard
Demo Studio / Dev Derby
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: lorchard, Unassigned)
References
Details
(Whiteboard: [triaged][type:change])
When I first set up dev derby, I was lazy and expected requirements to change. So, rather than create a friendly admin UI, I built it such that you could manage it by editing lists of tags in the constance admin UI to control what content showed up when.
Since then, requirements have not changed much. So, it might be nice to revise the way Dev Derby works so that we don't have to edit long lists of tags.
| Reporter | ||
Comment 2•13 years ago
|
||
(In reply to John Karahalis [:openjck] from comment #1)
> Les, would bug 684070 cover this?
No. bug 684070 is about automatically rolling over to new content on a scheduled basis. This bug is about ditching the tag-based content management scheme. This bug could make bug 684070 easier, but they are not the same thing.
Flags: needinfo?(lorchard)
Updated•12 years ago
|
Whiteboard: [triaged]
Updated•12 years ago
|
Whiteboard: [triaged] → [triaged][type:change]
Comment 3•11 years ago
|
||
Dev Derby was put on extended hiatus with bug 1045796. Suggest WONTFIXING this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•6 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
•