I totally agree with the need to be cautious - however, if there's one thing that Big Tech has taught me, it's that there will be 20 other people in the room that will remind you of exactly what you are suggesting. There's plenty of pessimism to go around, not enough optimism.
Very cool. I feel like this is the early version of a "programmable Notion[1]" in some ways which is built on similar building blocks that are customizable.
For anyone interested in this space and wishes something like this existed for Android, I got you covered! I open sourced this project last year - https://github.com/airbnb/Showkase
I have a really similar motivation behind a project that aims to teach Jetpack Compose in the same fashion and funny enough, the name is also pretty similar to the title of this thread - Learn Jetpack Compose By Example. You can find it here - https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Exampl...
There's a ton of comments in every example (even though they might be redundant across the examples) and the idea is that you should be able to learn this new framework by merely reading through the examples.
I built an open source library for Android called Showkase [1]. Showkase autogenerates a UI component browser for your Jetpack Compose components on Android and allows you to search, visualize and organize your UI elements. Think Storybook but for Android development.
I think a lot of people assume that Jamstack sites need to be static sites through and through. I don't think this is realistic and you will be overcomplicating things for yourself if you try to do this. For things that don't change often, having a static site has obvious benefits and Jamstack is well suited to build those parts of your site. For user generated content, you are better off just storing it somewhere else and loading it dynamically.