search

promises-aplus / promises-spec

An open standard for sound, interoperable JavaScript promises—by implementers, for implementers.
https://promisesaplus.com/
Creative Commons Zero v1.0 Universal
1.84k stars 164 forks source link

Easy copy/pastable markdown to add logo to readme #132

Closed junosuarez closed 11 years ago

junosuarez commented 11 years ago

EG, I want to be able to close this issue https://github.com/jden/resolved/issues/3 really easily. If I get around to it, I'll submit a pull request

domenic commented 11 years ago

Have you seen the top of https://github.com/promises-aplus/promises-spec/blob/master/implementations.md ?

junosuarez commented 11 years ago

Ah, perfect. Would you be open to breaking the top bit of that out into a branding.md, with language at the top of implementations.md along the lines of "conforming implementations are encouraged to adopt the Promises/A+ branding as described in $link`?

domenic commented 11 years ago

I am ambivalent to creating a new file for that (and thus a new page on the gh-pages, once we do the redesign there). Thus I am inclined toward leaving things as they are. If anyone else has opinions, though, I am persuadable. @briancavalier?

briancavalier commented 11 years ago

I don't feel the need to create a separate page for it. Although I do think as part of the redesign, we should provide helpful links at the top of the spec to point to other useful information, like the list of implementations, the badge for compliant implementations, etc etc.

ForbesLindesay commented 11 years ago

I kind of like the idea of it being on a separate page, if only because the target audience of the pages should be very different. The list of implementations is primarily for users of promise libraries while the branding section is primarily for implementers of promise libraries.