Welcome! Renderful is a rendering engine for Contentful spaces. It allows you to map your content types to Ruby objects that take care of rendering your content.
Add this line to your application's Gemfile:
gem 'renderful'And then execute:
$ bundleOr install it yourself as:
$ gem install renderfulOnce you have installed the gem, you can configure it like this:
contentful = Contentful::Client.new(
space: 'CONTENTFUL_SPACE_ID',
access_token: 'CONTENTFUL_ACCESS_TOKEN',
)
renderful = Renderful.new(
contentful: contentful,
renderers: {
'jumbotron' => JumbotronRenderer,
}
)Suppose you have the jumbotron content type in your Contentful space. This content type has the
title and content fields, both strings.
Let's create the app/renderers/jumbotron_renderer.rb file:
class JumbotronRenderer < Renderful::Renderer
def render
<<~HTML
<div class="jumbotron">
<h1 class="display-4"><%= entry.title %></h1>
<p class="lead"><%= entry.content %></p>
</div>
HTML
end
endYou can now render this component by retrieving it from Contentful and rendering it with Renderful:
entry = contentful.entry('jumbotron_entry_id')
renderful.render(entry)If you have rich-text fields, you can leverage Contentful's rich_text_renderer along with a custom local variable:
class TextBlockRenderer < Renderful::Renderer::Rails
def html_body
RichTextRenderer::Renderer.new.render(entry.body)
end
def locals
{ html_body: html_body }
end
endThen, just reference the html_body variable as usual:
<%# app/views/renderful/_text_block.html.erb %>
<%= raw html_body %>What if you want to have a Grid component that can contain references to other components? It's
actually quite simple! Simply create a References field for your content, then recursively render
all of the content entries contained in that field:
# app/components/grid.rb
class Grid < Renderful::Renderer
# This will define a `resolved_blocks` method that reads external references
# from the `blocks` fields and turns them into Contentful::Entry instances
resolve :blocks
def render
entries = blocks.map do |block|
# `client` can be used to access the Renderful::Client instance
<<~HTML
<div class="grid-entry">
#{client.render(block)}
</div>
HTML
end
<<~HTML
<div class="grid">#{entries}</div>
HTML
end
endYou can easily cache the output of your renderers by passing a cache key when instantiating the
client. The value of this key should be an object that responds to the following methods:
#read(key)#write(key, value)#delete(key)#exist?(key)
A Redis cache implementation is included out of the box. Here's an example:
renderful = Renderful.new(
contentful: contentful,
cache: Renderful::Cache::Redis.new(Redis.new(url: 'redis://localhost:6379')),
renderers: {
'jumbotron' => JumbotronRenderer
}
)If you are using Rails and want to use the Rails cache store for Renderful, you can simply pass
Rails.cache, which responds to the expected interface:
renderful = Renderful.new(
contentful: contentful,
cache: Rails.cache,
renderers: {
'jumbotron' => JumbotronRenderer
}
)The best way to invalidate the cache is through Contentful webhooks.
Renderful ships with a framework-agnostic webhook processor you can use to automatically invalidate the cache for all updated content:
Renderful::CacheInvalidator.new(renderful).process_webhook(json_body)This is how you could use it in a Rails controller:
class ContentfulWebhooksController < ApplicationController
skip_before_action :verify_authenticity_token
def create
Renderful::CacheInvalidator.new(RenderfulClient).process_webhook(request.raw_post)
head :no_content
end
endThe cache invalidator will not only invalidate the cache for the entry that has been updated, but
also for any entries linking to it, so that they are re-rendered. This is very useful, for instance,
if you have a Page entry type that contains references to many UI components - when one of the
components is updated, you want the page to be re-rendered.
If you are using Ruby on Rails and you want to use ERB instead of including HTML in your renderers, you can inherit from the Rails renderer:
class JumbotronRenderer < Renderful::Renderer::Rails
endThen, create an app/views/renderful/_jumbotron.html.erb partial:
<div class="jumbotron">
<h1 class="display-4"><%= entry.title %></h1>
<p class="lead"><%= entry.content %></p>
</div>As you can see, you can access the Contentful entry via the entry local variable.
The Rails renderer uses ActionController::Base.renderer by default, but this prevents you from
using your own helpers in components. If you want to use a different renderer instead, you can
override the renderer method:
class JumbotronRenderer < Renderful::Renderer::Rails
def renderer
ApplicationController.renderer
end
endIf you want, you can also add your own locals:
class JumbotronRenderer < Renderful::Renderer::Rails
def locals
italian_title = entry.title.gsub(/hello/, 'ciao')
{ italian_title: italian_title }
end
endYou would then access them like regular locals:
<div class="jumbotron">
<h1 class="display-4">
<%= entry.title %>
(<%= italian_title %>)
</h1>
<p class="lead"><%= entry.content %></p>
</div>If you need to render resolved fields (as in our Grid example), you can use renderer and
client to access the Renderful::Renderer and Renderful::Client objects:
<%# app/views/renderful/_grid.html.erb %>
<div class="grid">
<% renderer.blocks.each do |block| %>
<div class="grid-entry">
<%= client.render(block) %>
</div>
<% end %>
</div>After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run
the tests. You can also run bin/console for an interactive prompt that will allow you to
experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new
version, update the version number in version.rb, and then run bundle exec rake release, which
will create a git tag for the version, push git commits and tags, and push the .gem file to
rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/bestmadeco/renderful.
The gem is available as open source under the terms of the MIT License.
Renderful is sponsored and maintained by Bolt Threads Inc..