Intriguing venture. I have some feedback, please forgive the terseness: [1] Documentation: too dense, starts off with running a shell script, but it's not imme

Intriguing venture. I have some feedback, please forgive the terseness: [1] Documentation: too dense, starts off with running a shell script, but it's not immediately clear it's a quickstart, or to set up a dev environment, or what's going on. At least have an intro, or a table of contents, or something. [2] Speaking of documentation, I'm unclear where your product stands. Is it a 'build your own Lambda-as-a-Service provider', or some kind of meta-proxy-orchestrator that abstracts away from the actual LaaS provider? (if it's not the latter, why link to every commercial LaaS offering? Aren't they competitors?) [3] Our Team: "coming soon". I sympathize with having a lot to do on a website, but I care about your credentials if I am to run some code. Or maybe I don't, since lots of projects are popular on github and you don't necessarily know all of their authors in detail. But if you don't have it yet, don't highlight it in your menu. [4] Your github is barebones and links back to the aforementioned docs page. It's a bit like running in circles. Have a short readme on github, then you can link somewhere else! [5] On the front page, all 'learn more' buttons go to the same place. But, why have these at all? (see, #2. maybe move these into a 'Why' page that explains your pitch and how LaaS is big and these are the big players that are also doing it) [6] Edit: the slides are good and they help me understand what's going on.