Thanks for the kind words! 1. I'm working on the admin panel, but it's not yet ready. I'm still hesitating how to approach the persistence layer without introd

Thanks for the kind words! 1. I'm working on the admin panel, but it's not yet ready. I'm still hesitating how to approach the persistence layer without introducing too many abstractions. Generally speaking, I'd like to avoid ORMs as much as possible. :) 2. I use the node-pg-migrate [1] for migrations at the moment, but I plan to tightly integrate with Postgraphile / Hasura to give another approach for that part. 3. You need to add them manually, but the architecture is pretty close to Vite [2]. You have just one Node process for both front-end & back-end: in development I compile assets on the fly using ESBuild [4], in production I bundle them using Rollup. I should probably describe that in the docs more clearly :) In contrast to Vite, Kretes also provide a REST API out-of-the-box, and a relatively simple path for adding a GraphQL endpoint. 4. The current query builder - sqorn [5] - has a nice syntax as it uses the same vocabulary as SQL, but it's not typed. My goal is to create a fully typed TypeScript query builder that's adapted only for PostgreSQL. Here's the preliminary work for that [3] 5. I'm still working on the docs. I'll fix the things you mentioned right away. [1]: https://github.com/salsita/node-pg-migrate https://github.com/salsita/node-pg-migrate [2]: https://github.com/vitejs/vite https://github.com/vitejs/vite [3]: https://github.com/typeofweb/functional-orm https://github.com/typeofweb/functional-orm [4]: https://github.com/evanw/esbuild https://github.com/evanw/esbuild [5]: https://sqorn.org/docs/about.html https://sqorn.org/docs/about.html