25 karma · joined February 18, 2018
Perhaps your CMS serves multiple front ends: a website, or a mobile app.
> Why would I want a CMS based on GraphQL?
The way I see it, the CMS is not based on GraphQL, it's just a CMS that you can query with GraphQL. I haven't used GraphQL at all, but it seems like it could be useful for working within a system where you need to bring data from many different REST endpoints together. Usually I would have to hand code something like this myself on the backend, but with GraphQL it seems like once you have it all set up, you can get data from multiple APIs, while specifying the schema of your response on the client instead of on the backend.
> What is wrong, with plain old HTML?
Nothing, if you can build what you want to build with "plain HTML" then do it.
2) Yes, start out by learning to fetch data in componentDidMount and then calling set state with the result. It’s usually a good idea to do this at the top level of your app and pass it down to child components. Don’t look into Redux or MobX or anything like that until you run into problems. Most people do not need a separate library for managing state.
3. react-router is not “official” but it’s pretty damn close, probably the most popular. Look into next.js if you want client and server side routing.
> /u/ythn is the worst CEO ever, he gluts himself off of the labors of the socioeconomicly desperate!"
Thanks to you and brianvaughn for answering so many questions.
Yes, clearly the solution to this problem is BTC, NOT some kind of other reform or liberalization. </s>
Other things on my list to try are Phaser for the easy cross platform distribution (it's JavaScript) and Godot, because although I enjoy coding little games "from scratch" I feel like I would be much more productive with the tools that Godot or Unity offer.
Here's my little game: https://github.com/dj/dinojump