Craft CMS Reviews

GraphQL Playground Reviews

Craft CMS mentions (31)

• Different flavors of content management

  The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to... - Source: dev.to / 9 months ago

• Go with PHP

  PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves... - Source: Hacker News / about 1 year ago

• Stack to build and deploy a fully functional personal blog?

  You're basically looking for any CMS that supports headless mode. E.g. Strapi (https://strapi.io/, NodeJS based), CraftCMS (https://craftcms.com/, PHP based) or countless others. Source: about 1 year ago

• A mate of mine built a cool little Tottenham Database showing the history of spurs.

  It's built on Craft CMS. Makes the relationships between elements (a match and a player, for example) super easy. Source: about 1 year ago

• Creating a CMS with React, what should I look at?

  Is there a reason you aren’t using an existing CMS? There’s a lot that provide all the UI functionality you are talking about and then expose it via a API to be consumed in your front end. https://craftcms.com is one option I’ve had good success with. Source: over 1 year ago

GraphQL Playground mentions (11)

• Exploring GraphiQL 2 Updates and New Features

  GraphiQL is a tool that was created to help developers explore GraphQL APIs, maintained by the GraphQL Foundation. But when GraphiQL became more and more popular, developers started to create additional GraphQL IDEs. A good example of this was GraphQL Playground, which quickly became the most popular GraphQL IDE. It was loosely based on GraphiQL, but had more features and a better UI. - Source: dev.to / over 1 year ago

• Why Is It So Important To Go To Meetups

  I went to a GraphQL meetup and they used the gql playground and a similar schema generator to what I was using, and it made me feel relevant. - Source: dev.to / about 2 years ago

• GraphQL subscriptions at scale with NATS

  Here, we'll create a simple GraphQL server and subscribe to a subject from our resolver. We'll use GraphQL playground to mock client side behavior. Once we're connected we'll use NATS CLI to send a payload to our subject and see the changes on the client. - Source: dev.to / over 2 years ago

• GraphQL vs REST in .NET Core

  Now we can consume created GraphQL API. In the GitHub Repo same functionality has been added with REST approach and GraphQL endpoint. Also widely used Swagger configured for Web API Endpoints as well as AltairUI added for GraphQL endpoint testing. Naturally, AltairUI it not a must for GraphQL, you can also use Swagger, GraphiQL, or GraphQL Playground. - Source: dev.to / over 2 years ago

• Creating GraphQL Api Using NestJS For Multiple Databases

  Navigate to http://localhost:3000/graphql. NestJS uses graphql playground by default. It's a lovely GraphQL IDE. We can check our schema here. - Source: dev.to / over 2 years ago