Support for external CMSs

fredmontet · November 17, 2020, 10:05am

Hi everyone,

I’m interested to use RedwoodJS with external CMSs, for instance Sanity as in this article: RedwoodJS with Sanity.io CMS as Backend - DEV Community

At the moment, I’m using DatoCMS and would love to migrate my codebase to RedwoodJS but keep my content at the same place.

Is such a feature already available? Did someone tried something with other headless CMSs using GraphQL?

peterp · November 17, 2020, 12:22pm

Hey @fredmontet

I don’t see why it wouldn’t be possible. We have a concept called “services” as a way to specify resolvers for your GraphQL schema.

In our tutorial we fetch data from Prisma, but the data can come from anywhere. So… if DatoCMS has an api then you can create a service that retrieves your content from them and make it available via a GraphQL field.

If you do not wish to create GraphQL types for the payload returned from DatoCMS you can create a JSON field type and simply return the result from DatoCMS.

fredmontet · November 19, 2020, 8:36am

Thanks @peterp!

I did a POC with a couple services and it indeed works perfectly.

Also, in order to avoid remaking the schema of each ressource, I tried another way: to change the GraphQL client used by the RedwoodProvider so that it uses DatoCMS but struggled a bit, mainly because DatoCMS asks for an auth token.

Do you have any suggestions regarding this, or would it simply be better not to consider this?

Tobbe · November 19, 2020, 8:54am

This sounds super exciting! We have an open issue that’s related. Please feel free to add any relevant input you might have to that issue

github.com/redwoodjs/redwood

[RFC] Bring your own GraphQL library

opened 09:19AM - 10 Sep 20 UTC

closed 09:29AM - 19 Mar 21 UTC

peterp

Right now Redwood ships with Apollo's GraphQL client out of the box. We don't kn…ow if that will change, but we would love to give you the ability to switch to the GraphQL client of your preference. As a user, nothing will change if you're happy with the GraphQL client! This is only for people who would want to change the client. How does this work right now? Right now we initialise the Apollo GraphQL library in `<RedwoodProvider>` where we do two things: 1. We grab the `API_PROXY_PATH` value from the `redwood.toml` configuration to point to the URL to your GraphQL server. 2. We determine if you're users are authenticated and we put the appropriate `Authorization` headers into the GraphQL clients configuration. How would you specify your own GraphQL client? ```js // ./web/src/index.js return ( <AuthProvider> <RedwoodProvider graphQLClient={({ url, headers }) => new GraphQLClient(url, { headers })} queryHandler={({ query, variables }) => useQuery(query, { variables })} > </RedwoodProvider> </AuthProvider> ) ``` We would provide the url to your GraphQL server and headers to facilitate authentication, which you would pass to the configuration of your client. You would also need to let us know how to run run queries. Let me know what you think!