WebAPI/DesignGuidelines: Difference between revisions

Jump to navigation Jump to search
m
Line 7: Line 7:
* If this is (one of) your first web APIs, keep your scope narrow.
* If this is (one of) your first web APIs, keep your scope narrow.
** With some experience, you'll see fundamental issues with the web platform for which you can propose fixes!
** With some experience, you'll see fundamental issues with the web platform for which you can propose fixes!
** If this is your first web API, work with a co-editor that has bandwidth to help you.
** If this is your first web API, work with a co-editor who has bandwidth to help you.
* Publicly discuss & document use-cases, motivations, and design sketches early, often, and widely (e.g. [[IRC]], wiki (here on WikiMo or http://wiki.whatwg.org/ ), applicable W3C/WHATWG lists, [https://lists.mozilla.org/listinfo/dev-webapi dev-webapi], [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia], blogs, Twitter, GitHub issues, etc.).
* Publicly discuss & document use-cases, motivations, and design sketches early, often, and widely (e.g. [[IRC]], wiki (here on WikiMo or http://wiki.whatwg.org/ ), applicable W3C/WHATWG lists, [https://lists.mozilla.org/listinfo/dev-webapi dev-webapi], [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia], blogs, Twitter, GitHub issues, etc.).
* Avoid scope creep by avoiding trying to fix unrelated problems.
* Avoid scope creep by avoiding trying to fix unrelated problems.
Confirmed users
328

edits

Navigation menu