1) >>> Stripe runs on written long-form documents in a way that I haven’t seen before. <<< 2) >>> The product shaping document will come at it from the perspec

1) >>> Stripe runs on written long-form documents in a way that I haven’t seen before. <<< 2) >>> The product shaping document will come at it from the perspective of a user. <<< When you combine bullets 1 & 2, it makes for very good documentation. It was one of the things I loved about Stripe when I first tried to use them (plus the simplicity of the product at that time). However, my latest experience with Stripe is that their documentation is becoming similar to Google documentation i.e. multiple pieces of documentation describing the same thing but the different documentation is not consistent especially when they are using the same scenario. For example, you might see 2 different documents (from Stripe) that talk about embedding an online payment form and those 2 would have the same example but one would give the impression that you only need to deal with X attributes while the other one will show you that you actually need Y attributes. Some of the attributes could also be named differently (the name has probably changed and one document has not been updated while the other has or was written after the attribute was changed).