Closed
Bug 1314058
Opened 9 years ago
Closed 8 years ago
Move Kumascript macros out of the Kuma DB and into the Kumascript GitHub repo.
Categories
(developer.mozilla.org Graveyard :: KumaScript, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rjohnson, Assigned: rjohnson)
Details
(Keywords: in-triage, Whiteboard: [specification][type:feature])
What problem would this feature solve?
======================================
Allows:
1. Better, code-oriented editing of Kumascript macros via GitHub
2. Better social/reputation building via GitHub
3. Faster macro loading during renders
Who has this problem?
=====================
Registered users of MDN
How do you know that the users identified above have this problem?
==================================================================
None
How are the users identified above solving this problem now?
============================================================
Using the custom MDN editing process for Kumascript macros
Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
This one.
Is there anything else we should know?
======================================
No
Comment 1•8 years ago
|
||
Macros imported into KumaScript repo:
https://github.com/mozilla/kumascript/pull/60
https://github.com/mozilla/kumascript/tree/master/macros
Deployed to staging and production.
Assignee: nobody → rjohnson
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
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
•