canmove, Confirmed users
901
edits
WebAPI/DesignGuidelines: Difference between revisions
Jump to navigation
Jump to search
m
Add periods to make it screen reader-friendly
m (Add periods to make it screen reader-friendly) |
m (Add periods to make it screen reader-friendly) |
||
| Line 39: | Line 39: | ||
** create a JavaScript version. | ** create a JavaScript version. | ||
* '''keep your proposal short''' | * '''keep your proposal short''' | ||
* encourage counter proposals | * encourage counter proposals. | ||
** multiple proposals are good so don't be attached to your design in case it doesn't survive | ** multiple proposals are good so don't be attached to your design in case it doesn't survive. | ||
** solving the problem you set out to solve is more important than your proposed API getting standardized | ** solving the problem you set out to solve is more important than your proposed API getting standardized. | ||
* in advance, answer questions you anticipate and point people to the answers | * in advance, answer questions you anticipate and point people to the answers. | ||
* if you don't get responses, ask people you know who are more well-known in that community | * if you don't get responses, ask people you know who are more well-known in that community. | ||
* "it takes a village to raise an API" | * "it takes a village to raise an API". | ||
==Specification work== | ==Specification work== | ||