Make it clearer on our landing page that Wasp is proper framework and not a one-shot code generator

[Martinsos]

Motivated by this convo on Discord: https://discord.com/channels/686873244791210014/1277607531363172496/1277645496743231550 .

we wanted to make sure that wasp was not just a beginner friendly "vendor" lockin which seems to NOT be the case. Building on this it would be beneficial for this information to be transparent to help developers who DO want to fast track their development but also do have scaling concerns. This is to make sure that wasp does not appear just as a quick way to MVP but as a quick way to bootstrap enterprise quality webapps

Motivated by this I took a look at our landing page and I wonder how clear is it at all that Wasp is not a one-shot code generator but a proper framework.

For example that diagram we have, if you look at it quickly, looks like it is code generator, not a framework.

Seems to me like one would have to read the landing page quite carefully to get the right notion!

We should probably make it clear what Wasp is + modify that diagram or text around it to make it very clear that Wasp is not a code generator. Maybe the diagram should go somewhere lower, it is really talking about the impleemntation details that are not that super important to somebody just learning about Wasp, while they don't still get what it is.

[Martinsos]

I think adding additional details for the “Production / Scaling” part of the docs would indeed be the best choice since you can pretty much explain what I was told here, that basically people have nothing to fear because at the end of the day they can use the same tools they could use directly from the JS ecosystem for scaling or tackling similar concerns (even if you don’t have internal solutions for that at this point).

In general, in these docs I would want to be reassured through that production section that Im “buying” into a framework(lang?) that takes care (or at least does not stop me from doing it) of security, scalability, maintainability since Im already sold on ease of use, speed and efficiency.
Actually that would solve a major issue of choosing to develop (backend) in the JS ecosystem in general not just wasp