Features/Jetpack/Make Add-on SDK Hug the Web Harder: Difference between revisions

m
no edit summary
No edit summary
mNo edit summary
Line 20: Line 20:


In the future we might even consider making the experience of developing an add-on resemble creating for the web by moving main.js to main.html and making the relative paths work as they do when developing a website.
In the future we might even consider making the experience of developing an add-on resemble creating for the web by moving main.js to main.html and making the relative paths work as they do when developing a website.
|Feature users and use cases=The target audience is addon developers. The use case is an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) to build an addon.
|Feature users and use cases=The target audience is addon developers. The use case is an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) to build an addon.
}}
}}
Line 29: Line 28:
|Feature engineering team=Jetpack
|Feature engineering team=Jetpack
}}
}}
{{FeatureTeamStatus
{{FeatureTeamStatus}}
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits