Is this something you could know for any university? I imagine most private ones anyway would be pretty secretive about how many positions they reserve for so-called "legacy" students.
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.
It's describing the CMS, not the API. It's not so familiar to software engineer types, but is pretty well understood in publishing / Drupal / WordPress space.
So you're supposed to put test/markdown and images in it and basic structure like title/date/author? What about data oriented systems instead of content oriented?
I'm not sure I understand your questions. I haven't used GraphCMS so I don't know if they let you store HTML, but some CMS do, and yes that makes it harder to reuse your content in a context other than the web. I don't know, but I assume that you could probably make GraphCMS store HTML if you wanted to. The question of "can the CMS store HTML" seems orthogonal to the question of "Is it headless?" or "Does it have a GraphQL or REST API?"
It's been open to everyone 13 and up since 2006. I would know, I was a teenager at the time. And I looked it up before commenting. And age restrictions online are, well, easily ignored.
That is still pretty stupid. Either the website shouldn't be responsible for controlling access or they should have to take steps that are actually effective for controlling access. The idea that they have the responsibility to control access to their website but can fulfill that responsibility by doing something that they know is completely ineffective is pretty stupid.
1) A common pattern is having “page” components that render different layouts.
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.
This is a ridiculous comparison. How would you be enriching yourself by paying people to pick up trash? Did you get a contract from the government or the owner to pick up the trash? If you did, then yes you should probably take some of that money you made and hire some people to do the work or do it yourself.
> App Controls: Finally, starting on Monday, April 9, we’ll show people a link at the top of their News Feed so they can see what apps they use — and the information they have shared with those apps. People will also be able to remove apps that they no longer want. As part of this process we will also tell people if their information may have been improperly shared with Cambridge Analytica.
In your experience, what are the kind of things that people do in `componentWillMount` that they shouldn't be doing? Is it correct to say that `getSnapshotBeforeUpdate` is named to indicate what you were supposed to use `componentWillMount` for?
Thanks to you and brianvaughn for answering so many questions.
