Closed
Bug 632195
Opened 13 years ago
Closed 13 years ago
[Demo Studio] More flexible tag curation / tag namespaces
Categories
(developer.mozilla.org Graveyard :: Demo Studio / Dev Derby, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
0.9.5
People
(Reporter: lorchard, Assigned: lorchard)
Details
Currently, tags and tag descriptions are devoted to technologies. But, it would help if tags were made more flexible, maybe through tag namespaces. For example, all technologies could be given a namespace prefix of tech:*. Other tags meant "for office use only" could be prefixed with system:* and their use restricted to site admins and editors. Expanding tags could allow them to be used for curating collections for contests, different kinds of highlighting than just "featured". Maybe something like "featured:2011-02-24" to indicate it was once featured but since removed from the featured set.
Assignee | ||
Comment 1•13 years ago
|
||
Pasting in an email from Jay as background for this bug: ---- From: "Jay Patel" <jay@mozilla.com> Sent: Wednesday, January 26, 2011 7:55:51 PM That does raise the question of how we'll specify and curate featured demos. There could always ever only be a finite number, say, always exactly 15 features. Then featuring a new demo means retiring an old one, and I doubt we want that. So if the number of featured demos continues to grow, always adding more and never defeaturing the previously featured, then the box on the home page probably shouldn't show * all * featured demos anyway. So if it's just the most recently featured, whatever number we decide on can be a multiple of three to avoid the jerky sliding. I had a discussion with Stormy today to talk about curating featured demos and also tagging a set as "top picks" (which may be any number from 2-5 at any given time) and a "winner" (which we'll have 1 of for any given week/month/quarter). This is a new feature we need to build in at some point soon after launch, since the devengage team wants to have regular contests to encourage new developers to submit demos and give out prizes as a result. Could we make it so that we can: 1. label any number of demos "featured" and then only display the top 15 (to make the slider work) based on the "feature" tag + most views? 2. allow admins to tag demos as "top picks" and set the limit to 5 so that the devengage team can manage that over time? 3. allow admin to tag a demo as "winner" and set the limit to 1? With 2 & 3, we would ideally be able to create a contest page that automatically filters for the "top picks" to display and then allows us to tag a "winner" that we can showcase at the top of the page at the end of each contest cycle. If it adds too much work right now to implement that, we can wait until after launch, but just wanted to give you guys a heads up that it's a new feature that we will need soon to meet our devengage goals. Thanks. - Jay
Target Milestone: --- → 0.9.5
Assignee | ||
Comment 2•13 years ago
|
||
Additionally, all localizable content for tags and tag descriptions are in code now, to make them easier to get into the l10n process. Might be nice to pull all of that up into the database, making them manageable from the admin pages rather than requiring code pushes. I don't think Verbatim supports this kind of l10n process at the moment, though
Assignee | ||
Comment 3•13 years ago
|
||
Another note-to-implementor: Since MDN pulled in kitsune, there's a small conflict between tagging apps. Demo studio originally used django-tagging, while Kitsune uses django-taggit. The latter is more modern, so it might be useful as part of this bug to migrate from tagging to taggit along with revising the tag namespace
Assignee | ||
Comment 4•13 years ago
|
||
Working on this alongside bug 657779, initially for dev derby features
Assignee: nobody → lorchard
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•13 years ago
|
||
Some groundwork leading up to this, but I think this does it: https://github.com/mozilla/kuma/commit/19bbfd1f9cf520ae392d1bd6659626dea64aa9bb Doesn't solve pulling l10n of tag descriptions out of hardcoded model, so that's probably worth another bug.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 6•13 years ago
|
||
qa-verified-trunk https://developer-stage9.mozilla.org/en-US/demos/tag/tech:css3/
Comment 7•13 years ago
|
||
verified fixed https://developer.mozilla.org/en-US/demos/tag/tech:javascript/
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
Version: MDN → unspecified
Updated•12 years ago
|
Component: Demos → Demo Studio / Dev Derby
Updated•4 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
•