I don't really get the GraphQL part yet either. I really like the concept of static sites with instant client-side page transitions, but for the vast majority of those, it doesn't seem like putting all the data into a GraphQL database before inserting it into the templates solves a problem?
I've been using React Static [1] for that now, where you just load the data in memory. I'd expected to discover in the process why GraphQL is so useful, but I did not. This might just be my limited point of view.
I guess as soon as you're dealing with lots and lots of data it might be useful, but the projects for which that is the case and which want a mostly-static site seem like they're a very small niche.
I've been using React Static [1] for that now, where you just load the data in memory. I'd expected to discover in the process why GraphQL is so useful, but I did not. This might just be my limited point of view.
I guess as soon as you're dealing with lots and lots of data it might be useful, but the projects for which that is the case and which want a mostly-static site seem like they're a very small niche.
[1] https://react-static.js.org/