ContentQL allows one to access Contentful data using Om Next Queries.
Contentful is a popular headless, cloud-based CMS system. Beyond being purely an API-first CMS system it also supports somewhat complex data schemas, responsive images and webhooks making it a very compelling content platform.
Despite the great features provided by Contentful, one thing remains somewhat challenging: its API is not the most straightforward to use.
Instead of porting Contentful's API on a one-on-one basis to Clojure and ClojureScript, this library takes an abstraction route to querying: it uses Om Next's Query language as its main interface.
Add the following dependency to your project.clj
file:
By using Om Next queries one can:
ContentQL's key features are:
clojure.core.async
and cljs.core.async
supportThe Om Next query syntax is beautifuly described by António Monteiro here but if you need a quick primer, here it is:
If you have a content type called blogs
, you can query its entries with:
'[:blogs]
You can always combine several content types in one go:
'[:blogs :articles]
If you want just the title
and the body
of your blogs
, you can use a join such as:
'[{:blogs [:title :body]}]
Assuming your blogs
content type has an author
embedded whose name
you want to fetch
as well, simply nest your joins:
'[{:blogs [:title :body
{:author [:name]}]}]
This will continue to give you the title
and the body
of each blog entry but now also
the name of each blog's author.
Queries can be parametrized by using a list where the second element is a map of parameters.
If you want the blog identified by id
"3x1YMtJ1CoOWk0ycYsOw4I"
you can fetch it with:
'[(:blogs {:id "3x1YMtJ1CoOWk0ycYsOw4I"})]
This can be combined with joins, ie:
'[({:blogs [:title :body]} {:id "3x1YMtJ1CoOWk0ycYsOw4I"})]
Or even nested joins:
'[({:blogs [:title :body
{:author [:name]}]}
{:id "3x1YMtJ1CoOWk0ycYsOw4I"})]
All your content types can be queries as part of a query root.
You've already seen above how to query a specific entry by its id
:
'[(:blogs {:id "3x1YMtJ1CoOWk0ycYsOw4I"})]
In addition to :id
the other supported query root parameters are:
:limit
- limits the page size to its value (i.e. :limit 10
):skip
- skips the specified number of entries (i.e. :skip 5
skips 5 entries):order
- allows ordering of the entries (i.e. :order "fields.name"
ordres the dataset by name
). Reverse ordering is supported with the addition of -
(i.e. :order "-fields.name"
)Any image asset is immidetally wrapped in an image entity containing three fields :width
, :height
and :url
. The asset can be scaled up or down by sending the intended :width
or :height
parameter.
In order to see it in action, suppose your author
has an avatar
image and you want it constrained within a width
of 150 pixels:
'[{:authors [({:avatar [:width
:height
:url]}
{:width 150})]}]
Async channels are slightly different between Clojure and ClojureScript due to underlying characteristics of how the JVM and the JavaScript environment deal with multi-threading. ContentQL supports both platforms seamlessly.
For Clojure, require contentql.core
and clojure.core.async
:
(ns my-project
(:require [contentql.core :as contentql]
[clojure.core.async :refer [go <!]]))
For ClojureScript, require contentql.core
and cljs.core.async
:
(ns my-project
(:require-macros [cljs.core.async.macros :refer [go]])
(:require [contentql.core :as contentql]
[cljs.core.async :refer [<!]]))
Then create a Contentful connection with contentql/create-connection
. It receives four fields :space-id
, :access-token
, :mode
and :environment
. Use the space id and access token found on your Contentful dashboard. :mode
should be either :live
(for production environment) or :preview
for (guess what, preview mode). Lastly, :environment
should be the environment you want to fetch data for.
(def config {:space-id "c3tshf2weg8y"
:access-token "e87aea51cfd9193df88f5a1d1b842d9a43cc4f2b02366b7c0ead54fb1b0ad6d4"
:mode :live
:environment "master"})
(def conn (contentql/create-connection config))
Once your connection is created, send it to contentql/query
with your query along:
(go
(let [res (<! (contentql/query conn '[{:blogs [:id :title]}]))]
(println res)))
contentql/query
returns an async channel. The snippet above uses a go
block to send the code to a separate thread. If you are in Clojure and want a blocking alternative, simply import <!!
from clojure.core.async
and use the returned channel like this:
(<!! (contentql/query conn '[{:blogs [:id :title]}]))
Pagination is supported by default on all query root (all your content types). Your response
will be wrapped in a map containing a :nodes
field and an :info
field. The former will
encapsulate the entries for the current page while info gives you some metadata about the
total universe of entries and the page you are in. This is a typical :info
map:
{:nodes {:total 33}
:page {:size 4
:current 1
:total 9
:has-next? true
:has-prev? false}
:pagination {:cursor 0
:next-skip 4
:prev-skip 0}}
This tells us that there are 33
total nodes in the dataset while the page size is 4
.
This payload represents page 1
of a total of 9
pages. There are a next page from where we
are but no previous page. The starting cursor for the page is entry 0
(the very first one)
and to get to the next page we need to skip 4
entries.
Pagination is achieved by manipulating the parameters :limit
(to specify page size) and
:skip
(to specify how many entries to skip). These two parameters can be sent to any query
root.
If you find a bug, submit a Github issue.
This project is looking for team members who can help this project succeed! If you are interested in becoming a team member please open an issue.
Copyright © 2017 Tiago Luchini
Distributed under the MIT License.
Can you improve this documentation?Edit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close