I guess this could come in handy for many repos! Nice work, I'm eager to give it a try.

Thanks! Feel free to join our discord at https://reviewpad.com/discord to give us some feedback!

Thanks for posting my article.

Thanks for the nice words! Glad you find the page useful.

Docusaurus FTW! I have yet to try it, but it's come across my lense a lot lately. Deffo going to use it for my next docs site.

Great! Let me know if you have any question

We're actually looking for a static website platform, to use in tandem with Docusaurus. Any guides on how to do it with Docusaurus alone?

Not sure to understand what you mean here, can you explain?

Docusaurus is a static site generator, a bit similar to Gatsby. It's opinionated toward docs/blog/pages but you can also use it in a more generic way.

Indeed, that was it. I think maybe we'll give it a try!

Great writeup and comparison. Also, serverlessq looks really interesting. I've struggled with queues quite often in the past – can't wait to give this one a try.

Thanks a lot!

If you want, give ServerlessQ a try and let me know if you need any help! You find my contact info on my landing page: serverlessq.com or DM me on twitter: twitter.com/sandro_vol

Author here. Haha! You are right. I admire Stripe's API and there's absolutely a lot of things in it that are my "benchmark" when it comes to good APIs. However, they return UNIX timestamps, for example, which I don't like that much (as stated in the post). They also use POST for updates, because, if I recall correctly, PUT/PATCH wasn't a thing yet when Stripe was built initially. Thanks for the comment.

Author here. I read that a couple of times already. RFC 3339 is what you should use - I should probably change that (it's what I actually meant). :) Thanks for pointing that out.

Author here. Thanks for the nice words - I appreciate it. I've read that a couple of times in the comments already. Definitely something worth considering, Stripe does this as well. Thanks for your comment.

Author here. I generally agree - IF something goes terribly wrong within the application, a 500 is definitely the way to go. The thing is - these just shouldn't happen that often. Because in that case we're having a bigger problem. :D For example I have never seen Stripe return a HTTP 500 from their API. Thing just works.

Hey thanks for your input. These are great additions!