4 ms·
Wow, thanks for the kind words! I'm blushing over here. I wrote a big portion of our docs and would love to know which parts could be fleshed out more (I can th
by mwetzler 12y ago
Wow, thanks for the kind words! I'm blushing over here. I wrote a big portion of our docs and would love to know which parts could be fleshed out more (I can think of a few areas but I'm curious what you think).
- fomojola 12y agoYou're welcome: Keen's been great to work with. Mostly just organization: as far as I can tell you've recently started maintaining some of the docs at the Github repo, but much of the original writeups were on https://keen.io/docs/clients/javascript/reference/ https://keen.io/docs/clients/javascript/reference/. It makes it a little confusing jumping around and linking back and forth when you trying to figure out how to do a new thing. For my money (not much of it, but its what I have) Stripe's API doc reference (https://stripe.com/docs/api https://stripe.com/docs/api) which wraps both the concepts and the code samples into a nice little ball are still the gold standard.
- mwetzler 12y agoAh yes, we are in an awkward zone with some docs on our site in Sphinx and others on Github. We love that developers can PR our docs on Github, and we agree that Stripe's docs are the BEST. At some point we will tackle a doc revamp that puts us in that direction. The personalized code samples & easy library switching features of Stripe docs are a dream.