Mike, thanks for the feedback! As a solo founder with a short amount of time before launch (and a day job), I had to decide to focus on only one thing for the

Mike, thanks for the feedback! As a solo founder with a short amount of time before launch (and a day job), I had to decide to focus on only one thing for the main landing page. That ended up being selling the benefits of the product instead of focusing on the technical details. I recorded a 2 hour screencast going through the entire backend for devs who are interested in that — and I also plan to put together a blog post outlining all the tradeoffs I made. I'm sorry the documentation doesn't explain enough yet — I know it's lacking. However, you're partly right: I think the people who would benefit the most from using Remake are probably designers and developers with 3-4 months of experience. Long term, I think they'll be at least 70% of Remake's market. However, I think it's also a great tool for more experienced developers like you. It's true that you can make other stacks work for you, and, especially if you have a starter project you can clone, you can get something up and running within a few hours. However, Remake's true strength comes from the power of its mental model. The page state, page logic, and page structure are all nested together in HTML template files — which are the only files you need to create an entire web app, including saving data, enabling user accounts, advanced routing, and performing CRUD operations. That's a pretty powerful way to build something. As someone with 8 years of experience building web apps, I can say with confidence that Remake speeds me up at least 500% when it comes to building simple CRUD apps. It's not good with building social networks or analytics platforms, but it's perfect for simple page builders. I'd recommend giving it a shot and seeing if it appeals to you before dismissing it. If nothing else, it might help you test out a few ideas you might dismiss otherwise simply because you can build them so fast!