It's frustrating as this product looks like a great idea and looks well done, but you're leaving out all the important bits of information that I'd want to know immediately.

Do I have to request the the content from prismic with every request? Is it done client or server side? What kind of caching will I be able to do my end? What happens when you go down?

That website and especially the video are terrible at communicating (pan, pan, pan, pan, pan, arghhhhhh). I thought it was because I was watching it without sound. Turns out there is no sound.

It visually looks great, but the content itself is practically useless, classic style over substance.

And the API documentation is bad. What does the first section of the documentation even mean?

/api is the single endpoint of your content repository. You can learn and browse everything else from there. You should never forge any API URL in your code, as all usable forms (that define what URLs you can build) are available in /api (and the URLs might change as features get rolled out).

I (finally) found the api which is hidden in the help menu of all places and kinda can guess what you're supposed to do, but I think you've a few rough edges to sand off in the usability.

Gratz on the launch, but get someone in to help you write the copy and overhaul those API docs.