Caleb Cartwright

> I think trying to serve information we believe is wrong or outdated first is the wrong call. Good point. I'd already forgotten that the two endpoints need different inputs...

> Hi Would like to work on this issue. Can you guide me ? Great! We've got a detailed [tutorial](https://github.com/badges/shields/blob/master/doc/TUTORIAL.md) that walks through the process of adding a badge, so...

While this project does certainly fall into the category of the types of developer/technologist-centric service and has some good adoption and traction, I was also wondering about the documentation. One...

Thanks for facilitating the cross-thread comms @adriens! I confess I'm a little torn on whether we should proceed with the API in its current state or wait till it's more...

Yeah that sounds fair to me. I think as a related, but separate, followup it'd be worth considering augmenting the text with a clause to that effect

@adriens - we've got a great [tutorial](https://github.com/badges/shields/blob/master/doc/TUTORIAL.md) on adding new badges in case you or anyone else is interested in working on it!

@adriens - we're actually saying the opposite, and that we're fine with proceeding now given what the SDMAN maintainers have indicated

Confess I'm still not sure I'm following after reading through a couple times, but curious whether this is a case that would be better suited to our [Endpoint Badge](https://shields.io/endpoint)?

> but would require hosting the endpoint, which may be too much setup for users. This is a common and understandable intuition, but one which I tend to think is...

As I started pulling more of my notes together, I felt like there's potentially a few audiences for this material (as well as the rest of the material not yet...