Unblocked can not only ingest your code repositories, but also related material — your website, your product documentation, your conversations in GitHub issues and Slack — in order to provide a service that I call context assembly. I picked up that term from Jack Ozzie, back when he was working with his brother Ray on Groove, a peer-to-peer successor to Ray’s greatest hit, Lotus Notes, which pioneered what became known as knowledge management. Like Notes, Groove brought information work into shared spaces where you could search your mail, calendars, documents, and data all at once.
Carte is a simple Jekyll based documentation website for APIs. It is designed as a boilerplate to build your own documentation and is heavily inspired from Swagger and I/O docs. Fork it, add specifications for your APIs calls and customize the theme. Go ahead, see if we care.
We built Carte because the existing options (Swagger and the likes) were trying to do too much and did not match our needs:
Most of our API calls are sending JSON objects, as opposed to a series of parameters,
Being able to query the real API is nice, but running anything but GET calls can get tricky ("What do you mean I deleted my stuff? I was just trying out the API calls!"),
Overall, setting up a separate server for what really requires a good static documentation seemed overkill.
We built Carte because the existing options (Swagger and the likes) were trying to do too much and did not match our needs:
Most of our API calls are sending JSON objects, as opposed to a series of parameters,
Being able to query the real API is nice, but running anything but GET calls can get tricky ("What do you mean I deleted my stuff? I was just trying out the API calls!"),
Overall, setting up a separate server for what really requires a good static documentation seemed overkill.
