Closed
Bug 920530
Opened 11 years ago
Closed 11 years ago
[tracker] support Webmaker on SUMO
Categories
(support.mozilla.org :: Knowledge Base Software, task)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
RESOLVED
FIXED
2013Q4
People
(Reporter: atopal, Unassigned)
Details
* Webmaker specific KB dashboard * Webmaker specific L10n dashboard * Add Webmaker topic to AAQ * Add Webmaker as product to Questions listing * Add Webmaker to Army of Aweomse
Reporter | ||
Comment 1•11 years ago
|
||
I'll file the bugs individually, just collecting for now.
Comment 2•11 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #0) > * Webmaker specific KB dashboard > * Webmaker specific L10n dashboard We have this right? https://support.mozilla.org/en-US/contributors?product=webmaker https://support.mozilla.org/es/localization?product=webmaker
Comment 3•11 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #0) > * Add Webmaker as product to Questions listing This comes for free once we enable the product and add it to AAQ. For example: https://support.mozilla.org/en-US/questions?product=firefox-os
Comment 4•11 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #0) > * Add Webmaker to Army of Aweomse I assume this is just adding 'webmaker' as a search keyword to track: https://twitter.com/search?q=webmaker easy peasy
Reporter | ||
Comment 5•11 years ago
|
||
* Add Webmaker discussion forum
Reporter | ||
Comment 6•11 years ago
|
||
For clarification: The KB and localization dashboards are not showing Webmaker yet because it's not marked as visible. As soon as it is visible the dashboards will be available. Re AoA: since we have many more Firefox tweets, webmaker tweets would be hard to even spot. It would be better to give them their own view, but that's out of scope for now. Just listing it here for completeness.
Reporter | ||
Comment 7•11 years ago
|
||
I think we are done here. Thanks everyone!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•